/gcheck sometimes teleports you to where the player was significantly later than when they broke the block in question

[ftht jyjyy]

In July 29th 2018 right after 10:00 servertime /gcheck 34 took me to coordinates -174 107 333 but the block the player broke was 78m away at -95 64 334. Apparently player 45150_ did walk past the stairway where /gcheck took me and the server logged his position at the wrong time.

[Anna Bakker]

This issue is more relating to when the server thinks the block has been broken. At times it can take longer than usual for the block to break serverside and by that time the player may have already walked or teleported a distance away. From the server's point of view, that location is where the player was standing when the block is registered as broken.

Also the logging and teleporting of /gcheck is handled by GirefAlert and not scripts. So this issue is invalid.

However an addition to the command that could help could be adding info about the distance of the broken block. Though it already has coordinates of the block and usually it's easy to tell if the block wasn't there (in this case it appears to be a piston which wouldn't be on the quartz stairs).

[ftht jyjyy]

This can be really confusing. In this case the player logged off without answering any questions and I thought he might have gotten the piston from an hourly gift, placed it accidentally and then broken it. So I think it should tell you if those two positions are further apart than 5m (the distance where you can break blocks).