Titan Quest II Ability Slots Back in 0.7.1: Check Your Keybinds

Quick answer

The October 29 Titan Quest II 0.7.1 feature update restored two ability slots after the earlier reduction. Grimlore Games warned that some existing keybindings might reset and that a notice could appear when you launch the game. Check the assigned inputs before entering combat; do not assume a missing action means a skill was removed. The November 5 hotfix separately improved gamepad interaction with non-item objects during combat.

Check build and prerequisites

Applies to: PC Early Access 0.7.1-public.144378 (Oct 29), with 0.7.1-public.145090 hotfix (Nov 5)

  • You are playing Titan Quest II PC Early Access and have installed, or are about to install, the October 29 0.7.1 update.
  • You used custom keybinds, or a skill appears missing from your ability bar after updating.

Step-by-step answer

  1. Confirm which update you installed

    Check the game update history for the October 29 feature update, build 0.7.1-public.144378, or a later 0.7.1 build.

    Why this matters: The two-slot restoration is dated to that release; older May or summer screenshots show a different bar.

    Check: Your installed build includes the two restored slots.

  2. Look at the ability bar before changing anything

    Compare the currently displayed ability positions with your prior setup. Identify whether a slot is empty or a physical key no longer triggers its assigned action.

    Why this matters: An empty ability position and a reset key assignment are different problems and require different checks.

    Check: You can name the affected skill, slot and input rather than simply 'the bar broke'.

  3. Inspect your existing custom input assignments

    Use the game's current in-game controls or input settings and record the keys assigned to the affected ability slots. Restore your preferred assignments using the visible settings UI if they differ.

    Why this matters: The developer explicitly warned that certain user keybindings may reset and that a startup notice may appear.

    Check: The affected action has the intended assignment and no unwanted collision with another action.

  4. Test one action in a safe situation

    Return to a low-risk area and test the affected assignment without changing unrelated input options. Verify the ability itself appears on the bar.

    Why this matters: A menu assignment alone does not establish the action works as intended. Testing one variable avoids confusing hotkey issues with combat state.

    Check: The expected on-screen action now responds to its intended input, or you have a reproducible failing binding.

  5. If controller interactions fail during combat, check the later hotfix

    Check whether your version also includes the November 5 build 0.7.1-public.145090. Test a named non-item interactable in normal gameplay and record the object and combat state.

    Why this matters: The later hotfix specifically improved controller interaction with non-item objects during combat; it is separate from the October 29 ability-slot restoration.

    Check: You know whether the remaining problem is an ability hotkey or a context-sensitive controller interaction.

Original GGClue titan-quest-ii decision-flow illustration based on source-bounded rules; not gameplay footage.
Original GGClue evidence-based progression graphic; not an in-game map or gameplay screenshot.

What result should you see?

The two restored slots are visible and your chosen bindings work, or you have isolated a reproducible input problem with build and device details.

If your result is different

If a binding is correct in the menu yet still fails, do not assume the October 29 release's warning fully explains the bug. Preserve settings and report the exact action and build through the game's official support channel.

Important version, route and evidence differences

What actually changed in 0.7.1

The October 29 update restored two slots to the ability bar after a previous change removed them. This is a documented UI change, not proof that skills disappeared from a character. The same update warned that a small number of custom bindings might need attention, so older screenshots and preset guides can be misleading.

Keyboard and controller reports are not interchangeable

A re-assigned ability key is not the same as controller input failing on a chest, statue or quest object. The November 5 hotfix improved non-item interaction during combat, but no announcement says it repairs every controller, keyboard, UI or save issue.

Keep your report reproducible

Record your game build, keyboard/controller type, original intended input, current assignment, whether the failure happens only during combat, and the name of the affected action. Do not rename configuration files or recommend a reset command without developer evidence.

Frequently asked questions

Did Titan Quest II remove skills in the October 29 update?

The developer says it added back two ability slots. A missing or unused binding is not proof that a skill was deleted.

Do all custom keybindings reset?

No universal reset was announced. The patch says certain bindings might reset and players may see a startup notice.

Does the November 5 hotfix fix every controller input issue?

No. It specifically improves interaction with non-item objects during combat; the developer did not describe a universal input fix.

Sources and verification limits

Evidence reviewed 2026-11-07.

Official developer information supports the dated mechanics. This page has not been verified by GGClue hands-on gameplay; generic diagnostics are clearly distinguished from patch facts.

Not independently confirmed: GGClue has not reproduced the keybinding reset on a live client and has no verified click-by-click menu screenshot. The developer warns that some inputs may reset, not that all accounts or input devices are affected. This page does not claim an unverified config-file path, console command or reset shortcut.

Related GGClue answers