Tutorials

Setting Up and Using Raid-Helper

Connect RaidHelper events to GearCheck readiness, build mappings, signed-up members, and flex coverage.

Scheduling

Who uses it: Group leads, managers, event coordinators
Where it lives: Dashboard > Scheduling > Raid-Helper and /raidhelper commands
Goal: Staff can check whether signed-up members are ready for what they selected and see alternate coverage options.

On This Page5 sections

Before You Start

Pro or higher access where RaidHelper is gated.
A RaidHelper server API key, not a user API key.
GearCheck builds that map to the event roles or labels.

Steps

Use the server API key
RaidHelper has user and server API keys. GearCheck needs the server-wide key from the non-user settings API key command so it can list server events.
Configure watched channels if needed
Auto-detect can work, but watched channels help GearCheck find event embeds reliably. If list lookup fails, paste the event ID or message link directly.
Map event labels to GearCheck builds
Role-specific events are easiest to match. Generic events may need saved mappings or staff interpretation. Keep mappings human-readable so group leads can trust the report.
Run readiness
Generate the report to see each signup, selected role/build, latest GearCheck result, readiness bucket, and gear check link.
Use flex coverage
When a role or build has a gap, check whether signed-up members have other verified builds that could cover it. GearCheck suggests possibilities; staff still make the roster call.