Open jrjespersen opened 4 years ago
could be easily fixed by sending a packet with the config from the server to client. Ill see if i can implement it this weekend
No worries from me on this one. I actually want flight on, so the client override doesn't bother me (I was just suprised to see the behavior). I turn off the heart explosion on the server, and the "explosion" glitch can be worked around by either crafting in a safe area (in the air or on obsidian) or by a disconnect/reconnect of the client.
MC version: 1.15.2 Forge Version: 31.1.27 Mod version: 1.15.2-1.0.1 Config settings: flight = false explosion = false
If I turn off flight in the config on the server, but the client as flight enabled in the config, the player can still fly.
Liekwise, if I turn explosion off on the MC server, but the MC client has explosion turned on, the MC client renders an explosion and removes blocks from the rendered screen, but the blocks are still present (i.e. cannot walk through them). However, the server does not explode the blocks. If the MC client disconnects and reconnects, the "exploded" blocks are visible again by the MC client.
I'm not a modder (but I run mod servers); perhaps this could be solved by putting these config settings in the -server config instead of the -common config (I'm not sure how to direct Forge on where to put config entries)?