Community
Where creators compare powered-by literacy notes
Discussion norms and pointers—not an exhaustive directory of every Discord on earth.
Powered by Zweihander writes in a license literacy editor register: concrete procedures first, lore tourism second, and zero invented prices.
Date which program PDF you checked and what you marked as out of scope. Co-authors need a trail.
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.
Date which program PDF you checked and what you marked as out of scope. Co-authors need a trail.
Guides for literacy; Glossary for powered-by vocabulary; Resources for primary doors. Then verify the cite.
Table procedures from other desks can help your session—do not confuse that with a publishing grant.
One primary license link, one trademark check, one attribution reminder—before you paste a logo.
One-page citation checklist. If a question repeats, ink the answer—then still verify primary terms.
One-page citation checklist. If a question repeats, ink the answer—then still verify primary terms.
Related desks in this neighborhood
Play and community siblings (.cc, .org, crate, reforged, store) cover table practice beyond licensing.
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.