CoreProtect seems to only log the current block state in the world instead of what was provided to the queue.
This of course causes several issues to the plugin itself, as well as to any plugin using the API to log block actions.
How to reproduce
- Place a flower pot.
- Insert a flower into it.
/co inspect it
Expected result:
intelli broke flower_pot intelli placed potted_flower_name
Actual result:
intelli broke flower_pot intelli placed flower_pot
Of course other things are broken, this is the easiest one i could come up as an example.
Somewhere in the chain it's getting the material from the location again instead of using what was provided.
This seems to have been an issue for at least a month according to my sever logs.
After some digging the issue seems to be with commit eee96fb5f99bed23912a078434d955658d9c59b9
CoreProtect seems to only log the current block state in the world instead of what was provided to the queue.
This of course causes several issues to the plugin itself, as well as to any plugin using the API to log block actions.
How to reproduce
/co inspectitExpected result:
intelli broke flower_potintelli placed potted_flower_nameActual result:
intelli broke flower_potintelli placed flower_potOf course other things are broken, this is the easiest one i could come up as an example.
Somewhere in the chain it's getting the material from the location again instead of using what was provided.
This seems to have been an issue for at least a month according to my sever logs.
After some digging the issue seems to be with commit eee96fb5f99bed23912a078434d955658d9c59b9