Before you change bindings
Confirm that your controller already sends input to WoW and that ConsolePort is enabled for your game client. If this is the first installation, follow the ConsolePort setup guide. For Classic, use the client compatibility checklist.
Keep a keyboard and mouse available. Note or take screenshots of the assignments you want to preserve before replacing them. Work on one character and one controller during the first pass so you can tell which change affected the result.
The plan below is a suggested starting method, not a class rotation, ConsolePort preset or claim that one layout is best for everyone.
1. Group actions by how you use them
Start with the tasks you need to perform while moving and looking around. Choose positions you can reach comfortably on your own controller, rather than filling every available slot immediately.
| Action group | Planning question |
|---|---|
| Movement and camera | Can you move, stop and look without reaching for an action control? |
| Frequent abilities | Which small set do you use often enough to learn first? |
| Targeting and interaction | Can you choose the intended target and interact without losing your place? |
| Situational abilities | Which actions can you reliably find on a deliberate modifier combination? |
| Menus and navigation | Can you confirm, go back and return to normal control? |
Leave an action unassigned during this first exercise if you cannot yet reach it reliably. Add it deliberately once the smaller layout is familiar. Keep another input method ready for anything you have not mapped.
2. Build the base layout first
In ConsolePort’s configuration, choose the button or action slot you want to change and assign the intended ability or function. Its official project shows binding and action-bar configuration together; the exact controls and labels depend on your release.
Try one familiar action before assigning the rest. Verify its actual effect in WoW, then release the control and repeat. For targeting or interaction, check the selected target as well as the button you pressed.
A simple written record helps: control position, assigned action, and whether you tested it. Use the names or positions displayed on your own controller instead of translating from someone else’s button lettering.
3. Add one modifier layer at a time
Choose a shoulder or trigger combination that your ConsolePort setup uses as a modifier. Assign a small group of related actions to that layer, then practice entering and leaving it before adding another layer.
As a planning example, you could keep a familiar frequent action on a base button and put a situational action on that same button while holding one modifier. Those are two separate assignments. Select the abilities yourself for your character; this example supplies no default bindings or performance recommendation.
Test three states: the base button alone, modifier plus button, and the base button again after releasing the modifier. A correct modified action is only half the check if the controller remains on an unexpected layer afterward.
If the result differs from your plan, use the wrong-action and modifier troubleshooting guide before adding more assignments.
4. Test the layout as a sequence
- In a quiet place, move and come to a complete stop.
- Look around, then return the camera control to neutral.
- Use the base action you assigned and confirm the intended result.
- Hold one modifier, use its assigned action, release both controls, and retest the base action.
- Choose a target or interaction appropriate to your test, then open and leave a menu.
Use the full setup checks when bringing Thumble into the session. If movement or camera direction is wrong, check camera behavior and touch calibration separately from spell assignments.
Repeat the sequence after each small group of changes. If a new assignment causes trouble, restore that assignment from your notes and retest before changing another part of the layout.
5. Check Thumble labels after saving
For matching Thumble addon and receiver builds, type /reload in WoW after binding changes so the receiver can read the saved snapshot. Where available, keep the receiver’s ConsolePort sync enabled and confirm the selected phone controller is the intended one.
This updates presentation from saved information; it is not a live cooldown display. If the game action is correct and the phone label is stale, follow the spell-label sync checks. Editing a displayed label is not a substitute for assigning the action in WoW.
Public Thumble phone apps are coming soon. The documented companion-addon 0.1.2 release targets Classic Era 1.15.9; check the matching release scope. Offline phone practice cannot verify that WoW accepted a binding.
Sources and scope
Checked October 26, 2026: ConsolePort’s official project and configuration examples, Thumble setup reference and companion-addon release scope.
The action grouping and practice sequence are Thumble’s suggested planning method. They are not an official ConsolePort preset, a tested class build or a universal button map.
Get ready for phone controls
The Thumble phone apps are coming soon. Get launch updates while you prepare your WoW setup.