Why don't my UI buttons respond to clicks?

Because the click isn't reaching the button or isn't triggering its action: something is blocking the input (an invisible or overlapping element, or a full-screen raycast blocker, intercepting the click, the most common cause), the button is disabled or the UI isn't receiving input focus, or the button's event handler isn't connected (so clicks register but do nothing). It's either not getting the click or getting it but doing nothing.

How do I find why a button isn't working?

Check whether the button shows any interaction feedback (hover/press states): no feedback means input isn't reaching it (something is blocking it or it lacks input focus, check the UI hierarchy for overlapping/invisible elements over it); feedback but no action means the handler isn't connected. Inspect the UI hierarchy for blockers, verify the button is enabled and focused, and confirm its event handler is wired up.

Why is an invisible element blocking my buttons?

A common cause of unresponsive buttons is an invisible or transparent UI element on top of them intercepting clicks, often a transparent panel, an overlapping element, or a leftover full-screen 'raycast blocker' that catches input. The player clicks the button but the click hits the invisible element instead. Find and remove or disable the blocking element (or stop it from blocking input meant for the button) to fix it.

How to Fix UI Buttons That Don't Respond

Quick answer: UI buttons that don't respond mean the click/tap isn't triggering the button's action. Causes: something is blocking the input (an invisible or overlapping element on top intercepting the click, a full-screen raycast blocker), the button is disabled or not receiving input focus, or its event handler isn't connected (so clicks register but do nothing). Check for blocking elements, verify the button is enabled and receiving input, and ensure its handler is wired up.

A UI button that doesn't respond is a basic but blocking bug, the player clicks and nothing happens, and they can't do whatever the button was for. The click is failing to reach the button or trigger its action, and the causes are a small, checkable set: something blocking it, the button not receiving input, or its action not connected.

Why Buttons Don't Respond

For a button to work, the click/tap must reach it and trigger its action, and that can fail a few ways. Blocked input, something is intercepting the click before it reaches the button, an invisible or transparent element on top of the button, an overlapping UI element, or a full-screen 'raycast blocker' (an invisible panel that catches input), so the click hits that instead of the button. This is a very common cause, an unseen element eating the clicks. Not receiving input/focus, the button is disabled, not interactable, or the UI isn't receiving input focus (something else has input focus), so the button doesn't get the click. Handler not connected, the click reaches the button but its event handler/action isn't wired up (or is wired wrong), so clicking does nothing.

So an unresponsive button is either not getting the click (blocked, or not receiving input) or getting it but doing nothing (no handler). The most common culprit is an invisible blocking element intercepting the input.

How to Diagnose It

Check the categories. Is something blocking the button, an overlapping or invisible element, a raycast blocker, on top of it intercepting clicks? (Check the UI hierarchy/layout for anything over the button, even transparent.) Is the button enabled and interactable, and is the UI receiving input focus? Is the button's event handler actually connected? Test: does the button highlight/react on hover/press (suggesting it gets input, so the handler may be the issue) or not react at all (suggesting input isn't reaching it, blocked or not focused)?

Whether the button shows any interaction feedback (hover/press states) is a key clue, no feedback means input isn't reaching it (blocked/focus); feedback but no action means the handler isn't connected. This is usually reproducible directly (click the button), so the diagnosis is inspecting the UI hierarchy (for blockers), input/focus state, and handler connections. Player reports confirm which buttons and contexts are affected.

How to Fix It

Fix the failing link. For blocked input, find and fix the blocking element, remove or disable the invisible/overlapping element or raycast blocker that's intercepting clicks (a transparent panel covering the button, a leftover full-screen blocker), or ensure it doesn't block input meant for the button, this resolves the most common cause. For not-receiving-input, ensure the button is enabled and interactable and that the UI/button is receiving input focus (give it focus, ensure nothing else is capturing input). For an unconnected handler, wire up the button's event handler to its action correctly so clicking does what it should.

Verify by clicking the button and confirming it both reacts (hover/press feedback) and performs its action. Test in the actual contexts where it failed (sometimes a blocker only appears in certain states). Unresponsive buttons are usually quick fixes once you identify which of the few causes it is, with an invisible blocking element being the most common and the first thing to check.

Unresponsive buttons aren't getting the click (blocked by an invisible element, or no input focus) or aren't triggering their action (handler not wired). Check for blockers first, it's the usual culprit.