02-06-2014, 05:58 PM
(This post was last modified: 02-06-2014, 06:07 PM by redstonewarrior.)
You're a bit behind the ball on this one, we've been using worldedit for a long time.
We don't integrate W/E with the plot plugin for the same reason we don't have plot protection on build; we feel the collaboration and open nature of the build server is more important than avoiding the rare accidental W/E derp or grief, and with the backup system, we very rarely can cause real damage. (Perhaps some lag / few minutes of downtime every few days, but that's all.)
We can, and we've considered it, and regardless, we're soon going to throw in a 2x2 plot limit on W/Es (and a 64x64x64 limit on //g?)
We already have a schematic saving system, and it's built into W/E! //copy a region, then type //schematic save <username>/file. You can bring it back by using //schematic load <username>/file, and you can access them all via http://schems.openredstone.org/.
As for more useful things, we've also considered building a standard component database using schematics, but we haven't gotten to it.
We don't integrate W/E with the plot plugin for the same reason we don't have plot protection on build; we feel the collaboration and open nature of the build server is more important than avoiding the rare accidental W/E derp or grief, and with the backup system, we very rarely can cause real damage. (Perhaps some lag / few minutes of downtime every few days, but that's all.)
We can, and we've considered it, and regardless, we're soon going to throw in a 2x2 plot limit on W/Es (and a 64x64x64 limit on //g?)
We already have a schematic saving system, and it's built into W/E! //copy a region, then type //schematic save <username>/file. You can bring it back by using //schematic load <username>/file, and you can access them all via http://schems.openredstone.org/.
As for more useful things, we've also considered building a standard component database using schematics, but we haven't gotten to it.