I still have that problem stated in my previous postings: My handle_schematics mod can't work properly. It is in part a filie browser. Its purpose is to save schematics (so far so good - no problem there) and to place schematics into the world (WorldEdit, .mts or even .schematic format). Those schematics can be found in the worldname/schems/ folder (placed there by WorldEdit) or in some gamename/mods/modname/schems/* folder (may vary a bit from mod to mod). In order for my mod to be able to supply players with a way to transfer a building from one map to another, they need to be able to select it somehow. And the mod needs to be able to actually *read* the schema file. Just telling people to copy it over does not seem to be a good idea. Neither is telling them to turn security off.

I'd be fine with an extra, simple, easy-to-understand-and-check mod that provides read access to directories (filename extensions .mts, .schematic, .we and .meta are required - the rest is of no intrest anyway) and that provides read access to those files. Said read access is only required for files which *another world* or *another mod* could read anyway. The files need to be readable without having to be opened in the init phase.

How can i modify it on my computer?is there a way to destroy it?(if it's a lua file, where is it)I HATE IT(GOOD IDEA, BUT JUST ANNOYING IF IT CANT BE TURNED OFF IN MINETEST 4.1.6 Ubuntu (tried turn off, does not work : ((( )

@ rubenwardy: but its annoying if you can't disable it on your computer,i tried to write senseful clientmod for me alone, didn't work, no os.execute, disable mod security also not work, says disabled, still no execute!plz anyone tell me how kill it so it doesn't bother me again?

Without security, the (client) mods can remove, corrupt, overwrite or encrypt all of the files to which you as user have access to. You can get the maximal destruction potential out of it by running Minetest as root or administrator (Windows).Before you're asking for a setting to disable the security: We simply cannot make for each and every feature a setting to disable it. It might look different if tens of people would request such a setting - but not in single cases.