Arma 3 · Exile Mod · Tanoa

A server, and everything
that keeps it alive.

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.

XCSV EXILE — in development Arma 3 2.20.152984 Exile 1.0.4a Pineapple MariaDB 10.11 extDB3 x64 · 12 GB target Console Rust + egui

00 — AI / AGENT GATEReconcile before building

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.

Roadmap ≠ implementation proof

The roadmap owns priority and intent. Local source, git, GitHub, deployed artifacts and runtime evidence each prove different parts of reality.

Find the delta

Classify work as done, unverified, partial, planned, conflicted or blocked. Never build substantially equivalent functionality twice.

Then run the Gauntlet

Reconciliation comes first; Target Lock and the risk-scaled worker/critic Gauntlet happen only after the remaining work is known.

One execution tracker

GitHub Issues + Projects track active execution. The roadmap remains durable decision memory, avoiding a second Trello/Jira-style source of task truth.

XCSV GUARD supervising the live server
XCSV GUARD supervising the live server — process state, memory against the 12 GB x64 target, and every pre-flight check that exists because something once broke. More screenshots →

01 — REPOSITORIESFour repos, one system

The hub carries documentation and submodule pointers. Everything else lives where it is built — and each has its own page here.

XCSVpublic

The hub. System map, this site, the wiki, and submodules pointing at every other repository. Start here.

Markdown · HTML · git submodules

XCSV_GUARDprivate

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.

Rust · egui / eframe · UDP RCon · DPAPI

XCSV_ADDONSprivate

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.

SQF · CfgExileCustomCode · CfgXM8

Exilepublic

Catalogue of third-party addons and scripts, database schemas, plus custom engineering tooling: a PowerShell PBO packer and a BattlEye RPT auto-triage.

SQF · SQL · PowerShell · C#

02 — ARCHITECTUREHow it fits together

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.

03 — HARD-WONFive things that cost real hours

Every one of these is now an automated check in XCSV GUARD, so it cannot cost them twice.

  1. A corrupt PBO still passes a checksum verify. A leading \ 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.
  2. extDB3/x64 is production now. The old extDB2 bridge and 32-bit rollback artifacts were removed by policy. The server runs arma3server_x64.exe with -maxMem=12288.
  3. -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.
  4. Arma's server simulation is single-threaded. SQF 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.
  5. Half the errors you can see are symptoms. Bridge errors and protocol noise can appear after the real failure. Count Starting mission: instead; more than one means a restart loop, and only the first error is real.

04 — STATUSWhat is running

ComponentStateNotes
ServerliveTanoa · listed as “XCSV EXILE (In Development)”
DatabaseliveMariaDB 10.11 · extDB3 · x64
PBO integritygatedchecked every poll; blocks start on failure
Stack orchestrationdoneone start / one clean stop
Headless clientliveA3XAI authorized · FuMS owner 4 heartbeat
BattlEye enforcementpartialstaged enforcement; remaining rules require measured triage
infiSTAR cloud403hosted upload unresolved; local logging remains authoritative

05 — ROADMAPWhat comes next

Performance before content. Reconcile before implementation. The full roadmap lives in the documentation and the full engineering programme is in the GUARD Development Plan.

▸ now

AI reconciliation contract

One canonical AI entrypoint, delta-first roadmap reconciliation, risk-scaled Gauntlet, and GitHub-native execution tracking.

GUARD restart safety

Durable/reconstructable state, startup reconciliation, absolute restart deadlines, RCon recovery and Safe Mode.

Backend contracts

Backplane/services, explicit tab health states, self-diagnostics, replay fixtures and operator action history.

Operator UX

Operations/Engineering modes, attention-first Overview, universal entity inspection, Incident Mode and operations map.

Evidence & deployment

Historical telemetry, SLO/headroom, experiments, artifact registry, deployment diff, rollback and state-drift detection.

Curated player systems

Territory management, contracts/jobs, bounties, faction standing, Chronicle/community systems and choreographed events.

ELSEWHERE IN THE SYSTEMThe other three

Four repositories, one system. Nothing here stands alone.