Fix: GameMaker Path Following Overshooting Target

You set an enemy to follow a patrol path. It walks smoothly along the waypoints, reaches the last one, and then teleports 20 pixels past it before snapping back. Or it loops when it should stop. Or it freezes at 99% of the path and never quite arrives. All three bugs come from the same place: the relationship between path_speed and path_position at the endpoint.

How Path Position Works

path_position is a normalized value from 0.0 (start) to 1.0 (end). Each frame, GameMaker advances it by an amount proportional to path_speed / path_length. A 200-pixel path at speed 4 advances by 4/200 = 0.02 per frame, reaching 1.0 in exactly 50 frames.

But if the remaining distance is 0.015 and the increment is 0.02, the position goes to 1.005 — past the end. What happens next depends on path_endaction.

The Fix

Step 1: Use path_action_stop.

// Create event
path_start(pth_patrol, 3, path_action_stop, true);
// Speed 3, stop at end, absolute position

path_action_stop halts the instance at position 1.0 and fires the Path Ended event. It is the safest option for one-shot movement like a patrol leg, a cutscene camera move, or a projectile arc.

Step 2: Clamp in the Step event.

// Step event - belt and braces
if (path_position >= 1.0) {
    path_position = 1.0;
    path_speed = 0;
    // Arrival logic here, or handle in Path Ended event
}

Step 3: Handle arrival in Path Ended.

// Path Ended event
if (state == "patrol_to_B") {
    state = "wait_at_B";
    alarm[0] = room_speed * 2;  // wait 2 seconds
}

The Path Ended event fires exactly when the path finishes. It is the cleanest place to put arrival logic because you do not need to poll path_position in the Step event.

Closed vs. Open Paths

A closed path (loop) wraps path_position from 1.0 back to 0.0 automatically. An open path with path_action_continue keeps incrementing past 1.0, which moves the object in a straight line beyond the last waypoint. Use closed paths for patrol loops and open paths with path_action_stop for one-way trips.

Verifying the Fix

Draw path_position as text in the Draw GUI event. Walk the object along the path and watch the number climb to 1.0. It should stop at exactly 1.0 and never exceed it. If it flickers between 0.99 and 1.0, the speed increment is fighting the clamp — set path_speed = 0 on arrival.

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

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

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

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

Diagnosing this class of bug benefits from a structured approach: confirm the symptom, isolate the variables, hypothesize the cause, and verify the hypothesis before writing fix code. Skipping the isolation step is the most common mistake; without it, fixes often address symptoms while the underlying cause continues to produce other variations.

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

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

Boundary conditions deserve specific testing attention. What happens when the input is zero, maximum, negative, or NaN? What happens at the start of a session vs hours in? What happens at the boundary between two systems handling the same data? These are where bugs hide and where regression tests are most valuable.

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.

“Path following in GameMaker is reliable once you understand that path_position is a fraction, not a pixel distance. Clamp it, stop it, and handle arrival in the event designed for that purpose.”

Related Issues

For instance variable resets on room change (which can reset path state), see GameMaker instance variables resetting on room change. For sprite animation during path movement, see GameMaker sprite_index wrong after state change.

Always use path_action_stop for one-shot paths. The other end actions are for specialized cases and will surprise you at the endpoint.