Updating the config file and starting the server again resets it to default values
deltamachina opened this issue ยท 1 comments
Minecraft Version
1.20.2
Mod Loader
Fabric
Mod Loader Version
Fabric 1.20.2
Mod Version
waystones-fabric-1.20.2-15.0.0
Balm Version
balm-fabric-1.20.2-8.0.1
Describe the Issue
I am using ApexHosting to host a server.
I want to add Waystones but only allow the mods to add waystones to specific locations so I want to set it so there are no naturally generated waystones + waystones can only be placed/destroyed/edited in creative + no xp cost to tp.
I stop the server, then go to
/default/config/waystones-common.toml
and edit only these three settings:
Set to false to allow non-creative players to make waystones globally activated for all players.
globalWaystoneSetupRequiresCreativeMode = true
Approximate chunk distance between waystones generated freely in world generation. Set to 0 to disable generation.
frequency = 0
The base xp level cost when travelling between dimensions. Ignores block distance.
dimensionalWarpXpCost = 0
Once I have done so I press "Save"
Then I restart the server. This however resets the waystones-common.toml file back to default and creates a file named
waystones-common.toml.bak1
and the settings on the server are the default values not the ones in the backup file.
I have googled for hours and I can't find anything to suggest this is intended behaviour so here I am. I am very sorry if this is silly/obvious/not the right place. Please help me if you can <3
Logs
No response
Do you use any performance-enhancing mods (e.g. OptiFine) or custom server distributions (e.g. SpongeForge)?
No + I'm using ApexHosting to host the server
The server log should contain information on why the file is reset, which normally only happens if there's an error. You can also post the full config file e.g. on https://gist.github.com/