Arma 3 · Exile Mod · Tanoa
XCSV EXILE is a dedicated Arma 3 Exile server. Around it sits a Rust operations console, a set of addons written from scratch, and a catalogue of third-party systems — four repositories, one system.
Any AI working on XCSV starts with the XCSV AI operating contract. If Architect says “read the GitHub” or “read the roadmap”, the agent first performs a read-only reconciliation of roadmap intent, RAG/history, local working trees, commits, GitHub/submodules and relevant live evidence.
The roadmap owns priority and intent. Local source, git, GitHub, deployed artifacts and runtime evidence each prove different parts of reality.
Classify work as done, unverified, partial, planned, conflicted or blocked. Never build substantially equivalent functionality twice.
Reconciliation comes first; Target Lock and the risk-scaled worker/critic Gauntlet happen only after the remaining work is known.
GitHub Issues + Projects track active execution. The roadmap remains durable decision memory, avoiding a second Trello/Jira-style source of task truth.
The hub carries documentation and submodule pointers. Everything else lives where it is built — and each has its own page here.
The hub. System map, this site, the wiki, and submodules pointing at every other repository. Start here.
Operations console. PBO integrity gate, BattlEye RCon implemented from the protocol up, crash autopsy, live metrics, scheduled restarts, and one button that starts or stops the entire stack.
Our own addons and mission scripts — faction radio chatter, speaking traders, a lore briefing, an admin world census, and XM8 apps. No Exile source, ever.
Catalogue of third-party addons and scripts, database schemas, plus custom engineering tooling: a PowerShell PBO packer and a BattlEye RPT auto-triage.
The console supervises everything. One start, one stop — server, database, headless client and the local model come up and go down together.
┌──────────────────────────┐
│ XCSV GUARD │ Rust console
│ integrity · RCon · AI │ one button starts
│ metrics · restarts │ and stops all of it
└────────────┬─────────────┘
│ supervises
┌───────────────┬─────────────┼──────────────┬───────────────┐
│ │ │ │ │
┌────▼────┐ ┌──────▼──────┐ ┌────▼─────┐ ┌─────▼─────┐ ┌──────▼──────┐
│ MariaDB │◄──┤ arma3server │ │ Headless │ │ LM Studio │ │ BattlEye │
│ 10.11 │ │ (x64) │ │ client │ │ (local) │ │ RCon │
└─────────┘ └──────┬──────┘ └──────────┘ └───────────┘ └─────────────┘
extDB3 │ AI + missions triage only UDP/CRC32
│ off the main never in the
┌───────────────┴───────────────┐ thread critical path
│ │
┌────▼─────────┐ ┌────────▼────────┐
│ @ExileServer │ │ Exile.Tanoa │
│ server PBOs │ │ mission PBO │
│ XCSV_ADDONS │ │ XCSV_ADDONS │
└──────────────┘ │ XM8 apps │
└─────────────────┘
The local language model is deliberately outside the critical path. It classifies and explains logs; it holds no tools, takes no actions, and its output is treated as untrusted data. Players have no path to it at all.
Every one of these is now an automated check in XCSV GUARD, so it cannot cost them twice.
\ on every entry path makes Arma resolve
<prefix> + \path, find nothing, and silently never
load the server core. Once produced 219 mission starts in eight
minutes — and every visible error was a database error.
Verifying is not enough; you have to read the entry table.arma3server_x64.exe with
-maxMem=12288.-filePatching is mandatory.
A3XAI reads its config as a loose file. Without the flag it silently
ends the mission during world init and the server loops.spawn does not create a thread — every scheduled script
shares roughly 3 ms per frame on the main thread. More cores do not help.
A headless client does.Starting mission: instead; more than one means a
restart loop, and only the first error is real.| Component | State | Notes |
|---|---|---|
| Server | live | Tanoa · listed as “XCSV EXILE (In Development)” |
| Database | live | MariaDB 10.11 · extDB3 · x64 |
| PBO integrity | gated | checked every poll; blocks start on failure |
| Stack orchestration | done | one start / one clean stop |
| Headless client | live | A3XAI authorized · FuMS owner 4 heartbeat |
| BattlEye enforcement | partial | staged enforcement; remaining rules require measured triage |
| infiSTAR cloud | 403 | hosted upload unresolved; local logging remains authoritative |
Performance before content. Reconcile before implementation. The full roadmap lives in the documentation and the full engineering programme is in the GUARD Development Plan.
One canonical AI entrypoint, delta-first roadmap reconciliation, risk-scaled Gauntlet, and GitHub-native execution tracking.
Durable/reconstructable state, startup reconciliation, absolute restart deadlines, RCon recovery and Safe Mode.
Backplane/services, explicit tab health states, self-diagnostics, replay fixtures and operator action history.
Operations/Engineering modes, attention-first Overview, universal entity inspection, Incident Mode and operations map.
Historical telemetry, SLO/headroom, experiments, artifact registry, deployment diff, rollback and state-drift detection.
Territory management, contracts/jobs, bounties, faction standing, Chronicle/community systems and choreographed events.
Four repositories, one system. Nothing here stands alone.