Anti-Piston-Dupe v1.0 By Sleaker Obselete with 1.7.3 servers Download: Here! AntiPistonDupe is a simple plugin that checks when a player places a piston. If the piston is in a location that could result in being abused by duping the piston is dropped back into the world. Usage: Just drop the Jar in your Plugins directory!
I'm still worried about this in teh minecraft wiki: "Placing a lever 1 block above and to the side of a piston and then activating the lever will cause the game to crash and will crash every time you try to join the world which has this bug." Has this been fixed? I'm afraid to try it... If it hasnt, could you add this to the blocked placement configuration?
New standard reply for these types of posts is: No it doesn't. This. EDIT by Moderator: merged posts, please use the edit button instead of double posting.
It has already been fixed in 1.7_01. I had that crash, then they pushed the update now everything works well.
Thx for the quick reply =). Sleaker, Nice job on the plugin btw! It does work as described, gonna test it on fullscale playerbase. They always manage to find a way around things =P. I'll report back
@crysis992 - I've got that fixed now, sitting on the update though. I saw where players could use sticky pistons to infinite dump sand/gravel, got some logic to fix that one and I'll have the update out soon
Works perfect. That will definately help! I wasn't sure what I was going to do, I've been waiting for this plugin!
Stops working with this message... 15:15:14 [WARNING] Task of 'AntiPistonDupe' generated an exception java.lang.ClassCastException: org.bukkit.material.MaterialData cannot be cast to org.bukkit.material.PistonBaseMaterial at com.sleaker.antipiston.PistonChecker.run(PistonChecker.java:34) at org.bukkit.craftbukkit.scheduler.CraftScheduler.mainThreadHeartbeat(CraftScheduler.java:137) at net.minecraft.server.MinecraftServer.h(MinecraftServer.java:438) at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:361) at net.minecraft.server.ThreadServerApplication.run(SourceFile:422) Yes Users were trying to get their machine to work when this occurred and now their machine is running again, plugin still loaded.