Standing record / safety boundary

Your account is not part of the game board.

Anarchy-world conflict can be part of play. Credentials, devices, real-world identity, and service integrity are not stakes another player gets to claim.

Standing closure / outside gameplayKeep the chaos inside the world.applies behind every answer

Boundary before advice

A server premise does not grant access to you.

This manual documents terminology and practice without romanticizing credential theft, malware, doxxing, harassment beyond the game, or attacks on the service. Those remain outside the record’s gameplay frame.

Risk register / action before lore

Recognize the boundary.

These notes do not depend on a particular server allowing or forbidding a client or play style.

Credentials: Use the Microsoft launcher sign-in flow, a unique password, and two-factor authentication. A kit, giveaway, queue, or verification prompt does not create an exception.; Never provide passwords, recovery codes, session tokens, or downloaded “proof” tools.
Software: A server may tolerate modified clients while an unvetted download still compromises the machine or account. Policy and software safety are separate questions.; This record endorses no download and hosts no client package.
Conduct: Raids, traps, betrayal, and conflict may occur in-world. Doxxing, off-platform harassment, credential theft, and service attacks do not become play.; Keep real-world identity and private contact details out of reports.
Evidence: A screenshot, DM, map, or testimony can contain private data, malicious links, coordinates, or identity clues even when offered as proof.; Do not send unnecessary personal data; no attachment intake is open.

Identity and consent / pseudonyms are people

Publish less than you possess.

This site does not publish identity-bearing testimony by default. Discord identity, server membership, popularity, and in-game rank are signals at most; none proves a claim or grants permission to publish someone else’s information.

Send only what a correction requires. Screenshots, maps, private messages, and identity-bearing artifacts stay private unless provenance, rights, redaction, necessity, and a safe inspection path are established.

A correction or safety concern can use the published corrections, consent, privacy, and takedown route without opening a public thread.