AOS REVIVALJoin Discord
Your player record follows you from the launcher to BattleSpades, profiles, and leaderboards. Choose a revival account, play as a signed guest, or connect with the original Steam client you already own.
Different credentials, one normalized player record and one statistics history.
A unique username becomes your callsign. The same credentials work on this site and in the launcher; the database stores an Argon2id hash, never the password itself.
Jump in without registration. The launcher proves possession of a locally generated Ed25519 key and receives a collision-safe Guest-XXXXXXXX callsign.
Retail clients keep their native protocol-168 handshake. Packet 105 carries an opaque Steam ticket; the game server waits for Valve’s OK callback before accepting the connection or resolving a profile.
Names are presentation. The server attaches gameplay to an identity only after a cryptographic proof succeeds, then exchanges it for a short-lived, single-use join ticket scoped to one server.
Inspect Steam packet 105
AUTH CHECKPOINT / REV-01Browser cookies are HttpOnly; launcher bearer tokens are random, revocable, and stored hashed.
Guest challenges expire, game tickets are one-use, and Steam callback attestations reject stale timestamps and ticket replay.
The game client cannot choose another player ID or upload leaderboard results directly.
No email is required. IP addresses are HMAC-pseudonymized for rate limits and audit events.
Practical answers about names, guests, Steam ownership, and statistics.
No. The official client can use its native Steam session ticket. A trusted BattleSpades server validates that ticket with Valve before the master service resolves the owner’s durable player profile.
No. The launcher creates a random Ed25519 key pair on that installation. The private key stays on the device, while the service stores only the public key and its fingerprint.
Revival usernames are unique without regard to letter case and double as nicknames. Guests receive a Guest-XXXXXXXX callsign. Steam display names receive a short SteamID suffix so identical persona names remain distinct.
No. A short-lived join ticket binds a connection to a player record, and only an authenticated dedicated server can submit idempotent match statistics.