LazyGripInstallation
Installing GRIP-EMS takes about two minutes. The part most guides skip is what comes after. There are in-game settings that have to be configured before anything will work, and none of them are set correctly by default. This page covers the install steps and the most critical setting. The full settings breakdown is on the Settings page.
Step 1: Download and enable
Download from CurseForge, Wago, or WoWInterface
GRIP-EMS is free on all three platforms. Use whichever addon manager you already have.
Enable the addon in-game
At the character select screen, click AddOns in the bottom left corner and make sure GRIP-EMS is checked. Log into your character.
If you do not see GRIP-EMS in the list, your addon manager did not install it correctly. Try a manual download and drop the folder into your World of Warcraft\_retail_\Interface\AddOns directory.
Step 2: The three settings you must configure
This is what most installation guides do not tell you. GRIP-EMS needs three specific WoW client settings to be correct before sequences will fire. None of them are set to the right value by default. If you skip this section and wonder why pressing your keybind does nothing, this is why.
Fix your Cvar Health, the most important step
GRIP-EMS fires through WoW's key-down event system. By default WoW uses key-up, which means your sequence registers the press only when you release the key rather than when you press it. At 150ms intervals this is the difference between a functioning rotation and nothing happening at all.
Open the GRIP-EMS settings and navigate to the Cvar Health tab:
Go to the Cvar Health tab. If the status indicator is not green, click Fix. That sets ActionButtonUseKeyDown to enabled.
Verify your SpellQueueWindow
The SpellQueueWindow controls how many milliseconds before a GCD ends WoW will accept your next cast input. The Cvar Health tab shows your current value and flags it if it looks off. The default of 400ms is fine to leave alone for now. The full explanation of what SQW does, why it matters, and how to tune it for your connection is on the Settings page.
Set your click rate
GRIP-EMS advances one step per keypress. Your hardware or software needs to send repeated keypresses at a consistent interval. The right value depends on your setup but 150ms is a reliable starting point that works across most hardware and latency combinations. If you are using Razer hardware, set your repeat rate to 150ms in Synapse.
GRIP-EMS has a built-in Tempo Advisor that analyzes your actual click rate from log data and tells you whether to click faster or slower. Once you have a sequence running and some combat data, use it.
What you will not see and why
GRIP-EMS does not put a button on your action bar. This trips up almost every new user who comes from GSE, which does create a draggable button that you place on a bar and bind. GRIP-EMS works differently. You bind a key directly to a sequence inside the addon, and the keybind fires the sequence without going through the action bar at all. There is nothing to drag. If you are looking for a button to appear and it is not appearing, that is expected behavior and not a bug.
To bind a key to a sequence, open the sequence in the GRIP-EMS editor, go to the Keybinds tab, and assign a key there. The bind is stored per-spec, so switching specs gives you a clean slate for a different rotation on the same key.
Quick sanity check
Before moving on, confirm these four things are true:
Troubleshooting common problems
Keybind is set but nothing fires
Run /gems settings and go to the Cvar Health tab. If the Fix button is visible, click it. This solves the majority of new-user keybind problems. If everything shows green and the sequence still does not fire, check that you have a target selected and that the sequence has a keybind assigned in the Keybinds tab inside the editor, not just in WoW's default keybind menu.
Sequence fires once then stops
GRIP-EMS requires continuous repeated keypresses, not a single press and hold. Your hardware or software needs to be configured to send repeated keypress events. At 150ms that is roughly 6 to 7 presses per second. A single press fires one step and stops.
Sequence shows greyed out after a /reload in arena or M+
This was a known bug where the addon waited on a match flag that never cleared mid-fight, leaving sequences inactive until the match ended. It is fixed in v2.1.17. If you are hitting this, update GRIP-EMS through your addon manager. Clicking a greyed-out sequence row in the editor also re-activates it on the spot in v2.1.17 and later.
Sequence key stops working randomly while grinding, mount and dismount fixes it
This was a bug where the game skipped its own bar-change signal after messy dismounts, leaving a stale keybind eating keypresses. A watchdog fix was added in v2.1.16 that checks actual mount and vehicle state rather than trusting the bar-change signal. Update to v2.1.16 or later. You can run /gems debug to watch the watchdog catch a stale bind in real time.
Sequence key dies after skyriding or leaving a vehicle
Fixed in v2.1.14. The keybind suspend-and-restore now runs inside the secure engine and survives skyriding, vehicle exits, and possession. Update GRIP-EMS if you are on an older version. As of v2.1.16 you can also press your sequence key while skyriding over an attackable target and it will dismount and fire step 1 in a single press.
Sequence key fires mid-air or vehicle keys are dead on first flight of the session
This was a first-takeoff bug where ground binds stayed live while airborne or vehicle keys never activated at all. Fixed in v2.1.20. The watchdog now heals the bar swap at takeoff and restores it on landing. Update GRIP-EMS if you are hitting this on the first flight of every login.
Another addon keeps stealing my sequence keybinds
Some addons override-bind the same keys GRIP-EMS uses for vehicles and skyriding, and whoever loads last wins. As of v2.1.20, the Keybinds tab inside the editor names the contending keys directly in the vehicle and pet battle sections so you can see exactly which addon is causing the conflict. GRIP-EMS does not fight for the bind, it just tells you who took it.
Lua error spam about tainted table iteration in arena or BG
This is typically caused by another addon tainting the environment before GRIP-EMS runs, not a GRIP-EMS bug itself. A common culprit is PvPCallouts. Try disabling other addons one at a time with BugSack and BugGrabber installed to identify the source. If the error text says execution tainted by GRIP-EMS specifically, file a bug report in the Discord with the full error and your addon list.
Commands worth knowing
/gemsOpens the GRIP-EMS sequence editor/gems settingsOpens settings including Cvar Health/gems bindsShows all currently bound sequences for your active spec/gems debug onEnables debug output to chat, useful when something is not firing/gems debugwindowOpens the debug window with additional diagnostic information/gems validateRuns spell validation across all your sequences and reports stale spells/gems revalidateForces a full revalidation, useful after a patch or respec