Best practice for depot inbox overflow (#4323)

Looking for a second pair of eyes before we tag a release. We logged query times over 200ms on market browse during peak hour. Scripts are Lua-only so far; no C++ patches in this branch. Any safer pattern for rolling this out without wiping houses?

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.

Try indexing the player storage lookups; it helped our spawn scripts.

We documented a similar path in our ops notes last month.

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

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