FeaturesAuto updates

Lunar Client

The updater is split in two halves on purpose, which is why a new build takes two restarts.

1. Launch one: stage. After the game starts, a background thread asks hwic.dev for the latest version. Only if it is strictly newer does it download the jar, verify the advertised SHA-256, verify the file opens as a real bitchos jar, and stage it next to the running jar as bitchos.jar.new.
2. Launch two: apply. Before anything is loaded, the staged jar replaces the old one. The old jar is kept as bitchos.jar.bak for a manual rollback. This is the only moment the jar is not open; on Windows a loaded jar cannot be replaced at all.

Any failure at any step leaves the installed jar untouched and the launch continues normally. The chat greeting on join says which build you are on and whether it is the latest.

To turn it off, create an empty file named no-autoupdate in ~/.bitchos/.

Forge

Forge holds every jar in mods/ open for the whole session, so the mod cannot replace itself. On start it checks hwic.dev and, if a newer Forge build exists, says so in chat. Download it from the redeem page on hwic.dev and replace the file yourself.

What ships

Every published build is obfuscated and verified. The site advertises each build's size and SHA-256, and the Lunar updater refuses a download whose hash does not match. The Lunar and Forge builds are different jars with different hashes; neither works in the other's place.