WoW Classic controller setup on Mac: check your client first

What is supported by which component?

A controller setup has several independent parts: the controller’s connection to macOS, game input in your WoW client, ConsolePort’s interface and bindings, and any optional companion addon. One working part does not establish compatibility for all the others.

ConsolePort’s official release listing covers multiple game flavors. Check the file you install rather than treating the project name or a “Classic” label as a match for your client.

1. Identify the client you actually launch

Write down the game edition and version from the game you are using. “WoW Classic” alone is not precise enough when checking an addon release. Keep Classic Era, other Classic clients and Retail distinct, even if more than one is installed on the same Mac.

In CurseForge, select that same WoW installation before searching for or updating addons. Its official setup documentation explains that WoW instances are managed separately and describes scanning for a missing game or adding it manually.

If the addon appears in CurseForge but not in the game’s AddOns list, recheck the selected installation. Changing bindings will not fix an addon installed into a different copy of WoW.

2. Choose the controller path

Physical controller

Connect the gamepad to the Mac using its supported wired or Bluetooth method. Follow Apple’s controller connection instructions, then use a ConsolePort release matching your game. Verify input in WoW before spending time assigning a full action layout.

Thumble phone controls

WoW runs and displays on the Mac; the phone supplies controls. Thumble does not stream the game video to your phone. Check the current requirements and availability before preparing the receiver. Public iPhone and Android downloads are coming soon.

For companion features, use the Thumble addon installation guide and its release details. If your client differs from Classic Era 1.15.9, check for an explicitly matching release before assuming the documented addon will load or sync. Changing a file’s version declaration is not evidence of compatibility.

The phone versus physical gamepad comparison explains the practical differences between these input methods.

3. Configure and verify one character

1. Install and enable the matching ConsolePort release in the intended client, then follow the ConsolePort setup steps.
2. Keep a keyboard and mouse available. Begin with movement, camera, jump and one familiar action.
3. Test the base action and each modifier separately, releasing shoulders and triggers between checks.
4. Navigate a menu and return to normal control. Repeat the checks after changing client, addon or controller versions.

With supported Thumble sync builds, use /reload after binding changes to save a snapshot. Labels are not a live cooldown feed. If input works but the phone picture is stale, use the label and character sync guide.

Common Classic setup questions

Does a ConsolePort release for Retail also prove Classic compatibility?

Check that file’s supported game versions. A project can publish for several flavors, but the version you install must match the client you launch. Likewise, ConsolePort compatibility does not extend the release scope of the separate Thumble addon.

Can I use the documented Thumble addon on another Classic patch?

The documented 0.1.2 release targets Classic Era 1.15.9. For a different patch or branch, look for a matching release and its notes. This guide does not claim those other clients were tested.

Which guide should I use if controls still fail?

For no game input, start with controller detection on Mac. For an unexpected spell, use the action and modifier checks. Include the exact game, ConsolePort, receiver and companion-addon versions when contacting support.

Sources and scope

Checked October 26, 2026: ConsolePort official listing and files, CurseForge installation and instance management, Apple controller connection instructions, and the documented Thumble addon release.

This is a release-matching checklist. Successful play still requires verifying your controller in the game; no broad Classic or Retail gameplay certification is implied.