WorldEdit is an in-game world editor. Use it to repair griefing, or just create awesome buildings in seconds.
License: GNU AGPL v3 Basically, this means everyone is free to use, modify, and distribute the mod, as long as modifications are also licensed the same way.
Most importantly, the Affero variant of the GPL requires you to publish your modifications in source form, even if the mod is run only on the server, and not distributed. Dependencies:none GitHub:https://github.com/Uberi/Minetest-WorldEdit
Download
WorldEdit aims to be Rolling Release which means you can rely on the latest state of development working correctly. This is the preferred way of installation.
You can download a git snapshot here: ZIP file
Or install directly from ContentDB: https://content.luanti.org/packages/sfan5/worldedit/
If you for some reason prefer to have a "stable" version, please check below:
WorldEdit 1.3: ZIP file (release notes) Spoiler
MarkTraceur wrote:When I followed your instructions, I got "permission denied" (or similar). weperms.txt created, logged in with the right name, weperms looks like
There's a new world subdirectory, say world/moddata.
Define a function minetest.read_file(filename) which reads a file below world/moddata and returns its contents as a string (or an array of lines?). Similarly, define minetest.write_file(filename, contents).
Disable io.open and all other functions from from the io library. This should make it a bit safer to install random mods.
Also make sure minetest.{read,write}_file don't accept filenames that contain a directory separator or start with a dot.
And there's os.execute,os.remove, ...
or
Suggestion 2:
Like suggestion 1, but instead of minetest.read_file and minetest.write_file, define minetest.open_file(filename, mode) which opens a file under world/moddata and returns a file handle. This might mean that some functions from the io module would need to stay enabled.
or
Suggestion 3:
Restrict all filesystem access from lua and give mods some kind of access to the sqlite database.
Last edited by kahrl on Mon Dec 12, 2011 19:16, edited 1 time in total.
Suggestion 4: Suggestion 1 or 2, but with a dialog if the mod wants to write/delete something.
Like, a menu showing up: "Do you want to allow modname to write modstuff.extension? Reason: reason".
dannydark wrote:@Gatharoth you could do "//set air" ^_^
Last time I tried "//set air" I was getting an error that it couldn't replace the block(s). And now today, it replaces them. >.< Oh well. Good mod anyway
I did that, I made a weperms.txt file and added my username in the brackets as so: {John_Lennon}. It didn't work so I just put the name "test" in there, and it still didn't work. I am on windows, if that helps anything.
its case sensitive, so the login name has to equal the name in the weperms.txt
so unless your login name for the server (including local) is "John_Lennon". Then idk. (if you're not using local, then you should also put it in the server's bin folder)