Home / WoW: Forever / Controller settings and keybinds

WoW: Forever / Controller authority

WoW Forever controller settings and keybinds: a practical setup guide

Blizzard has announced official gamepad support for WoW: Forever. The beta points toward face and D-pad actions, trigger-modified layers, shoulder targeting, and controller navigation, but the exact current interface still needs a client check. Start with exposed controls, bind by job, and test anything that could stop an attack or lose a target.

Start the setupOpen the WoW hub
StatusPrepared reference; verification pending
Reviewed
Current-build verificationPending direct pass
OfficialGamepad support announced
External leadsReports need reproduction
Current-build checkPending direct verification
RefreshAfter every beta patch

This page separates what Blizzard announced, what external testers report, and what a current-build test still has to establish. Nothing below promises that every input is rebindable, that every handheld is supported, or that a beta workaround is universal.

Announced support

Blizzard’s Forever panel recap says official gamepad support is planned. That establishes the product direction, not a complete current button map.

External hands-on lead

September 19–20 forum feedback describes Windows 11, Switch 2 Joy-Cons over wireless, and an Undead Paladin played to level 10. The build string, exact spec, and reproduction sequences were not supplied.

Current-build verification

Exact menu paths, editable inputs, target cycling, persistence, reset, and handheld behavior still require a direct client pass. Keep those details gated rather than presenting them as settled facts.

Quick start

Build a small, reversible first profile.

Use this as a test sequence until the exact current-build UI has been captured.

  1. Connect before launch. Record controller model, connection type, WoW: Forever build string, date, class, spec, and content.
  2. Find the controller interface. Record the exact menu path and a screenshot. The package does not authorize a guessed path.
  3. Start with low-risk positions. Use exposed controls for movement and a low-consequence ability before changing interrupts, targeting, or emergency actions.
  4. Build the layers the UI exposes. Check neutral, left-trigger, right-trigger, and both-trigger states; do not assume a permanent count or default map.
  5. Test the failure cases. Try hostile, friendly, party, interact, jump, radial, bags, chat, open world, and a busy group scenario.
  6. Save a dated record. Capture the layers and page state. If the client offers an export, verify it. Otherwise keep the worksheets below.

Beta note: September reports disagree about whether the usable action space is 28 or 32 positions. That conflict is why this guide uses job groups and a current-UI verification table instead of a fixed default chart.

Current-build gate

What must be verified before a settled instruction.

Use one row per observation and keep external reports separate from a reproducible current-build check.

WoW: Forever controller verification matrix as of September 20, 2026
ControlCurrent statusRecord required
Build and deviceDirect verification pendingBuild string, date, controller model, connection type, class/spec, content.
Controller interface menu pathNot verifiedExact menu path and current-build screenshot.
Neutral / LT / RT / both mapNot verified; external counts conflictEvery input, default action, editable state, and layer count from the current UI.
Locked versus rebindable controlsExternal lead onlyInput, default action, editable state, and a reproducible reset or restore result.
Targeting and radialExternal lead onlyThree hostiles, dense pack, enemy-self-enemy, party both directions, friendly-to-enemy, NPC/object, and focus recovery.
Mouse and keyboard fallbackNot verifiedMid-combat swap, bags, chat, menus, disconnect, relaunch, logout, and patch persistence.
Backup, reset, and restoreNot verifiedReal Forever path or command, reset scope, successful restore, and whether keyboard/controller/both are affected.
Handheld gatesNot testedInstall, login, detection, UI text, targeting, radial, bags, talents, chat, suspend/resume, reconnect, patching, battery, and performance.

Trigger layers

Think in jobs, not fixed defaults.

Face buttons and the D-pad are the starting vocabulary. Trigger modifiers add deliberate layers when the current interface exposes them.

Four WoW Forever controller layers: no trigger for constant actions, left trigger and right trigger for frequent jobs, and both triggers for deliberate actions.
The package visual is a planning map, not a promise of current default buttons. Confirm the labels and editable positions in the client.

Closest inputs

No trigger

Start with constant actions such as a main filler, interrupt, movement, or target switch only after checking which controls the client exposes.

One trigger can hold a frequent rotation or role-utility job. The other can hold defensives, healing, control, or a second role job.

Deliberate inputs

Both triggers

Reserve the most deliberate layer for mounts, consumables, rare utility, travel, or actions that should not fire accidentally.

A demo may show eight positions per layer or a combined total of 28 or 32. Use the current UI, not the demo, as the authority.

Locked versus rebindable

Check each input; do not assume a blank canvas.

External reports describe locked unmodified face-button functions while modified layers expose more choices. That is a lead to reproduce, not a universal rule.

Current-build input audit worksheet
InputDefault actionEditable?Evidence / retest
Neutral face / D-pad
Left-trigger layer
Right-trigger layer
Both-trigger layer
Shoulders / sticks / menu

Do not add a console workaround, a Retail configuration path, or an addon profile here. If an input is locked in the current build, document the default and make the tradeoff explicit.

Targeting

Target cycling needs a real failure test.

Hands-on demos show shoulder cycling and manual lock as the intended shape. Community reports also describe mixed-action and auto-attack problems. Keep both as test prompts until reproduced.

Reproduction sequence

  1. Record model, connection, build, class/spec, and zone.
  2. Cycle three hostiles, including a dense pack.
  3. Try enemy → self → enemy and friendly → enemy transitions.
  4. Cycle party targets in both directions, then an NPC or object.
  5. Lock a target manually, attack, swap, and recover focus.
  6. Check whether auto-attack stops and whether mouse input recovers.

Safe interim rule

Keep a manual target option and mouse fallback available until the sequence passes. Do not state that shoulder cycling is reliable for every class, role, content type, or target mix.

Record the exact sequence when it fails. A community report that says “targeting is rough” is a lead, not a reproduction.

Bind by job

Keep the priorities stable while the class list changes.

Use the same failure-cost logic for controller and keyboard. The action names change by class; the jobs do not.

Keybind priority map moving from frequent or urgent actions to role-critical actions and then rare or costly actions, with closest, one-modifier, and deliberate binding zones.
Keep urgent actions closest, group role-critical actions under one modifier, and put rare or costly actions behind a deliberate layer.

Closest inputs

Main builder or spender, interrupt, movement, short defensive, emergency action, and target switch.

One trigger

Secondary rotation, long defensives, cleanse, crowd control, role tools, and frequent cooldowns.

Both triggers

Mounts, consumables, professions, travel, rare utility, and anything costly to trigger accidentally.

For the broader keyboard, mouse, and role map, use the general WoW keybind guide. This page keeps the Forever-specific verification and worksheets here instead of replacing that generic ownership.

Print or save

Worksheets for a dated first pass.

Fill these in after each meaningful change. Blank cells are safer than guessed defaults.

Controller worksheet
JobActionNeutralLeft triggerRight triggerBoth triggersTested
Main rotation
Interrupt
Movement
Short defensive
Emergency action
Targeting
Role utility
Travel / out of combat
Keyboard and mouse worksheet
JobPrimary keyModified keyMouse optionTested in combat
Main rotation
Interrupt
Movement
Defensive
Emergency action
Target self / party / enemy
Role utility

If the physical problem is a mouse or keypad rather than a controller, keep the hardware decision on the Forever gear guide and use the MMO mouse setup guide for the generic button map.

Build-dated issue ledger

Use reports as leads and keep the workaround narrow.

These are current beta concerns to reproduce, not universal behavior.

External reports and safe interim advice
LeadEvidence statusSafe interim adviceRetest gate
Unmodified face buttons may be lockedCommunity reports, September 17–20Audit each neutral input; do not promise every face button can be rebound.Current-build input table with a reproducible restore.
Mixed-action targeting feels awkwardDemo and community leadKeep manual target and mouse fallback.Hostile, friendly, party, dense-pack, and focus sequence.
Auto-attack or mouse input may stopCommunity issue leadTest in low-stakes content and log the recovery sequence.Build, class/spec, exact inputs, and relaunch/disconnect result.
Menus, bags, and text may be slowerCommunity feedbackKeep keyboard and mouse nearby; do not claim mouse-free play is universal.Chat, bags, talents, inventory, and menu pass.
Action space may be tightReports conflict on 28 versus 32 positionsBind by job and leave rare or costly actions deliberate.Current UI screenshot and complete layer count.

Backup and reset

Do not copy a Retail reset path.

The exact Forever backup file, command, and reset scope are not verified. Until a real restore succeeds, screenshot every layer and worksheet, change one group at a time, and log logout, relaunch, disconnect, crash, and patch behavior.

Before resetting, capture the current state. After resetting, confirm whether controller, keyboard, or both were affected. Add a public restore procedure only after it works on the current build.

Handheld gate

Promising is not the same as supported.

No official handheld support or performance claim is made here.

Until tested, say “promising for handheld PCs,” not “Steam Deck supported.” A handheld pass must cover install, login, controller detection, UI text, targeting, radial, bags, talents, chat, suspend/resume, reconnect, patching, battery, and performance. Console support is not implied.

Hardware recommendations stay on the Forever gear guide. Graphics, FPS, and display tradeoffs stay on the ultrawide UI guide. This page owns the Forever input settings and verification method.

Method and sources

What is known, and what is still gated.

Reviewed September 20, 2026. Blizzard’s official panel recap is the source for announced gamepad support. Forum reports and third-party coverage are external leads. Exact menu paths, complete input maps, locked-control rules, targeting guarantees, backup/reset procedures, and handheld verdicts remain open pending a direct current-build check and are not presented as settled.

Official and external referencesBlizzard: WoW: Forever What’s Next panel recapBlizzard: WoW: Forever launch and beta announcementOfficial forum lead: controller major issuesOfficial forum lead: controller support feedbackWarcraft Tavern: built-in controller support coverage