You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Issue description:
Exactly the same as #467, rftoolsdim-server.toml resets on ever server start after changing any settings.
Server installed locally on my personal machine, so no server host forcing the file to reset, it's just resetting to default
Steps to reproduce: change anything in the rftoolsdim-server.toml and restart server, then check the config file and see if its reverted.
Versions:
Minecraft: 1.20.1
Forge: 47.1.76
CompatLayer (only if on Minecraft 1.10 or 1.11):
McJtyLib: 1.20-9.0.3
RFTools: 1.20-5.0.2
RFTools Dimensions: 1.20-11.0.4
Possibly incompatible mods:
Relevant logs, if any:
The text was updated successfully, but these errors were encountered:
I think I know what is happening now ... the modpack I am using has a rftoolsdim-server.toml file in defaultconfigs/ that is being used to overwrite any settings I change in my world/serverconfig/ folder. If I change the file in defaultconfigs, then I see the changes.
If anyone else is trying to troubleshoot this issue, check for a rftoolsdim-server.toml file in defaultconfigs that was placed there by the modpack creator. If you need to make changes, change the file in defaultconfigs. New pack updates may undo your changes.
Issue description:
Exactly the same as #467, rftoolsdim-server.toml resets on ever server start after changing any settings.
Server installed locally on my personal machine, so no server host forcing the file to reset, it's just resetting to default
Steps to reproduce: change anything in the rftoolsdim-server.toml and restart server, then check the config file and see if its reverted.
Versions:
Minecraft: 1.20.1
Forge: 47.1.76
CompatLayer (only if on Minecraft 1.10 or 1.11):
McJtyLib: 1.20-9.0.3
RFTools: 1.20-5.0.2
RFTools Dimensions: 1.20-11.0.4
Possibly incompatible mods:
Relevant logs, if any:
The text was updated successfully, but these errors were encountered: