Tracking Recurring NPCs
AX.C.16.03.04
An NPC who appears more than once needs three tracked fields maintained between sessions:
Current want: What are they pursuing right now? This may evolve as events progress. An NPC whose obstacle was removed will shift to a new want. An NPC who suffered a setback may have revised their approach or redirected their efforts.
Player history: What have the players done that this NPC knows about and cares about? Not a complete log, only the events the NPC would have observed, heard about, or been directly affected by. This is the input to disposition.
Current disposition: How does this NPC currently regard the players? Disposition runs from actively helpful to actively hostile, and it should shift in response to player history. An ally the players ignored at a critical moment is a cooler ally next time. A neutral contact who received unexpected help without being asked has reason to reciprocate. A hostile NPC who was treated with respect despite the conflict may carry residual complexity into future encounters.
The world should remember what the players have done even when the players don't. When a recurring NPC reacts to events the players have half-forgotten, it signals that choices have weight, which is the foundation of meaningful play.
Tracking doesn't require a dedicated system. A single line per recurring NPC, want, one relevant event, current disposition, is sufficient. Update it after any session where the NPC appeared or where something happened that would affect them.