Why does an event group keep running after I deactivate it?

Event sheet evaluation runs top to bottom each tick. If the deactivate happens after the group’s events, the group already ran this tick. Move the deactivate above the group, or use System Wait 0 to defer the group’s contained events to next tick.

How do I deactivate by name vs reference?

System Set Group Active takes the group’s name as a string. Names are case-sensitive. Typo = silently no-op. Drag from the group itself in the project bar for tooltip-confirmed naming.

What's a Function vs Group for pause-able logic?

Functions can’t be deactivated; you call them. Groups can be paused as a unit. For ad-hoc pause-able blocks, prefer groups; for reusable code, prefer functions and gate them with an isPaused boolean.

Fix: Construct 3 Event Group Deactivate Still Runs

Quick answer: Event sheets evaluate top to bottom. Put the deactivate call before the group in the sheet, or the group runs once more this tick.

A pause action deactivates “Gameplay” group. The group runs anyway for one more tick after the pause press. Players see one extra frame of motion before the freeze.

Sheet Order Matters

Construct evaluates events top to bottom each tick. If the deactivate-group event sits below the group it deactivates, the group’s events execute first this tick. The deactivate takes effect on the next tick.

The Fix

Reorder the event sheet:

Event Sheet (top to bottom):
  On pause pressed:
    System Set group "Gameplay" active false

  // Group below
  Group "Gameplay":
    Every tick: player move

Now the pause check runs first; if pressed, the group is deactivated and skipped this same tick.

Use System Wait 0 for Defer

If reordering breaks other dependencies:

On pause pressed:
    System Wait 0 seconds
    System Set group active false

Wait 0 yields to the next tick. The deactivate happens at the start of the next evaluation, before the group runs again. Costs one frame of pause delay, which is invisible to players.

Verify Group Names

System Set Group Active takes a string. Typo = silent no-op. Drag the group from the Project bar into the action’s name parameter when authoring — this confirms the name visually.

Gate with Variable Instead

For mechanics where pause should also delay sub-conditions:

On pause pressed:
    System Set isPaused true

  Group "Gameplay":
    isPaused = false:
        player move
        enemies AI

Adds a level of indirection: the group remains active but its sub-events gate on isPaused. Slightly more verbose but doesn’t depend on sheet ordering.

Verifying

Add a tick counter to a group action. Press pause. The counter should stop immediately on this tick — not run one more tick before stopping.

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

Related bug classes often share the same root cause. If you find yourself fixing this issue, look for cousins: similar symptoms in adjacent systems, the same data flow but a different value, or the same fix pattern in another module. The catalog of 'we've seen this before' becomes valuable institutional knowledge.

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

For shipping titles with a long support window, watch for this issue resurfacing after dependency updates. Engine upgrades, driver updates, OS releases - each one can resurface a bug class you thought you'd fixed because the underlying behavior changed slightly. Regression tests catch the obvious ones; player reports catch the rest.

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

Performance implications matter when this bug class scales with player count or asset count. A bug that fires once per session is annoying; a bug that fires once per frame compounds. After fixing, profile the affected code path under realistic load. The fix that's correct for one entity may be too slow for ten thousand.

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

Modern engine versions ship better tooling for this kind of issue than older versions. If you're on an older release, the diagnostic step may take significantly longer because the tools you'd want don't exist yet. Sometimes the right answer is upgrading rather than fighting through limited tooling.

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

Edge cases for this class of issue often involve specific timing: the first frame after a state change, the last frame before a transition, frames where multiple subsystems update simultaneously. Reproducing these reliably is part of what makes the bug class hard to test.

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

When this bug class affects multiple teams (often the case for cross-system issues), early communication prevents duplicate work. The team that owns the symptom may not own the cause. A 15-minute conversation at the start of triage often saves hours of independent investigation.

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.

“Sheets evaluate top to bottom. Put pause checks above the gameplay they pause.”

Group order in the sheet is part of your gameplay logic. Treat reordering with the same care as code refactoring.