• Guest, we are doing a new map (refresh) for Herocraft. Gather your friends and get ready! Coming next Friday, 06/28/24 @ 7PM CT play.hc.to
    Read up on the guides and new systems! Here.
    View the LIVE Map here @ hc.to/map
    Stuck or have a problem? use "/pe create" to to open a ticket with staff (There are some known issues and other hotfixes we will be pushing asap)
  • Guest, Make sure to use our LAUNCHER! Read more here!

Bug /to whatshere is inaccurate

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:
  • 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.
The only reliable method would seem to be asking a non-member to check by breaking blocks around the perimeter.

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.
 

LordZelkova

Ashen One...
Legacy Supporter 8
Joined
Jul 3, 2011
Last time I hand counted Ahkrin our region was off 1 block for both N & S directions. However I chalked this up to me miscounting.

It would be very nice to get a tool to check for SR's. Like we used to be able to.
(Especially because the "You have entered town" message doesn't appear at the end of the region, it takes a second to appear)
 

Kainzo

The Disposable Hero
Staff member
Founder
Adventure Team
Joined
Jan 7, 2011
Location
The 7th Circle of Heaven
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:
  • 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.
The only reliable method would seem to be asking a non-member to check by breaking blocks around the perimeter.

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.
*head explodes*
 

SoHighFive

Soulsand
Joined
Jan 2, 2014
I believe that I have figured out the issue or at least part of it. This was all with WitchOnARampage's help.

I just upgraded to a Hamlet (should be 89 x 89) and here is what we discovered.

1) Using /to whatshere I mapped the area of blocks that ALWAYS show SR on them. This means that I have a true 86 x 86.

2) I have a border outside of that where /to whatshere shows me inside the SR if I'm on the inner half of that block (facing the center of my SR), but it shows you outside of the SR if you're on the outer half of the block. With that I technically have an 88 x 88.

Conclusion- I need a non town member to confirm this, but I believe that the coding is allowing for a 86 x 86 fully protected SR with an extra half block just on the outside to allow signs and torches to be protected there. This is great as long as those creating their SR are aware that the outer half layer for torches can't be used for walls.

I'll try to get somebody to test the torch/sign idea later, but it makes a lot of sense to me.

Let me clarify that I have not tested whether the outside layer of the true 86 x 86 is actually protected or not.
 

WitchOnaRampage

Legacy Supporter 9
Joined
Jul 15, 2012
Location
Australia
I believe that I have figured out the issue or at least part of it. This was all with WitchOnARampage's help.

I just upgraded to a Hamlet (should be 89 x 89) and here is what we discovered.

1) Using /to whatshere I mapped the area of blocks that ALWAYS show SR on them. This means that I have a true 86 x 86.

2) I have a border outside of that where /to whatshere shows me inside the SR if I'm on the inner half of that block (facing the center of my SR), but it shows you outside of the SR if you're on the outer half of the block. With that I technically have an 88 x 88.

Conclusion- I need a non town member to confirm this, but I believe that the coding is allowing for a 86 x 86 fully protected SR with an extra half block just on the outside to allow signs and torches to be protected there. This is great as long as those creating their SR are aware that the outer half layer for torches can't be used for walls.

I'll try to get somebody to test the torch/sign idea later, but it makes a lot of sense to me.

Let me clarify that I have not tested whether the outside layer of the true 86 x 86 is actually protected or not.

SoHigh, I was excited by what I found, but then I realized I'd only tested 2 towns, so I checked another 3 to make sure.

And I've listed what I found above. It was different everywhere!

I reckon the blocks that a non-town member can't break are fully protected, regardless of what /to whatshere says.

The protection is there (albeit on one block short). It's the whatshere command that's bugged.

Btw if anyone would like to check my Maths ... I got very excited because I'd stand in the line of blocks that I could break and take the coords there. At first I figured that the difference between the coords was the number of blocks in between, and they were showing up nicely as 51, 89, 123.

Then I realized of course that it's not the number of blocks in between, but rather that number less 1. As an example, if I could break in rows 5 and 10, the number of blocks in between is not 10 - 5 ie 5, but rather 4 (the blocks 6,7,8 and 9).

Hence the regions were actually one less than the size they're supposed to be (radius of 25 plus center block etc).
 
Top