Load thresholds

These decide when the launcher automatically slows its own polling and limits itself to just signing in, to keep working under heavy load instead of falling over. Deliberately low by default so you can actually trigger and test each tier on this one machine — raise them once you have a real sense of traffic.

Test a load tier

Force the tier above without needing real heavy traffic — the launcher reacts exactly like it would for real. Clears itself automatically after the duration below, so testing can't accidentally leave the site crippled.

Launcher version enforcement

Every launcher request carries its own version — anything below the minimum gets rejected outright (HTTP 426), across the whole API, not just sign-in. Automatic, not admin-set: the minimum is always exactly one patch behind whatever build is currently published, so only the latest release and the one right before it can ever connect — older builds age out on their own as new versions ship. The auto-updater itself isn't gated by this, so a blocked launcher can still fetch the newer build.

Loading…