Fair-Play Field Manual
Keeping the game human in the age of auto.
A working knowledge base for alliance leadership dealing with automation tools (“auto”) — what they are, what they can and cannot do, why people run them, and how a management team detects and displaces them. Published automatically from a private Obsidian vault; the author isn’t here to tell a story, only to keep notes that happen to be useful to others.
How to read this
If you manage an alliance (R4/R5): start with Rules, then Psychology. Those two pages are written for you and need no technical background. Argus is the tool I’m building to back those pages with data. The Field Log is the unpolished journal behind all of it — read it if you care about how the findings were earned, or skip it entirely.
It hosts no tools, links no tools, and teaches no one how to automate. It documents what automation does — because you cannot write rules against a capability you don’t understand. Tool names are kept generic on purpose: capability matters, brands don’t.
Why this exists (short version)
On 5 Oct my alliance leader asked me to look into the auto problem. I said yes mostly because I wanted an excuse to take the game’s technology apart — and secondarily because someone had to. One month later the picture is clear enough to publish: the publisher’s anti-cheat posture is effectively absent at the protocol level, the tools are sophisticated commercial products, and the only enforcement layer that actually reacts is alliance management. That’s you. This wiki is your briefing.
Rules → Psychology → Argus. Budget 30 minutes. The Field Log is optional background.
auto.1892xsj.online · pages publish automatically; the author does not curate this site for readers.