gchecking displays incorrect information.

Issue #275 invalid
Anna Bakker created an issue

When gchecking a placement grief alert, it can display incorrect infomation.

Tested with player gi634 placing a piston at Sat 21 Mar 03:05:28 GMT 2015 (servertime). gcheck number was 799. Put me in the correct spot looking at the piston he had placed. But came up with Blobehh's notes and info.

2015-03-21_16.03.47.png

Also earlier I had gchecked a gold block placed by Zen_Fighter and it had also came up with Blobehh's info too after teleporting me to the correct location. This was around 02:02 Servertime on the same day.

2015-03-21_15.03.40.png

Originally reported in a comment on: https://bitbucket.org/minecraftonline/griefalert/issue/7/failing-to-log-duplicate-placement-events

Comments (2)

  1. Riot

    Ah i see, thanks for reporting it here, I feel bad for closing it as invalid now you've gone to all the trouble, but this is after all the same issue with gcheck failing to log. The problem here is there is no gcheck 799 in the logs for the placement.

    The log lines are

    2015-03-21 01:23:02 [INFO] GriefAlert:Blobehh:broke:glass:0:x=-5193:y=39:z=-11103:sx=-5187:sy=38:sz=-11102:w=normal:799
    ...
    2015-03-21 03:05:08 [INFO] GriefAlert:gi634:used:piston:0:x=-1633:y=80:z=-9148:sx=-1630:sy=80:sz=-9145:w=normal:798
    2015-03-21 03:05:18 [INFO] GriefAlert:Anna_28:gchecked:799
    

    The second placement generated the alert, but only the first one was logged. So this display is "correct" in so far as it really did show the last gcheck 799.

  2. Log in to comment