Raid Checklists [Checklist]

Like an airplane, a raid is made up of several parts that need to work together for the whole thing itself to work. Those parts need to be set correctly in order for that to happen.

Because of the daunting number of controls to set, airline pilots need to use checklists to ensure that every switch, dial and button are in the correct states for whatever the plane will be doing, whether taking off, cruising or landing. Similarly, several aspects of a raid need to be in specific states for the raid experience to be as smooth as possible. The following checklists mimic the pre-flight checklists used in airline aviation, listing the states of the various aspects of a typical raid.

There are checklists for:

• Preparing for the raid (pre-raid checklist)
• Preparing for a boss attempt (pre-boss checklist)
• Handling a raid wipe (wipe checklist)
• Concluding a raid (post-raid checklist)

Pre-raid checklist
The pre-raid checklist is used for preparing for a raiding a single raid instance. The raid group must be full, all consumables properly stocked and all raiders in the raid instance.

Pre-boss checklist
The pre-boss checklist is used for preparing for each and every boss attempt. Were any raiders to leave the raid group prior, replacements are to be found for them. In addition, all present players must be at the keyboard ready (often a ready check is used in determining this), all consumable buffs applied and crowd control (CC), interrupts and defensive cooldowns (CDs) assigned.

Wipe checklist
The wipe checklist is used for expediting a raid wipe should one be called. All raiders should endeavour to fail the attempt and CC, interrupt and defensive CD assignments should be abandoned.

Post-raid checklist
The post-raid checklist is used for concluding a raid session (which may include one or more raids on raid instances). The raid group is to be disbanded and the players return to their normal activities.

Changes in states
An aspect of the raid may or may not change when a certain stage in the raiding session is reached. The use of a checklist ensures that either:

• The state is changed
• Should a state not be changed, it is checked for changes that are not deliberate

The statechart diagram illustrates the changes in the state of a raider, whether tank, healer or damage dealer. The state may be due to change due to any combination of:

• A deliberate action (transition-name)
• The fulfillment of a condition (guard-condition)

In addition, an action (action-expression) may need to be performed before the change of the state completes. The transition label is in the syntax: [transition-name]"("[transition parameters]")["[guard-condition]"]/"[action-expression]