Community
Where long-form tables compare saga notes
Discussion norms and pointers—not an exhaustive directory of every Discord on earth.
One short arc well-closed beats a wall of unfinished trilogy notes on week one.
Readable arc boards and clear remote audio beat gorgeous binders nobody opens mid-session.
Norms worth copying
- Label spoilers for freshly released adventures.
- Separate rules questions from horror/bleed talk when tone is heavy.
- Credit freelancers when you share layouts or tools.
- Assume good faith; escalate to mods instead of pile-ons.
Track open threads, legacy favors, and calendar pressure like hit points—they are the saga engine.
Leave room for player plans that smash your year-two outline. Run with the better ending.
Good Epic-scale campaign orientation across fantasy and adjacent genres nights are built from procedures and shared expectations, not from hoarding every PDF. This desk emphasizes clarity over collectible hype.
For a chapter night: one saga beat players can push, one legacy callback, one calm off-ramp if energy dips.
For a chapter night: one saga beat players can push, one legacy callback, one calm off-ramp if energy dips.
Spoiler labels for finales. Room for lore and logistics. Escalate to mods.
Keep notes short enough to reread before a session. Long wikis that nobody opens are not preparation; they are archaeology.
When in doubt, run the smaller scenario, teach one procedure well, and leave room for player ideas that were not in your outline.