Core feature

Tags

Use tags to label characters, locations, factions, and notes. Then filter and search by tag across all your content.

The tag manager showing a tag hierarchy with parent and child tags and their attributes.
The tag manager showing a tag hierarchy with parent and child tags and their attributes.
Tags nest, so a capital can live under location without repeating yourself.

How it works

From the first tag to the relationships it expects.

  1. Build the tag tree

    Make a root tag such as Role, add child tags under it, and children under those. Each tag carries a description, so everyone at the table reads it the same way.

    • See how many entities use each tag, and how many children it has
    • Reuse the same tags in every collection
    The tag manager with Role opened to City, and City opened to its four child tags, Archivist, Factor, Guild officer and Underwriter, each with its use count and description.
    Role, then City, then the roles held in the city.
  2. Give a tag the fields it needs

    A tag says a character is nobility. A field says which house, which title, and the year they were granted it. Define the fields your world needs and they become searchable, filterable, and chartable.

    • Each field has a type, such as text, a number or a dropdown
    • Set a default, and mark the fields that must be filled in
    • Typed fields on entities, tags, and events
    • Promote a field you keep retyping into a proper definition
    The attributes dialog for the Place tag: three fields, Charter status (a dropdown), Founded (text) and Population (a number), each with a default, a required switch and how many entities use it.
    Three fields declared on Place, and how many entities fill each.
  3. Child tags inherit their parents' fields

    A field declared on a parent tag reaches every tag under it, so you declare it once at the top of the family.

    • An entity has the fields of every tag it carries, and of their parents
    • A child tag's field list shows what it inherits, and from which tag

    The tag tree

    • Roledeclares Answerable to
      • Citydeclares nothing
        • Underwriterdeclares Office and Exposure

    An entity tagged Underwriter has

    • Answerable tofrom Role
    • Officefrom Underwriter
    • Exposurefrom Underwriter
    Answerable to is declared once, on Role, and every tag under it passes it down. Underwriter adds two fields of its own. If a child declares a field with the same name, its own declaration wins.
  4. Tag an entity and fill in its fields

    Pick the tags when you create an entity, and each tag's fields appear in the form, ready to fill in before the first save.

    • Stack tags (e.g., "villain", "noble", "season-2")
    • Make a new tag without leaving the form
    • Add or remove a tag on many entities at once
  5. Filter everything by tag

    Tags give you views like "all capitals," "chapter-3 cast," or "ancient artifacts," wherever the items are stored.

    • Filter maps and search by tag
    • Save a search or share a filtered view
    • Combine with relationship-type filters
    • Search for everything holding a field, or holding one answer
    • Color a map by the value of a field to see the pattern
  6. Say which relationships a tag expects

    A tag can also say which relationships its members should have. A character has two parents, a faction has one leader, a city has a ruler. Write the rule once in the Library, and Fateweaver shows which entities don't meet it.

    • Set a minimum, a maximum, or both, and which end the entity sits at
    • Child tags inherit the rule, and can override it
    • Each entity shows a checklist of what it has and what it lacks
    • Sort and filter the Entities table by what is missing
    • New relationships offer the expected types first
    The expected relationships dialog for the Signatory tag, with one rule: a Signatory is Signatory to at least one Claim, with no upper limit.
    One rule: every Signatory signs at least one claim.

Common workflows

Casting call

Tag major and minor characters by appearance or chapter to build quick pull lists.

  • "chapter-5" + "npc"
  • "season-2" + "antagonist"
  • Save the search for next session

World elements

Mark locations as "capital", "ruins", or "holy-site" to help with travel planning and lore checks.

  • Multi-tag locations by theme
  • Filter maps to focus exploration
  • Cross-reference with factions

Tips

  • Create a short list of standard tags before a campaign begins.
  • Agree the names before the map fills up, so a tag means the same thing in chapter one and chapter nine, and to everyone at the table.
  • Use prefixes like "arc:" or "season:", and keep case consistent (lowercase recommended).
  • Use tags to fill gaps in search (e.g., "plot-hook").
  • Between arcs, review your tags and merge the duplicates that crept in.

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.