Quick answer: Set persistent = true in the controller’s Create event, remove the controller from the room layout so only the persistent one exists, and guard against duplicates with instance_number.

Your audio controller plays music smoothly in the first room. Walk through a door to the second room and the music cuts out abruptly. The controller was destroyed when the room changed. Setting it persistent works for one transition then duplicates on the next.

How Persistence Works in GameMaker

Every instance has a persistent variable. When false (default), room_goto destroys the instance and triggers its Clean Up event. When true, the instance is preserved and re-inserted into the next room’s instance pool. Its variables, alarm states, and visual properties carry over.

Rooms also have a Persistent flag in Room Properties. A persistent room remembers all of its instances and tile changes across visits.

The bug pattern: developer marks controller persistent, but the controller is also placed in every room’s instance layer. Entering a room creates a fresh controller; the previous persistent one is still there. Now you have two.

The Fix: One Source of Truth

Pick one approach:

A. Persistent controller in only the first room

Remove the controller from every room except the first. In its Create event:

/// obj_controller Create
persistent = true;
// rest of init...
audio_play_sound(snd_music, 100, true);

The instance is created once when the game enters the first room. After that, the controller lives across all room transitions because no other room contains a duplicate.

B. Self-deduplicating singleton

If you can’t guarantee “only first room places it”, add a guard:

/// obj_controller Create
if (instance_number(obj_controller) > 1) {
    instance_destroy();
    exit;
}
persistent = true;
// init...

The second-instantiated copy detects the existing one and destroys itself. The original persists. Defensive but reliable across messy room layouts.

Reset on Game End or Restart

Persistent instances are destroyed by game_restart() and game_end(), so a restart goes through Create again cleanly. If you also have a debug “reset to title” that uses room_goto(rm_title), the persistent controller carries music settings into the title screen — usually unwanted. Explicit cleanup:

/// User Event 0: triggered when returning to title
audio_stop_all();
with (obj_controller) instance_destroy();

Persistent Rooms For Player Progression

For game state — doors the player opened, enemies they defeated — mark the room itself persistent. On re-entry the instances and tile changes survive:

  1. Open the room in the resource tree.
  2. Room Properties → Persistent: checked.
  3. Compile. Re-entering the room restores its state.

Caveat: persistent rooms forget their state when you call room_restart() or game_restart(). For full save support you need an explicit save system.

Verifying

Add a print in Create:

show_debug_message("controller created, count=" + string(instance_number(obj_controller)));

Walk through three rooms. After fix, the message prints once at game start. Without fix, it prints once per room entered.

Understanding the issue

This bug class falls into a pattern that's worth understanding beyond the specific case. In GameMaker Studio, 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

This bug class disproportionately affects late-stage development. The work to surface it is interactive testing in realistic conditions, which only really happens after the gameplay is in place and assets are populated. Catching it early requires deliberate testing of conditions that look unimportant.

At the engine level, the behavior comes from a deliberate design decision in GameMaker. 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

After applying the fix, the verification step has three parts: confirm the original repro is resolved, confirm no obvious regressions in adjacent functionality, and (for shipping titles) deploy to a small player cohort first and watch the crash and report rates. Each step catches something the others miss.

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 GameMaker-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 GameMaker, 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

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.

“Persistent instances need exactly one Create call across the game session. Anything else is a duplicate.”

Singletons in GameMaker are persistent + the instance_number > 1 guard. Build one helper script and reuse.