Set a limit for yourself!

[Tchmstr]

I just found the WE //limit <limit> command, here's what it does for those that don't know: Set a maximum number of blocks to change at most for all operations. This only affects yourself. Use this to prevent catastrophic accidents. This command will not override the limit in the configuration if it is set.
We all mess up / typo once in a while, and this is a great personal safety tool to ensure those mistakes if they do happen, aren't as bad, lol. Consider setting a limit of something like 100,000 blocks(E.G. - //limit 100000), that's still a 100³(100x100x100) area. If you find you are editing a larger area, you can adjust the limit up to where you need it, then change it back down after.
Just a fun fact: The interior volume of my Master Hall on the Arch Server is an area of 1,010,100 blocks as of right now, lol.

[alexcarlson]

Goooood to knooooow.

[tomisafish]

Nice find, Tch.

[Db696]

This can really help me. Well nvm I think lite sniper needs this.

[tomisafish]

This can really help me. Well nvm I think lite sniper needs this.

Lite Sniper does infact have a block limit but I think it is no longer working properly due to it being a different version to the version of bukkit we are running...or something like that anyway.

[Pri]

Voxel Sniper has not been updated in a few months unfortunately. It is still targeting build 1060 of Bukkit which came out August 15th - We are now on build 1337 which came out on the 13th of October.

To just put that August date in perspective at that time Minecraft was at version 1.7.3 so the Voxel everyone is using is quite a bit outdated. I believe some of the issues we are currently experiencing with Voxel are due to Bukkit API's being depreciated in builds since 1060.