Backup strategy for bestiary points economy (#8377)

We hit a reproducible crash after 6-8 hours uptime. Environment: Ubuntu 22.04, 4 vCPU, 8GB RAM, MariaDB 10.11. We logged query times over 200ms on market browse during peak hour. What would you change about the economy numbers? --- 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-8377.zip SHA-256: 6f74732d73796e7468657469632d66696c652d383337362d6f70656e54696269 VirusTotal: https://www.virustotal.com/gui/file/6f74732d73796e7468657469632d66696c652d383337362d6f70656e54696269 Note: demo hash for seed content only — replace with your real release hash before publishing.

If you share the stacktrace (redact IPs), I can compare with our build. Also: please keep the VirusTotal link next to the mirror. Example: https://www.virustotal.com/gui/file/6f74732d73796e7468657469632d66696c652d383337362d6f70656e54696269

Good call separating AAC auth from game auth cookies.

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