Event Design

Output Contract

Return sections in this exact order:

1. Context assumptions
2. Content draft (event/situation, explicitly labeled)
3. Localization keys
4. Lore rationale
5. Risks and open questions
6. Validation checklist

Design Rules

• Keep triggers explicit and bounded.
• Avoid farmable loops and permanently stacking rewards unless intended.
• Keep options meaningful, with visible trade-offs.
• Add localization for title, description, and every option.
• For situations, define clear phase transitions, catalyst cadence, and termination gates.
• Prefer minimal edits over broad rewrites.

Validation Checklist

• If event content exists: event id is unique and follows project naming style.
• If situation content exists: phases, catalysts, and endings are all declared and reachable.
• Trigger cadence is safe (no accidental frequent re-fire).
• Effects are proportional to cost/risk/timing.
• AI can take at least one sensible option.
• Localization keys exist for all visible strings.

Anti-Patterns

• Unbounded yearly or monthly reward events without cooldown or flag gates.
• Hidden effects that drastically change progression without player feedback.
• Overly global effects for a local narrative beat.
• Situations that never end because catalysts exist without end-state checks.
• Mixing lore speculation with canon claims.

Example Prompts

• Create an event when a frontier kingdom is formed, with one prestige option and one stability option.
• Rework this event to reduce trigger spam and add clear trade-offs.
• Draft localization and event text for a one-time crisis event tied to a global flag.
• Create a multi-phase situation with active/lull cycles, 4-6 catalysts, and two terminal outcomes.