WayneByNumbers Posted September 28, 2013 Report Share Posted September 28, 2013 Ran across this troublesome spammer today, who seems to have heard of a clever little way to circumvent some block trackers: Lava in the water turns into obsidian. While SafeBuckets prevents the rest of the lava from spreading, the trouble is that LogBlock doesn't track lava blocks hardening; the rollback only got the lava blocks, while for the obsidian I had to use /removenear, and then a little /fixwater to clean up. Can LB be configured to track fluid-to-solid events? Link to comment Share on other sites More sharing options...
buzzie71 Posted September 29, 2013 Report Share Posted September 29, 2013 Did you check for edits by LavaFlow or WaterFlow (think it's the former)? Try coal-blocking one of the hardened blocks. I know on S that lava flowing into water and causing water to turn to stone will leave an edit in the logs by LavaFlow. Link to comment Share on other sites More sharing options...
WayneByNumbers Posted September 30, 2013 Author Report Share Posted September 30, 2013 Nope, I've checked. Coal-blocking the obsidian logs the lava placement, but not the obsidian creation. I did a trace on LavaFlow, to make sure, and a couple edits showed up, so I know that feature is running. Why do I always* seem to run across these LB vulnerabilities? *Ok, twice. Link to comment Share on other sites More sharing options...
buzzie71 Posted October 1, 2013 Report Share Posted October 1, 2013 Ahh, blast it ><. I stand corrected then, my fault. Link to comment Share on other sites More sharing options...
totemo Posted October 2, 2013 Report Share Posted October 2, 2013 Since this is in PMC and not on the github issue list, presumably for the sake of discretion, I'm commenting just to acknowledge the issue. I believe that it can be fixed in SafeBuckets itself. Link to comment Share on other sites More sharing options...
Recommended Posts