snitch feature logs cleared on canceled destroy events, or redstone events
intangir opened this issue ยท 2 comments
I have snitchblocks on my server which are jukeboxes, they are also breakable, but protected by another mod which cancels the break event
the problems are:
if redstone powers the snitchblock, it resets and loses its logs
if someone attempts to destroy the snitch and it fires an blockdestroy event, but its canceled by another addon,, the snitchblock reverts to a normal jukebox
also if someone else removes the snitchblock, and replaces it and clears it.. they clear my logs
i think a possible and easy fix to all of these things is some option to disable all snitch clearing, by command or destruction, and make another option to expire snitch records after a period of time (now that you have datetime column this should be easier)
this might've been to vague
on our server no blocks are indestructable, including snitchblocks. but i still want them to be fullproof logging
if a griefer removes your block, but you replace it in the same spot, you can still see who did it
but if they replace it themselves in the same spot, and clear it, that log is lost
so basically id like a way to make snitch log events expire after a configurable time, and another config option to make it so snitch blocks can never be cleared
i am confused on exactly how redstone effects it but it looks like you fixed that in a later build anyway so it might not be an issue
Having snitch logs remain after you remove the snitch and put it back is a side-effect of plugin conflicts on your server. The PS block-break event never runs (which should remove the field when the block is removed) thus the snitch field stays as a ghost/orphan field. Same thing that happens when you break a field block with a worldedit tool which bypasses the block break event. That is not supposed to happen. It's not feasable to code a feature/workaround that is based on a plugin conflict. Once you break a snitch the snitch should stop existing.