Server Config Improvement Suggestion

[Danny and Son]

The new server config system is amazing in that it allows servers and worlds to have different config settings than the client, but it is really confusing for a lot of users. It's difficult to imagine a time when mod devs will be able to stop re-explaining how this system works to confused users and new pack devs. Nearly every Curseforge mod page has this "where are the configs?" conversation repeatedly in its comments.

One adjustment that would make it much simpler to understand, while still maintaining the new functionality. Instead of server configs generating within world folders by default, it would be better if they could generate in the defaultconfigs folder instead. The world/serverconfig folder would be used to override server configs. The server would first look in the world's server config, and if the config file isn't there, it will look in the defaultconfigs folder. I think it would be much more intuitive this way.

[diesieben07]

The defaultconfigs already has a function, which is already given in the name: It contains defaults for any fresh worlds. This is intended for modpacks.

[Danny and Son]

I understand that, but I think you missed the point of my suggestion. The current system is confusing for users and frustrating for pack makers, because when we make changes to the default configs, it does not affect existing worlds. I am personally finding myself repeatedly explaining this system to people and telling them to delete the serverconfigs within their worlds in order to take on the new default configs.

This is why I'm suggesting changing it so worlds use the default configs, by default, rather than copying the default config to the world file. And that, all server configs be generated in the default configs folder, and not in the world folder. The serverconfigs folder can then be used just to override the default configs.

There has been a fair amount of push back from the community about this feature. Many mod authors are choosing to use common configs for cases that should be server configs and users are complaining. There's even a mod to change the behavior by forcing default configs to be copied to existing worlds, which defeats the purpose of this whole system. The suggestion I'm making would solve all these issues and make the server config system more intuitive and easier to maintain. 

[LexManos]

Yes people always fuckup systems because they think they know best.

The problem is people fail to understand what were trying to do. Or how the system works.

 

`it does not affect existing worlds` this is a prime example. Its MEANT to not effect existing worlds because in theory server side configs would cause issues if changed during the worlds life.

 

But yes people do stupid things and we do need a system that is better for pack dev's and users. The problem becomes implementation. How do we figure out what values in the world folder were intentional edits to the config. And what just happened to be different because the defaultconfigs changed. How do we write partial config files to disc with only those changes...

How do we know if the code calling the save function actually changed anything.

 

It's a annoying implementation solution that needs to be solved.

And just not writing it to the world folder doesnt work, as wed need to compare the entire config set to a copy from the defaults to see what folder we need to save it to. Mod and Forge code can call the save function quite often. And the NightConfig implementation also has issues with monitoring the files. Do we reload server configs automatically for every world when the file is modified? 

 

It's not as simple as just `if !(wolrd/config/mymod.toml).exists(): file= defaultconfigs/mymod.toml`