Relation properties
As the cast grows, remembering “who was this person tangled up with again?” means rereading character write-ups one by one. A relation property links nodes as values — a faction, a family tie, a rival — so the ties show at a glance in the character's table and the graph draws them as lines, giving you the whole picture without drawing a character map yourself.
Say you put Raon in Vincent's “Older brother” property. Raon shows right there in Vincent's table, and a line appears between the two in the graph.
Writing a relation
A relation property is a property whose value type is Node relation. How to add one is in Node types & slots.
- Press a relation property, like Vincent's “Older brother”.
- Pick another node as its value, and the two are joined. Typing just two letters narrows the candidates.
The name in a filled-in value links to that node.
You can say it in chat, too. Say “Raon is Vincent's older brother. Add that to the World” and the agent makes the link in its reply.
Recording both sides
For a tie that comes in pairs, like older and younger brother, set it up so writing one side fills in the other. No writing it twice, no forgetting one side.
- Under Reverse sync on the relation property, pick the matching property on the other node.
- Now a relation written on one side is recorded in that property on the other node too: put Raon in Vincent's “Older brother” and Vincent goes into Raon's “Younger brother”.
Narrowing what it points to
Use Restrict to type to narrow which types the relation can point to. Point “Faction” at the faction type only, and characters and places stay out of the list you pick from.
Keeping a relation that changes
When someone changes sides or a tie breaks partway through, give the relation value a property start and end too. You don't have to delete the relation from earlier chapters.
- Board cards appear with their number in the pick list and in values, like 1.2 Name.
- Deleting a value that has a pair removes the other side's value as well, and you're asked to confirm first.