Quick answer: Clear or move the highlight whenever its target is destroyed, hidden, or scrolled off, and advance or hide the highlight on the step change.

A glowing highlight ring hanging in empty space after the button it framed is gone looks broken and distracts new players. The highlight outlived its target. Tie its lifetime to the target and clear it when the target leaves.

How to fix it

1. Bind highlight lifetime to the target

When the target is destroyed or hidden, destroy or hide the highlight in the same place. In Construct 3, pair the highlight removal with the target's destroy event.

2. Clear on step change

Remove the current highlight before showing the next step's highlight, so an early step's ring cannot linger into a later step.

3. Handle off-screen targets

If the target can scroll off screen, hide the highlight while the target is not visible and restore it when the target returns, rather than leaving the ring stranded.

Catching the ones you can't reproduce

The hardest version of this to fix is the one you can't reproduce — it only happens on a player's hardware, OS, driver, or save state, under conditions that simply aren't present on your machine. A report that says “it crashed” or “it froze” gives you nothing to act on, so the bug survives release after release while quietly costing you players.

Automatic error capture closes that gap. Each failure arrives with its full stack trace, the device and OS, the build number, and a breadcrumb trail of what the player did right before it broke, so even a failure you have never seen becomes a specific, reproducible issue. Fold identical failures into one signature ranked by how many players each hits, and your worklist sorts itself worst-first instead of arriving as a stream of vague complaints.

This is where a tool like Bugnet earns its place. Its SDK captures every Construct 3 error automatically with the full stack trace plus device, OS, memory, build, and game-state context, folds duplicates into one grouped issue with an occurrence count, and ties each to the build it first appeared on — so you fix the problem that hurts the most players first and confirm it is gone when its signature disappears from the next release.

The bug you can't reproduce isn't gone — it's just invisible until you capture it from the player's device.