coaster3000

This actually is the update to the new tekkit nothing related to this patch. I did not have this patch and it does this.. Its part of client side issues. Client side still displays it while server doesn't really have them there.

This was a bug in tekkit that is fixed when updating to 3.0.4 Block place event handling was not being shot out to plugins. That means all plugins running off of the event handler for the javaclass BlockPlaceEvent did not recieve data thus it was not protecting block placements... I know this as i even made a test plugin to check for it on this one version of tekkit. I forget which one. But to fix it. You must update tekkit!

I am currently looking for a quick deal snippet of a towny config for item use blocking and such. I am gonna make it myself. But went searching and found none so far.. I would love help finding that.

Because the bperms team decided that the * perms must be a no go to be UNIQUE for them to develop. And thus make it a pain in the rear to manage in the end although it is a really nice perms system and gui and shit. But it does not cut the bill when pex has regexp perms PLUS * nodes. Also on recent updates on bperms its been glitching like crazy on our servers D: Not nice for us to have people tping randomly to other people even though they don't have perms. But hell who is here to fight. That is just my oppinion. Also from the post about the modifyworld issue. I agree with the one user it does not look like it should skip it... Wish i can help there..

I thank you for this topic. We suspected of the chunk loaders lagging up the server. We finally have a way to block them... We now just have to go offline and edit those blocks out >.> Hope you find your fix to your problem soon. This topic certainly helped us a lot.

Ha.. Well that explains some things.. We are currently looking for ways to disable chunk loader blocks and shit. Due to severe lag of people placing them on all their bases..