Changelog

0.3.0

The settings layer between server and players is now Charter, our own library, replacing the third-party one merged into earlier builds. Existing config files and the Lock Configuration setting work unchanged.
Joining a server with a missing or mismatched version of the mod shows one screen naming the mod and both versions, with a refusal code that also appears in the server and client logs.
New console command charter: charter status shows whether the server binds your settings, charter diff lists where the server's values differ from your own file, charter versions lists the mods on both sides.
Reworded the Lock Configuration description. No gameplay change.

Renamed from OathBound to Lockstep, renamed to avoid confusion with LionAndOtter's unrelated Oathbound. Versions up to 0.1.4 below were published under the old name.
Everything carries the new name: plugin GUID com.Lockstep, config file com.Lockstep.cfg, chain file LockstepChain.yml, roster file Lockstep.<world>.roster.yml, console command lockstep. The old OathBound files are not read. To keep your settings, rename the files and remove the OathBound DLL and its files from the server and every client.

The store page now links to the GitHub repository and asks for bugs and feature requests to be filed as issues there.

The chain file is read by the rewritten YAML library. A stage without key or boss is an error and the previous chain stays in force, duplicate order values are warned about, an empty chain is an error, and every message names the file and the path of the mistake.
Rebuilt on the rewritten shared configuration libraries (server sync, hot reload).
MIT license file added and noted on the store page.

Fixed a frame rate loss caused by the exception-tagging finalizer the shared library attached to every patched game method; it is removed.
YAML files starting with a byte order mark are accepted.

Config hot reload polls the file every five seconds instead of using a file watcher, which on Linux dedicated servers fired for the mod itself reading the file and hung the server at startup in an endless reload loop. The roster file is polled the same way.
No warning on the first run when the example LockstepChain.yml is written.

First working version: roster, credit by attackers and radius, altar gate with spawn guard, console commands, YAML chain, late joiner catch-up, inactive days, mid-playthrough backfill