WitchOnaRampage
Legacy Supporter 9
- Joined
- Jul 15, 2012
- Location
- Australia
The townships command /to whatshere appears to return inaccurate/unreliable information at super-region boundaries.
Testing (by breaking blocks as a non-town-member), I found the following situations:
It would be great to have an item that we can use to check for super-regioned blocks, the way we have coal to check for regioned blocks.
@SoHighFive @minimike96 @devotedworker @jan9f @skittles32009 @Watermelon_01 @Eligof
@Alator @cindy_k
btw I tested 5 towns (a tribe, a hamlet and 3 villages). I'm still checking my maths, but I think they all had dimensions of regioned blocks that were one less than the configs, ie 50, 88, 122. I need to review this.
Testing (by breaking blocks as a non-town-member), I found the following situations:
- Blocks along a boundary frequently return both regioned and non-regioned responses depending on where you stand on the block.
- Some of these "double response" blocks were regioned, some were unregioned.
- The information provided was Inconsistent along a line - the pattern would often change a few blocks along from the corner.
- I found some regioned blocks that /to whatshere was sure were unregioned.
It would be great to have an item that we can use to check for super-regioned blocks, the way we have coal to check for regioned blocks.
@SoHighFive @minimike96 @devotedworker @jan9f @skittles32009 @Watermelon_01 @Eligof
@Alator @cindy_k
btw I tested 5 towns (a tribe, a hamlet and 3 villages). I'm still checking my maths, but I think they all had dimensions of regioned blocks that were one less than the configs, ie 50, 88, 122. I need to review this.