Tutorial draft: skull system tuning (#7948)

Looking for a second pair of eyes before we tag a release. Map size is roughly mid-scale with custom hunting zones east of the desert. We keep configs in git and treat live changes as a hotfix branch. Any safer pattern for rolling this out without wiping houses? --- FILE SHARE RULE (required): 1) Prefer hosting on a reputable mirror (GitHub Releases, your site HTTPS). 2) Every download link MUST include a VirusTotal analysis URL for that exact file hash. 3) Paste: file name, version, SHA-256, VirusTotal link, supported client/engine, license. 4) Archives without a VirusTotal link will be removed. Example VT link format: https://www.virustotal.com/gui/file/<sha256> Synthetic example package: ots-community-tool-7948.zip SHA-256: 6f74732d73796e7468657469632d66696c652d373934372d6f70656e54696269 VirusTotal: https://www.virustotal.com/gui/file/6f74732d73796e7468657469632d66696c652d373934372d6f70656e54696269 Note: demo hash for seed content only — replace with your real release hash before publishing.

Map looks promising. Hunting loop needs clearer signage near the temple. Also: please keep the VirusTotal link next to the mirror. Example: https://www.virustotal.com/gui/file/6f74732d73796e7468657469632d66696c652d373934372d6f70656e54696269

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.