# Command reference Epoch Forge operates on the current working directory; it does not yet search parent directories. `efo --help` is the authoritative syntax. ## Repository and timeline - `efo init [--force]` creates `.epoch` and `epoch/0/epochinfo.json`. Although `--force` is accepted in 0.1.0, it currently has no effect and will not allow a non-empty directory. - `efo status [EPOCH_ID]` shows an epoch summary, tags, and entity counts. - `efo epoch log [-c N]` shows epochs around the current epoch. - `efo epoch next` creates and checks out the next snapshot. It refuses while later snapshots exist. - `efo epoch switch ID_OR_TAG` checks out an existing snapshot without deleting later ones. Its currently accepted `--force` flag has no effect. - `efo epoch summary TEXT` and `efo epoch tag TAG` annotate the current epoch. - `efo epoch diff START [END]` reports added, removed, and modified entities. `END` defaults to the current epoch. - `efo epoch fsck` performs a read-only consistency check of epoch IDs, tags, and entity UUIDs. It does not repair damage. - `efo epoch reset` permanently deletes every epoch after the current one. ## Entities The built-in nouns are `chr`, `town`, `event`, `calamity`, and `blocker`: ```text efo add [NAME | --rng-name] [OPTIONS] efo edit [OPTIONS] efo show [NAME|@UUID] efo diff [--epoch-id ID_OR_TAG] efo del ``` Names match by prefix. `@UUID` is the stable form printed in detailed output; short UUID prefixes are accepted. Avoid ambiguous prefixes. Common add/edit options include `--stats key:value ...`, `--position x,y`, `--duration`, `--bounds`, `--effect`, faction/reach/description/relationship options, and prestige controls. `edit --delta` adds supplied stats rather than replacing them. See nested help (for example `efo chr add --help`) for exact syntax and values. Mutations write the current epoch immediately; staging does not exist yet. The top-level `show` command is currently demo output. Use ` show`. ## Generation and output `efo gen character|town|event|exotic|calamity|blocker` prints generated content. The first naming operation may unexpectedly create `naming.json` in the current directory; removal of this side effect is planned. Output is human-readable Unicode. Some 0.1.0 renderers emit ANSI colour when redirected and use optional Nerd Font glyphs; these are known accessibility issues. Stable JSON output is planned. A panic is always a bug.