How to reflect GregTech config changes in clients?

[seldonPlan]

I am in need of some assistance please.

I am running a private 1.20 Tech World server and would like to adjust some of the various config options on an already generated world. Specifically I am trying to change the following to "false" by changing Gregtech/Recipes.cfg like to:
B:ExpensiveLaser=false
B:ExpensiveSolarRecipe=false
B:ExpensiveWatermillRecipe=false
B:ExpensiveWindRecipe=false

I have made this change on the server config after shutting it down and restarted it several times now. The NEI listing does not and when I try to craft the "simpler" recipes, it does not read as a valid recipe. I have confirmed that the config file on the running server shows the changes made above so it does not seem that the config is being overwritten.

Have I missed a step? My understanding was that a change to the GregTech config on the server will affect the change downstream (after a restart). Also, I thought the NEI recipe would change as well.

Any help would be greatly appreciated.

 

[Velotican]

You must make the changes on the client as well. This is unavoidable until mod devs develop the sense to make their clients read config info from the server on login.

 

[slay_mithos]

In fact, it should be the duty of Forge to do that, because that would do it for every mods (at least forge based) at once, not just the 1 or 2 that implemented this, as well as possibly reducing the requests to the server.

 

[Abdiel]

You will need to send the modified config file to all of your clients, and have them replace their config with yours.

Don't worry, the differences are only visual if the configs don't match. NEI might not show the changed recipes, but the server is always the one who determines what can actually be crafted. So nobody can cheat by having a different client-side config.

 

[YX33A]

I suggest using Dropbox and distributing your edited configs to your players. As other have said(well, Abdiel), the difference between what you set and what you're seeing is purely client-sided. NEI reads client side configuration files, even when on a server, so if your server has the correct recipes and the client doesn't see that, it's just a illusion which they can learn to ignore. The fact that you are having trouble actually crafting the items without changing the config files client-side is worrisome, but have you tried pulling the item out of the crafting grid?

 

[seldonPlan]

Thanks for the quick responses everyone. Copying the Server config to the Clients did the trick. All of the recipes work and show correctly in NEI.

I absolutely agree that this needs to be done more transparently. There has got to be a number of ways to get config data from the server to the client without the need for manual intervention.

I really like the ftb modpacks and am appreciating all of the work that goes into them more and more every time I see how disjointed all of the (modded) components are.

 

[Norfgarb]

I believe such transfers between server and client and planned for the vanilla modding API anyway

 

[Peter_Gunnn]

I believe such transfers between server and client and planned for the vanilla modding API anyway

was that supposed to be included in or just timed with 1.5?

 

[Norfgarb]

was that supposed to be included in or just timed with 1.5?

I think the best answer to this would be that it is 1.5 independant