Skip to content

ATLASAbstract Tabletop Language & Syntax

The ultimate generic rules and state engine for digital tabletop games.

The ATLAS Philosophy ​

Why use strict YAML or JSON instead of a scripting language like Lua or JavaScript?

  1. Strict Declarative Contracts: Rules are defined transparently. A player knows exactly what an entity can or cannot do because it is hard-coded in the data schema.
  2. Deterministic State for Rollback & AI: Rollback netcode, Undo/Redo features, and AI (Minimax, Monte Carlo) require perfect state clones. A declarative configuration enforces strict object parity.
  3. Separating Data from Engine Logic: By storing data in structural arrays rather than executing code, game servers are purely state machines evaluating a fixed set of constraints. ATLAS provides the data format; the Engine enforces the state transitions.

Engine Independence

The frontend client shouldn't be interpreting rules. It simply renders the current state and sends action intent back to the rules engine API.