What file to edit for mod settings?

[wolfkin]

I think I have this issue on a few mods but currently I'm trying to work with Death Compass.

# When a player dies they'll be given a death compass automatically, and it will
# disappear when its duration expires or the player reaches the death location
death_compass_automatic (Death compass given to players automatically) bool false

But do I put this in world.mt or just edit it in the mods/death_compass/settingtypes.txt where that quote is found?

I tried putting it in world.mt


but when I die. I do get a death message from glamorous_deaths but no compass. That only works if I have one in my inventory before hand.

[Nathan.S]

Death Compass Settings.png (62.27 KiB) Viewed 2211 times

The easier way is to go to the settings in Luanti and search for Death Compass and change the setting there.

[Blockhead]

Not in world.mt: That only hold the handful of settings that the game engine allows to be per-world, most are global. Then the mapgen settings live in another file so that changes don't become global. You need a mod that adds World Settings, and mods have to explicity use a library like that mod to get per-world settings.

Not in settingtypes.txt: It's a little pitfall of the engine that the real defaults come from Lua and not in there.

So it goes in minetest.conf, which is easily edited with the main settings menu like Nathan has said.

To get per-world settings, some workarounds are:

1. Run Luanti with different command-line arguments to --config.
2. Modify the source code of the mod and put it into worlds/<worldname>/worldmods.
3. Run the world with a custom game that has overrides for its own minetest.conf.

[wolfkin]

The end destination is for an online server so I imagine the settings menu won't work there but thank you both. Got the answer I needed. Cheers.

Tested and it works like a charm. Again thanks.

[bgstack15]

If you're using container tech, which container image you use affects the location of the default minetest.conf. So that --config <path> is a great option.

Official Luanti docker container uses CMD ["--config", "/etc/minetest/minetest.conf"], and the linuxserver.io one uses "/config/main-config/minetest.conf" which is a little confusing to me. I suspect it ties in nicely with other linuxserver.io container design.

[wolfkin]

not yet unfortunately. I just haven't really sat down to teach myself docker. I get it conceptually but I don't know the specifics.

I just have a digital ocean droplet and I run it like bare like a linux server. Eventually I'll look into containerizing it and that'll let me run some other things on the same thing.