The issues was not registering the sync config packet on both ends. It was only registered on the client side.
Additionally, a bug was spotted where the config values would become out of sync when client connects to a server with config S, then leave the server, and join a singleplayer world which uses their local config C. Previously the client world would still use config S instead of C. That has now been fixed.
closes #106
The issues was not registering the sync config packet on both ends. It was only registered on the client side.
Additionally, a bug was spotted where the config values would become out of sync when client connects to a server with config S, then leave the server, and join a singleplayer world which uses their local config C. Previously the client world would still use config S instead of C. That has now been fixed.