Skip to content
3 Death Saves

Bondsmith

Every character keeps a separate standing with each faction and NPC. Reputation can decay toward a target value on a schedule, and a relationship board maps the whole web on the canvas.

Getting started covers installation, tracking your first actors, and opening the viewer.

Every setting is listed on the settings page.


Every tracked actor keeps its own score with each faction and NPC. Score ranges map to tier names and colors drawn from a built-in preset, one you write, or a Roll Table linked to a faction.

Give a faction members and ranks. Nest locations inside each other as continents, countries, settlements, and points of interest. Factions and actors can each hold a share of control over a location, and a location with more than one controller shows a contested badge.

Model relations between actors, factions, and locations. View them as force-directed, genealogy, map, or timeline graphs. View and edit rights on a graph are set per player.

Flag a scene as a relationship board and the connection lines for all tokens on the scene stay on screen at once, rather than only the lines belonging to the selected token. Board scenes also get the Arrange Tokens tool. A separate scene option turns on connection lines and adds the Draw Connection tool for lines you draw between two tokens yourself.

Pull reputation toward a target value on a schedule with reputation decay. Set it globally, then override it on a single actor or faction.

Hide entities from players with visibility controls. An actor can show players a masked name instead of its real one. Scores can read as tier names instead of numbers.

Fire reputation changes off game events with automation triggers.

Review reputation and relation changes in the change log. Move data between worlds with import and export.

Macros and modules read and write reputation, relations, factions, and graphs through the developer API. Bondsmith also fires hooks other code can listen for.