How new blades works now

The official Blades servers shut down on June 30, 2026. This site handles community accounts, setup, reports, the public tracker and the historical archive. The Rust server implements the game APIs and arena service the clients use now.

Start at Play. The recommended direct build talks to the community service without a VPN or certificate. The older WireGuard route remains as a legacy compatibility option for existing players and as a fallback if direct does not work on a device.

Not in normal production. The old HTTPS body capture, raw packet capture and automatic database-ingest workers are retired. The VPN remains available for routing a standard client to the replacement server; it is no longer a data-collection path.

The legacy VPN build may still need the project CA because the routing layer has to answer requests made to the original game host names. That is a compatibility requirement, not an instruction to record the request or response body. The direct build avoids that route entirely.

Requests now reach infrastructure we operate. Nginx, the routing layer and the Rust server provide operational and game-service logs at the point where a problem happens. If a code path lacks enough context, the fix is to add a bounded semantic event there—not to resume blanket collection from a player's device.

A report includes the signed-in Discord account and report time, so staff can correlate it with those logs. An old capture session can still be attached when a report is specifically about preserved pre-shutdown data.

Discord is where the community already lives, and its login gives us a stable account with only the basic identity needed here. A Discord sign-in is required to file a report so the tracker does not become an anonymous-spam queue. Your account may still be pending approval when you report; the report is held until staff review it.

Public roadmap requests remain readable without an account. Actions that change state are attributed to a signed-in user.

Pre-shutdown captures cannot be recreated, so they remain a sealed research archive. Existing session, recording and deletion tools still refer to that historical material. They do not imply that new VPN traffic is being recorded.

The archive stays separate from the transactional database used by the live website. That lets us preserve evidence without feeding large capture files back through the live application.

Sign in with Discord and use the report form. Include roughly when it happened, what you expected and what you saw. A screen recording is useful for visual or timing problems, but a VPN capture session is not required for a current-server bug.