Organize factions around one event
Oh Story has factions respond differently to a shared event and uses third parties to test motives and logic. Some variants favor a power-ranking payoff. This example applies goals and responses without requiring the protagonist to overpower everyone.
Original story: heavy rain approaches a river port. A warehouse holds workers’ food alongside cargo guaranteed by the shipping guild. The port office plans to close it under an established flood procedure. Workers want their food; the guild wants accountable handling. The protagonist, a warehouse clerk, wants access to the food and reliable handover records.
The office controls closure, workers identify their sacks, and the guild can supply cargo witnesses. Introduce history and names only as needed to understand these actions.
Example: help comes with conditions
| Action | Motive | Result |
|---|---|---|
| Workers demand access now | The office fears a blocked counting passage | It requests delegates rather than a crowd |
| Clerk proposes separate handovers | The guild wants a chain of responsibility | It offers witnesses if each batch is signed for |
| Workers nominate delegates and identify sacks | The office now has manageable access | It permits limited handovers before the existing closure time |
The guild helps because the proposal protects its records. Representatives still owe other workers an account of what was retrieved and what remains.
The plan does not prove every sack is saved. An approaching deadline still requires priorities and explanations; paperwork cannot erase established constraints.
Record why an alliance changes
Use a planning card: shared event; each faction’s goal and leverage; trigger for a changed position; scope of cooperation; unresolved interests and next action.
Providing witnesses does not mean the guild supports every future decision. Accepting representative access does not mean workers abandon the remaining food. Limited cooperation preserves future differences.
If the protagonist intervenes for an ally, connect that choice to an established goal, responsibility or relationship. A larger opposing faction needs a connection to the current interests, rather than arriving merely to escalate the cast.
Check whether factions actually differ
Hide the faction names and compare reasons. If everyone only humiliates the protagonist or expresses surprise, interests have not entered the scene. Give decision-making factions distinct leverage; background crowds need not become long-running subplots.
Trace who heard the proposal, received conditions and acted. A private agreement is not public knowledge. One person’s commitment does not automatically bind an organization.
Removing a third party should reveal its function. If only applause disappears, reduce it to background. If evidence, resources or opposition disappear, establish why it provides them. The planning map supports scenes rather than replacing them.
FAQ
Must a third party support the protagonist?
No. Help, refusal or limited cooperation follows its own interests and needs an established reason.
Do it with the skill
Use $story-long-write to review a multi-faction scene. Map the shared event, goals, leverage and knowledge, then trace responses and alliance triggers. Separate temporary cooperation from lasting allegiance. Do not invent allies, authority or a larger villain. Material: [scene and settings].
Read the method: Faction motives and responses