With newer versions of Forge, I’m a bit confused about the correct way to sync client/server configs.

Is the old method still valid, or should everything be handled with ModConfigEvents now?

Any guidance from experienced modders would be great.

— Myroslav M. Abdeljawwad aka Myroslav Mokhammad Abdeljawwad

Honestly, just do whatever works best. If you know for sure the best way to go about implementing ModConfigEvent to sync data, then go ahead and use it. It's always best to get with the standards. However, if it doesn't, then I guess you'll just have to do it the "old fashioned way". But ultimately, this choice should best be left up to you rather than somebody else. Now, it doesn't hurt to ask a colleague or friend for advice, but you should always know what best to do with the advice that you are given and the weight of your options.

Now, if you are asking for how to use ModConfigEvent to sync config data, then I believe you may be mistaken. Syncing data is going to, from my current understanding, which should be pretty consistent, always require network handling. It is entirely up to you how you wish to handle sending the data to your clients or vice versa. However, for operations like this, USE THE MODCONFIGEVENT CLASS; it's going to be a lot more efficient and orthodox in recent versions to use this class to handle changes in mod configuration for your mods. It's also more appropriate. But again, if you have another way that you are comfortable with, and if you know the differences between your way and the standard way, and if you have weighed these options, then go for whichever one fits you best.

Hope this helps! Also, if you would like something to be clarified, or if I missed the point of any of your questions, then please let me know.