World Evolution
AX.C.16.08.04
The setting is not static scenery. Antagonists are pursuing their goals. Factions are competing for resources and influence. Environmental and political processes are developing. Whether or not the players engage with any of these, they continue.
Maintain a small number of active world threads at any time, two to three is the practical maximum. More than that becomes difficult to track consistently; threads that aren't tracked consistently stop evolving and become dead ends that erode the world's credibility.
Each thread has four components:
Force: What is acting, a faction, an antagonist, an environmental process, an unresolved consequence from a prior arc.
Current action: What the force is doing right now, specifically. Not "the faction is expanding", "the faction is negotiating to acquire the eastern district's water access, which will complete by session's end if the players don't intervene."
Trajectory: Where the thread is heading if unchecked. This gives the GM something concrete to advance at the table when players engage with the thread, and something concrete to resolve in the background when they don't.
Intersection: When and how the thread surfaces into the players' awareness. Some threads surface through direct encounter. Others surface through NPC behavior shifts, environmental changes, or rumors. The intersection is the scene or moment where the thread becomes visible, not necessarily where it becomes urgent.
When the players resolve a thread, or when it resolves itself by running its trajectory to completion, introduce a new one. The count stays low, but the world's complexity accumulates. Players who were in the same city three arcs ago are in a meaningfully different version of it now.
Opportunities close. A contact who offered to help won't wait indefinitely. A faction advantage that could have been taken is eventually taken by someone else. A piece of information that was available for two sessions becomes buried or acted upon. This is not a punitive design; it is a consequence of the world having processes that don't pause. Players who learn that the world moves without them engage more actively with threads that are currently open.
Arc breaks are the natural moment to advance background threads visibly. When the campaign moves from one arc to the next, particularly if downtime is involved, the threads that have been developing in the background should surface in some observable form. The world the players return to should show the time that passed.