Home
Features

History & Versioning

Power feature

History & Versioning

Your edits to an entity or a map are saved as versions automatically, so you can compare what changed and roll back to any version still in history.

An entity's page with its version history, two automatic versions and a checkpoint, each with a restore action, beside the note that mentions it.
An entity's page with its version history, two automatic versions and a checkpoint, each with a restore action, beside the note that mentions it.
Automatic versions as you edit, with checkpoints kept four times as deep.

How it works

  1. Edit as usual, and each version is kept

    About a minute after you edit an entity or a relationship map, Fateweaver saves a version of it. Each version says who made it and what changed.

    • Each automatic version holds about a minute of edits
    • Every entity and every map keeps its own history: the entity's History card, or the map's History tab
    • The most recent 50 automatic versions are kept, oldest pruned first, so on a busy map they turn over quickly
    An entity's History card: a note that versions are saved automatically about a minute after an edit, Save version and Compare buttons, and three versions, each with a Restore button: a checkpoint named Fair copy, 3 days ago, by Rosa Whitlock, that changed notes and tags; an automatic version from last week by Daniel Ortiz that changed colour and notes; and the first version, 2 weeks ago, by Rosa Whitlock.
    Each version says when, who, and what changed.
  2. Save a checkpoint before a big change

    Before a session or a big reveal, press Save version to keep the page as it is now. On an entity you can give the checkpoint a name.

    • Up to 200 checkpoints are kept, four times as deep as automatic versions
    • On a relationship map, Save Map Version does the same for the whole map
    The top of an entity's page: Marena Ezandi, on 3 relationship maps, visible, with four tags, and Edit layout, Save Version and Back to collection buttons beside her name, above her notes and map context.
    Save Version sits at the top of the entity's page.
  3. Compare, then restore

    Press Compare and tick two versions, or one to compare with the page as it is now, to see each field that changed and who changed it. Restore puts an entity or a map back to that version.

    • A restore adds two versions: the page just before it, so you can undo it, and the restored page. Nothing is deleted.
    • On an entity, its name, colour, visibility, tags, attributes and images come back. Tick "Also restore the notes" to bring its notes back too; otherwise they stay as they are. Relationships aren't changed; any that differ are reported.
    • On a map, the positions, colours, visibility and relationships come back, and anything that can't be put back is reported. Entity notes and attributes aren't changed.
    History after restoring "Fair copy"
    1. 6CHECKPOINTRestored "Fair copy"You, just nowNew: what the restore put back
    2. 5SYSTEMBefore restoring "Fair copy"You, just nowNew: the page just before, so you can undo the restore
    3. 4AUTODaniel Ortiz, yesterdaycolour, tags
    4. 3CHECKPOINTFair copyRosa Whitlock, 3 days agonotes, tagsRestored from here
    5. 2AUTODaniel Ortiz, last weekcolour, notes
    6. 1AUTORosa Whitlock, 2 weeks agoFirst version

    Nothing is deleted. Versions 1 to 4 stay as they were, and you can restore any of them later.

Common workflows

Undo a messy session

A live session went sideways and the map got tangled. Roll the whole map back to the pre-session state.

  • Open map history
  • Pick the last clean version
  • Restore in one step

Checkpoint before a reveal

Before you rewrite a character's allegiances, save a checkpoint so you can return to the original.

  • Create a named checkpoint
  • Make your large edits
  • Compare or revert later

Tips

  • Checkpoint before any big structural change to a map.
  • Review the diff before you restore so nothing useful is lost.
  • Pair with Map Replay to find the exact moment something changed.

Related examples

Great Houses

Checkpoints and restore are most useful on a political map that changes often.

See the Great Houses example

Collaborative Session

When several people edit at once, history shows what changed and lets you undo it.

See the Collaborative Session example

More on this: all features · pricing · FAQ. Signed in? The help button in the corner of the app has step-by-step articles, a keyboard reference, and a guided tour for every page.