Documentation
Back to tutorials

Builds

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.

Who uses it

Build editors, event leads, raid 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.

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

1

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.

2

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.

3

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.

4

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.

5

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.

Launch Checklist

  • Each launch-critical build has Activity, Role, and Spec populated.
  • Repeated roles use the same label and key.
  • Template rows load from the pack/activity model without manual cleanup.
  • Signup-only rows are clearly unmapped when no build should be evaluated.

Common Pitfalls

  • Creating roles inside event creation that should live on the pack/activity model.
  • Using spec names as role names, which makes rosters hard to scan.
  • Relying on marketplace templates that require a pack the importing guild does not have.

Related