1 · Durable record
The Brass Exchange
- Type & status
- Merchant guild · Active
- Headquarters
- Mireport chain-house
- Parent
- Mireport Factors
- Members
- Factor Madric · three others
- Visibility
- Party
Free D&D faction tracker
A faction becomes playable when it can act without the party. Keep its identity stable, then update only the pressure that changed.
Build the two-part faction briefWhere each faction stands
The Drowned BellAgainst
House Madric
Owns the party’s harbour debt.
Watching
Brass Exchange
Waiting to back a winner.
With
Fellwake Hand
Owes the party one favour.
Party posture is optional shorthand in your notes—not a native Multiloop score or faction field.
The faction block
The five-line pulse stays in your notes. Multiloop supplies the faction record around it; clocks, reputation scores, and structured “next move” fields are not part of that record.
1 · Durable record
2 · Current pulse
Keep it small
01 · Add
Create the record when the faction first matters, not while it is still background lore.
02 · Update
Change the pulse after a session that altered its goal, leverage, move, or posture.
03 · Retire
Set the faction inactive when it no longer has an open move. Keep its history without rehearsing it every week.
The faction record inside Multiloop
The pulse above is a manual method. Multiloop’s Faction record keeps the organization connected to its headquarters, members, hierarchy, visibility, description, DM Notes, and events involving current members.
Merchant · Active · Party
Mireport’s dominant contract guild, controlling dry storage, permits, and passage through the flooded coast.
Members
4 · Madric, 3 others
Parent faction
Mireport Factors
Event involving a member
Madric’s offer refused
DM Notes
Private operational context. Factions do not have a separate native Secrets field.
In this worked example, goal, leverage, next move, consequence, and party posture remain note conventions rather than structured faction fields.
Organize the faction around the pressure
Use the faction record for identity, hierarchy, members, headquarters, visibility, and history. Keep the small operational pulse in Description or DM Notes only when it helps you run the faction.
A free Multiloop account and campaign are required. The pulse is not a native field set and does not transfer automatically.
Use a document until hierarchy, membership, headquarters, private context, and campaign history become harder to reconcile by hand.
Before your first faction
Start with a goal, a current move, leverage, targets, the likely consequence of inaction, and the faction's current relationship to the party. Add history only when it changes a decision.
Track only factions currently capable of changing the campaign. Two or three active groups are easier to portray consistently than a complete directory of the setting.
Not as native faction fields. You can keep those as manual conventions in your notes, while Multiloop's faction records hold hierarchy, members, headquarters, visibility, status, and linked campaign context.
Faction pressure across the campaign
Use the stable record for what the faction is. Use a short private pulse for what it is doing now.