Fix: Construct 3 Mouse Click Firing Twice on Touch

Here is how to fix Construct 3 actions that run twice on tablets and phones — once for the touch event, once for the synthesized mouse event the browser also fires. The double-fire is invisible on desktop where touch is absent. On mobile, every tap costs the player two of whatever the action did. The fix is consolidating input handling on a single source.

The Symptom

A button on a tablet plays its sound twice per tap. Or a counter increments by 2 per click. Or a dialog confirms then immediately re-confirms. Desktop with mouse-only input behaves correctly.

What Causes This

Browser synthesizes mouse from touch. Web browsers fire touchstart, touchend, then often a mousedown/mouseup/click trio for every tap to support legacy code. Construct 3 surfaces both.

Both Mouse and Touch handlers active. Your event sheet has Mouse On Click and Touch On Tap on the same target. Both fire.

Touch object Mouse Input setting. The Touch object has a Use Mouse Input property that lets desktop mouse drive Touch events too. With it on, you can rely on Touch alone for both platforms.

The Fix

Step 1: Use Touch with Mouse Input. Add a Touch object to the project. Open its Properties and enable Use Mouse Input. Now Touch.On Tap fires for both touch and mouse clicks. You can delete Mouse handlers entirely.

Step 2: Consolidate logic on Touch.

Event: Touch -> On tap on Button
  Action: Audio -> Play click sound
  Action: System -> Add 1 to score

Remove any Mouse On Click event for the same button.

Step 3: If you must use Mouse, gate by platform.

Event: Browser -> Is on platform "Desktop"
  Sub-event: Mouse -> On Left button Clicked on Button
    Action: handle click

Event: Browser -> Is on platform "Mobile"
  Sub-event: Touch -> On tap on Button
    Action: handle click

This avoids double-fire by branching, but Touch with Mouse Input is simpler.

Step 4: For continuous input, use IsInTouch.

Event: Touch.IsInTouch
  Action: Player -> Set position to (Touch.X, Touch.Y)

Touch.IsInTouch works for both pointer-down and finger-down when Mouse Input is enabled.

Step 5: Disable browser-default touch effects. Some browsers apply visual feedback or scrolling for touches. To prevent unintended interactions, in Project → Properties set Disable Touch Defaults to On.

Cross-Platform Best Practice

Always plan input on Touch as the primary source with Use Mouse Input enabled. This unifies behavior across desktop and mobile, eliminates double-fire, and keeps your event sheet smaller. Reserve Mouse-specific events for desktop-only features (right-click context menus, hover effects).

Understanding the issue

This bug class falls into a pattern that's worth understanding beyond the specific case. In Construct 3, the underlying behavior is shaped by how the engine layers its abstractions - the public API you call, the runtime systems that respond, and the platform-specific implementations underneath. A bug at any layer can produce symptoms that look like they originate at a different layer. Triaging effectively means recognizing which layer the symptom belongs to, even when the gameplay code is what's visible.

The specific bug described above is the kind that surfaces during integration rather than unit testing. It depends on a combination of factors: the asset configuration, the runtime state, the platform's specific behavior. In isolation, each piece looks correct; in combination, the bug emerges. This is why thorough integration testing - playing the actual game in realistic conditions - catches things that automated tests miss.

Why this happens

Bugs of this class are particularly easy to ship past internal QA because they often depend on specific runtime conditions - hardware combinations, network states, or asset configurations that QA didn't reproduce. Players hit them in the wild, file reports that are hard to repro, and the bug accumulates negative reviews while engineering tries to recreate the failure mode.

At the engine level, the behavior comes from a deliberate design decision in Construct 3. The engine team chose a particular trade-off - usually performance versus convenience, or generality versus specificity - and that trade-off has consequences when you push against it. Understanding the trade-off is what turns 'this bug is mysterious' into 'this bug is the expected consequence of this design'.

Verifying the fix

For shipping games, the safest verification is a staged rollout. Apply the fix to 1% of players for 24 hours; watch the affected metric; expand if green. Skipping the staged rollout means the verification is the entire player base, which is too high a stakes for most fixes.

Reproducibility is the prerequisite for verification. If you can't reliably reproduce the bug pre-fix, you can't reliably verify it post-fix. Spend time getting a clean reproduction before you write any fix code. The fix is fast once you understand the reproduction; the reproduction is the slow part.

Variations to watch for

There's almost always a less obvious case where the same problem applies. The reported case is the one a player hit; the related cases hide because they're rarer or affect fewer players. After fixing the reported case, search the codebase for the pattern - one fix often unlocks several.

Adjacent bugs often share a root cause. After fixing the case you've found, spend an hour searching the codebase for similar patterns. What's the same call with different arguments? The same data flow with a different entity type? The same lifecycle issue in a sibling system? Each match is a candidate for the same fix, or a related fix that prevents future bugs of the same class.

In production

Live games surface this bug class at scale. What's a rare edge case in development becomes a daily occurrence once you have a few thousand concurrent players. The class isn't 'this player has a unique setup'; it's 'one in N thousand sessions will trigger this exact combination'.

When triaging a similar issue in production, prioritize gathering data over hypothesizing causes. A player report describes a symptom; what you need is a build SHA, a session timestamp, and ideally a screen recording or session replay. With those, the bug becomes tractable. Without them, you're guessing at hypothetical reproductions that may not match what the player actually hit.

Performance considerations

If this issue manifests under high load (many actors, many particles, many network connections), profile the post-fix code path with realistic counts. The original cost was a bug; the new cost is real work, and real work has a budget.

Diagnostic approach

Before applying any fix, gather enough context to be confident you're addressing the actual cause and not a similar-looking symptom. The cheapest diagnostic step is reproducing the bug deterministically - if you can't get the same failure twice in a row, your fix attempts will be hard to evaluate. Lock down the reproduction first.

For Construct 3-specific diagnostics, the editor's profiler is the canonical starting point. Capture a representative frame with the symptom present; compare against a frame without the symptom; the diff often points directly at the cause. If the symptom is non-deterministic, capture multiple frames and look for the pattern - the cause is usually a state transition or a specific input value rather than a continuous effect.

Tooling and ecosystem

Third-party plugins often provide better diagnostics for their own behavior than the engine does. If the affected code is in a plugin, check the plugin's documentation for debug modes, verbose logging, or inspector tools - these can save hours of investigation when they exist.

Within Construct 3, the relevant diagnostic surfaces include the standard frame debugger, memory profiler, and engine-specific debug overlays. Each one shows a different facet of what's happening. The frame debugger reveals draw call ordering and state transitions; the memory profiler shows allocation patterns; the debug overlay reveals per-system state. Bugs that resist one tool usually surrender to another - the trick is knowing which tool to reach for first.

Edge cases and pitfalls

Platform-specific edge cases are worth enumerating explicitly. iOS handles backgrounding differently than Android; Windows handles focus changes differently than macOS. A fix that works on the development platform may not work on every target. Test on each shipping platform deliberately.

When writing a regression test for this fix, focus on the boundary conditions that surfaced the original bug. Tests that exercise the happy path catch obvious regressions; tests that exercise the boundary catch the subtler regressions that look like new bugs but are really the original returning. The latter are the tests that earn their keep over the long life of the project.

Team communication

Document the fix and its rationale in the commit message or attached engineering doc. Future engineers will encounter related issues; the rationale tells them whether your fix is reusable or specific to the case at hand. Without rationale, the fix gets reverted or copied incorrectly.

If this fix touches a system several engineers work in, a short writeup in the team's engineering channel helps. Not a full design doc - a paragraph explaining what was wrong, what's fixed, and what to watch for. Future engineers encountering similar symptoms will search for the fix; making it findable is a small investment that pays back later.

“Touch with Mouse Input handles both platforms. One event source, no double-fires.”

Related Issues

For touch input not working on mobile, see Touch Input Not Working. For pinch zoom issues, see Pinch Zoom Wrong Center.

Touch object. Use Mouse Input. Single event handler. The double-fire stops.