/stoplag

We are probably phasing this command out. The concern is that it despawns animals and villagers and this will fuck up Skagos. I can think of a few situaitons where we currently use /stoplag

-stopping massive TNT chain reactions - we may block WEing of TNT
-when people are draining or rolling back lava/water and want to stop the flow - this is annoying, but a proper rollback will still clean up the mess, just don't panic.
-glitched mobs that can't be removed any other way - they go away on a server restart
-because it is lagging due to redstone. - not sure how big of an issue this is.
-world edit fuckups causing lag - World edit block limit for non admins?
-stoping fire spread - use /stopfire

Anyone thing of any other situations when you employ stoplag?

HeyLookoverthere wrote:Anyone think of any other situations when you employ stoplag?

The biggest thing stoplag does is remove entities, which is the main thing I use it for. I think the need for it has dropped. If worse comes to worse I know how to create a stoplag command in Java and have it ignore animals.

sirrus86 wrote:

HeyLookoverthere wrote:Anyone think of any other situations when you employ stoplag?

The biggest thing stoplag does is remove entities, which is the main thing I use it for. I think the need for it has dropped. If worse comes to worse I know how to create a stoplag command in Java and have it ignore animals.

better still, could you make it per world? the wiki for worldguard says it takes a world parameter, but it lies. Anyway I've removed stoplag permissions for now and we'll see how thigns go.

HeyLookoverthere wrote:better still, could you make it per world?

Sure can.

block WEing massive blocks of tnt :O