v0.86.1

A patch for two things found on a live server within an hour of 0.86.0.

Changing a dedicated server's settings reaches the server

Change a deployment's scene, its player cap, its tick rate or its port, and the region would write the new configuration and leave the old server running — with no sign that anything had been ignored. The next time that server happened to restart, minutes or days later, it would silently adopt settings you had changed and forgotten about.

The same gap is why 0.86.0's status-file fix needed a server to be restarted by hand before it did anything. It no longer does.

A game key can reach a server through its environment

A service manager cannot safely put a key on a command line, because every process on the machine can read one and it is copied into the system log. A dedicated server now reads FLOPTLE_GAME_KEY from its environment, which is how Floptle Cloud's own region boxes have been passing it all along. An explicit --game-key still wins.

Upgrading

Nothing to do. If you run a region box, take the new agent the way you took the last one; it will bring your servers onto the new configuration by itself this time.