FOSS gamedev and creative worlds

.

jordan4ibanez wrote:Minetest cannot write to the minetest.conf if it is compiled as server only it seems, or am I doing something wrong?

The server can write the configuration file if a mod calls


This was done this way instead of saving on exit to prevent losing modified settings if the server crashed. See the original pull request for details:
https://github.com/minetest/minetest/pull/391

ds-2k wrote:

jordan4ibanez wrote:Minetest cannot write to the minetest.conf if it is compiled as server only it seems, or am I doing something wrong?

The server can write the configuration file if a mod calls

Your phone or window isn't wide enough to display the code box. If it's a phone, try rotating it to landscape mode.

Code: Select all

minetest.setting_save()

This was done this way instead of saving on exit to prevent losing modified settings if the server crashed. See the original pull request for details:
https://github.com/minetest/minetest/pull/391

I have mods that call that, but they won't write

I have exactly the same issue: minetest.setting_save() is not working when I run minetestserver.
Singleplayer seems to work for other mods though. I thought I'd just missed something or that it was perhaps normal behaviour.

Hopefully someone has the answer.

btw. I am using xubuntu 12.04 & minetest 0.4.4-d1

Hmm. Have you installed from the actual Ubuntu/Debian package? Perhaps Minetest is trying to write to the /usr/share/minetest/... tree instead of saving a modified version under ~/.minetest/..., which WOULD be a problem. No normal user application should be able to write to the /usr tree.

prestidigitator wrote:Hmm. Have you installed from the actual Ubuntu/Debian package? Perhaps Minetest is trying to write to the /usr/share/minetest/... tree instead of saving a modified version under ~/.minetest/..., which WOULD be a problem. No normal user application should be able to write to the /usr tree.

Not that for me anyway. The version in question was compiled as 'run in place'. I do have the latest stable version installed in system but I've only ever used it as singleplayer.

Out of curiosity I tried it on the system wide intstallation and got same result there.
Makes no difference whether I run it as a regular user or root.

Huh. Okay. Well, it was just a thought.

By the way, I wouldn't EVER run Minetest as root, especially if you load mods you did not create yourself. Better to temporarily grant full access to /usr/share/minetest to test if that is the problem than to run as root.

Never did get to the bottom of this but it appears to fixed (for me anyway) with minetest version 0.4.5