[General] - Mod Config not read properly by client

[ZupaleX]

Bug Submission:

Category: General
Issue Title: Mod Config not read properly by client
Issue Description: Hello,

so basically, the client do not retrieve the mod config data from the host anymore even with "all_clients_require_mod = true). I tried with many mods and all behave the same while I was quite sure it was not the case before (examples : Craftable Catcoon House, Chester eyebone recipe, Archery Mod,...)

This is quite easily noticeable when it comes to recipes:
The client see the recipe from his config file.
The host expect the recipe from his config file
So when the client try to craft the itemfrom his recipe, it just doesn't work (just get the crafting animation which last longer than usually and nothing get out of this).

Strange thing : the client log says that it applies the temp config though, and I believe that this temp config is supposed to be a replica of the host config.

 

After some more testing, it looks like there is two case scenario:

 

1) The server is a dedicated server : The client will recieve the mod config data properly as long as there is no *mod*_CLIENT file in the "mod_config_data" folder of the dedicated server.

 

2) The server is a player hosted server: The client will never get the mod config data from the server but will use his own config data instead.

Steps to Reproduce: Set a mod configuration for the server (easier to reproduce is to use a hosted server directly from within the game and not a dedicated one). Then change the config from the main menu -> Mods on the client (or even do not touch it, it will then be the default values for the client).

[ZupaleX]

The issue is still occuring and it's extremly annoying. An aknowledgement at least would be welcome.

[PeterA]

@ZupaleX, thanks for reporting the issue! I've put in a fix for it, and you should get that in the next update.

[ZupaleX]

Thanks for letting me know. The wierd thing was that it did not happen for everybody so I guess it was not easy to pinpoint what it was.