Tutorials

Roles and Specs

Model a guild's pack as activities, roles, and exact build specs so builds, scheduling templates, readiness, and rosters all use the same source of truth.

Builds and Evidence

Who uses it: Build editors, event leads, group leads
Where it lives: Dashboard > Game Packs > Pack and Dashboard > Scheduling > Templates
Goal: A pack whose builds can feed scheduling templates without retyping roles or creating conflicting labels.

On This Page5 sections

Before You Start

Permission to edit packs and builds.
A pack with at least one activity.
A rough role model for the activity, such as Tank, Healer, DPS, Support, Flex, or game-specific equivalents.

Steps

Create roles at build creation time
When adding a build, fill Activity, Difficulty where relevant, Role, and Spec. Role is the broad function. Spec is the exact build detail: gear, weapons, passives, skills, and other game data.
Reuse existing role names
Use the role suggestions in the pack page instead of retyping slight variations. This keeps scheduling templates from splitting Tank, tank, and Main Tank into accidental separate buckets.
Use icons where they help scanning
Build icons can carry into scheduling template rows. Use Unicode or registered custom Discord emoji so event embeds and roster views are easier to scan.
Load the model into templates
In the template workbench, choose the pack/activity/difficulty, then load matching builds. GearCheck turns those build records into signup rows with optional readiness mappings.
Keep signup-only templates valid
Manual roles are still valid for communities that only want event organization. They just skip readiness and build-specific scoring until mapped.