This page is a signpost, not a second rulebook. The binding text for conduct is still the main server rules, the PvP rules, and the living Staff Rulings document. Use this addendum to understand where to look when a situation is not spelled out in one paragraph.
- Wiki rules pages — Respect, PG-13, character policy, faction betrayal and capture, travel, QM policy, and the long-form Specific Powers sections (e.g. Force Sight, Force Bond) on the main rules article.
- Staff Rulings — Short, dated staff decisions that refine or clarify edge cases. When rulings and memory disagree, the wiki copy wins.
- DM instructions given to your plot — If a DM tells you how a spy plot, capture, or event works, follow that guidance and keep it IC/OOC separated as instructed.
Open a ticket on the SWLOR Discord (same pathway referenced throughout the rules for faction rank-ups, masteries, betrayal, and spying). Briefly state:
- What you want to do (IC and OOC)
- Who is affected
- Whether combat, capture, or permadeath risk is involved
Do not rely on general chat or faction OOC channels for a final call on policy.
- Faction betrayal, spying, or sabotage — see the main rules; staff may impose extra consent and consequence guidelines.
- Capture and long-term imprisonment — high risk to character agency; coordinate early.
- Non-supported powers and rare masteries — see Rank/Power Progression and Specific Powers on the main rules page.
- Force Bond — ticket before treating the bond as established.
- QM-led events that move faction military or political fronts — QM rules on the main page.
¶ Using // and OOC channels
The main rules already cover // chat and keeping IC matters out of OOC. This addendum only repeats the expectation: if a ruling fight is brewing, move it to tickets, not public Discord drama.
Staff: when you set a precedent that should bind future players, add it to Staff Rulings or extend the relevant section of the main rules. Players: cite the wiki link in tickets when asking “has this been ruled before?”