Direct answer
Mod configuration may be server-wide, world-specific or client-only; edit the file the loader actually reads.
Recommended procedure
- Stop the relevant server before editing a config that is loaded only at startup and copy the original file.
- Check
config/and world-specificserverconfig/locations as documented by the mod/loader. Do not move an unrelated client config over server settings. - Use the exact syntax expected by the mod (TOML, JSON or another format). Change one setting at a time and keep a diff.
Why this matters
Modded servers are strict about Minecraft version, loader version, mod version, and dependencies. A correct client pack does not automatically mean every client-side mod belongs on the server.
Important limitation: Mod upgrades can migrate or regenerate config keys. Preserve backups and read the release notes before copying old config files.
How to verify the result
- Restart and check both the loaded value and actual in-game behavior; successful file parsing alone does not prove the setting is used.
Version and compatibility notes
- When a setting, command, or file name differs from this guide, stop and check the documentation for your exact Minecraft/server-software version instead of forcing an old example.
Official references
These sources were checked for the current MSH revision. Version-sensitive details should always be confirmed against the project documentation for the release you run.
Related guides
Help us improve this article
Tell us what is missing, unclear, outdated, or incorrect. You can also suggest something we should add.