Hi, I have a few things I’d like to request:
- A higher WorldEdit block limit.
I find it difficult to copy and paste objects with the 3000 block cap. It makes more work in forcing me to cut and paste objects in several parts, when it would be much easier to do in one. I understand that the limit is there to reduce the risk of an inexperienced user, or potential griefer, but I find that the limit can cause more harm than good as it requires even more skill to move someone’s creation in two parts; something I found whilst trying to help dudersman.
- VoxelSniper (plugin).
This one is a big ask. It’s not so much of a request, but more of a suggestion. Although I find WE to be extremely useful, VoxelSniper covers a different area, one which WE cannot. A few months back, I went to a huge effort to set up my own crappy, laggy server, port-forwarding and all, just to get it and I found it to be incredible (mostly for terraforming, but also making ‘sculptures’ [see my YouTube channel]).
Thanks,
-Dylan.
Edit: It’s unlikely that Silarn will comply with either of these, but I thought it was worth a shot.
I was going to take a look at VoxelSniper but their servers are having issues and there is no way to get the plugin since they want you to use an installer plugin which tries to connect to a server which is down.
So, go yell at them and tell me when it’s fixed. Kthxbai.
It’s installed but this plugin has a fucked up ‘look-at-me-i’m-a-special-snowflake’ permission system that means I will have to manually add everyone that should have access to plugin commands. It’s pretty dumb.
I also can’t say I’m a fan of the ‘download our downloader so you can download our other plugins!’ bit either.
I’ve given VIPs and Deps ‘SniperLite’ permissions and Mods full permissions. Again, this is not automatic. I will have to manually add someone to the list if they are promoted. voxelwiki.com/minecraft/Voxe … r_Settings has commands.
Don’t fuck it up, I will remove this in a heartbeat.
I increased the WE limit to 5000.
Wow, you are a hero! Thanks a lot, Silarn, I bet that took a long time, it is much appreciated. 
I couldn’t have asked for a better result! haha
Edit: - I can’t up my WE limit past 3000; i’ve tried typing //limit 5000, but it denies my command. I’m sure you’ll be able to fix this easily.
(FIXED) Thanks!
- I just tried it out and it works a treat! I've been looking for a way to use this for some time, oh how i've missed it. Expect wonderous and magnificant builds hereafter.
Also, a note to other players who are thinking of using it:
I’d say it’s more difficult to grasp than WE, so be extremely careful! If you don’t already have past-experience with it, please wait and i’ll show you the basics. If you’ve foolishly had a mess around with it and made a huge gaping hole, then your greatest friend is ‘/u’ for undo, or
‘/u (n)’.
Secondly, it is used with the same wand tool as WE (an arrow), but only requires single slashes ‘/’ to operate. This means that selecting the second point can be a problem if you’ve set a VoxelSniper brush size, causing you to make a hole instead. To fix this simply set your brush size to 0 with ‘/b 0’.
I’ve encountered a problem with it.
Unfortunately because WorldEdit’s wand tool is also an arrow, there is a clash. The major one, and the only one I have noticed so far, is that whereas right clicking would have previously selected the second point (in WE), it now deletes a block.
This is because right-clicking is the ‘use’ or ‘action’ function for VoxelSniper’s brush which is set, by default, to 1 block in size with air as the material.
Obviously VoxelSniper chose the arrow because WE’s wand is the wooden axe, by default; picked to avoid problems like this, I assume.
As for a solution, would it be possible to re-assign a new wand item to either WorldEdit or VoxelSniper? If not, then I don’t know, re-bind the singular key, if that’s possible?
It may be a nice tool, but VS’s almost total lack of configuration options and server admin tool support (like permissions) is really sucky.
I’ve redefined WE’s tool to the bone.
Just a reminder that the WE tool is now the bone. But you’ll get this automatically if you do //wand anyway.