Tutorial draft: SHA-256 release signing (#668)

Looking for a second pair of eyes before we tag a release. Client target: 12.x/13.x OTC builds with our custom modules disabled for the repro. Map size is roughly mid-scale with custom hunting zones east of the desert. Any safer pattern for rolling this out without wiping houses?

Map looks promising. Hunting loop needs clearer signage near the temple.

Thanks — we saw the same spike when market history grew past 500k rows.

Agree on the VirusTotal rule for binaries. Hash + VT link or it does not ship.

If you share the stacktrace (redact IPs), I can compare with our build.

Good call separating AAC auth from game auth cookies.

I would pin a status endpoint and keep Cloudflare off the game port.

Consider feature-flagging it for premium only during the first week.

For Windows hosts, mark the service recovery options or it will not auto-restart.