Blocks with gravity logged at wrong coordinates

  • Date and Time (please include the timezone):
    Around 2022-02-17 21:20 UTC

    Describe the bug or exploit:
    When blocks affected by gravity (sand, concrete powder…) are placed with gravity turned off, CoreProtect will still log them on the location they would've dropped to. This means 2 things:

    • hitting the block won't reveal the interactions, it's needed to right-click over the first solid block under it
    • an admin can't rollback their placement while still floating as CoreProtect will apply the action in the wrong place.

    See images below:
    Sand-Log01.jpg
    Sand-Log02.jpg

    Plugin(s) impacted:
    CoreProtect, TFM

    Expected behaviour (if known):
    This one is difficult. TFM cancels the event where a falling block is summoned so CoreProtect is probably working as expected.

    If gravity is enabled later and a player makes those blocks drop, logging the original placement's coordinates would cause the opposite problem.

    TFM could catch the block placement itself and make a custom API call to CO only if gravity is off, and make another one if a floating block then drops, in case it's possible to blame an arbitrary entity (for example, I've seen [WorldEdit] as the entity's name in some logs and still don't know what's that).

    Step to reproduce:

    1. Manually place the block in the air.
    2. Inspect it. No logs.
    3. Inspect the space on the first solid block below (right click on its upper side). Log will be found.

    Server where the bug occurred:
    freedom-01

    Can the bug or exploit be reproduced on another server within the network?
    Probably, if it uses TFM to stop gravity.

    TotalFreedom's Executive Community & Marketing Manager