Guild operations guide
How to manage an MMORPG guild without burning out
A practical operating model for MMORPG guild leaders covering roles, communication, attendance, loot, records, and review cycles.
- Author
- ForgeKeep product team
- Published
- Updated
Start with an operating agreement
Write down the guild’s purpose, time commitment, leadership roles, and decision process before choosing tools. Members should know what officers decide, what requires a vote, and how disputes are reviewed.
Keep the agreement short enough to use. A clear one-page charter is more useful than a rulebook nobody reads.
- Purpose and target play style
- Leadership responsibilities
- Expected member conduct
- Decision and appeal process
Separate communication from the system of record
Discord is excellent for conversation and alerts, but chat history is a weak database. Use a structured record for roster changes, attendance, points, loot awards, inventory movements, and financial entries.
Link the two systems so an alert leads members to the current record, rather than copying a new version into another channel.
Design roles around real responsibilities
Grant the smallest set of permissions each role needs. A raid caller may need boss and attendance access without financial access; a treasurer may need ledger tools without member administration.
Review elevated access after leadership changes. Removing an outdated role is as important as granting a new one.
Run a predictable weekly review
A short recurring review keeps small inconsistencies from becoming political problems. Check roster changes, unresolved attendance, point adjustments, pending loot, inventory discrepancies, and treasury entries.
Publish decisions and owners. The goal is not more meetings; it is fewer surprise decisions.
- Resolve attendance exceptions
- Approve point adjustments
- Close pending loot decisions
- Reconcile inventory and treasury
- Publish next week’s boss plan