{
  "id": 21083608,
  "title": "Stop Nesting Your Dash and Dive Events in GDevelop — Here's Why They Get Stuck",
  "url": "https://urgent.news/2026/11/21/stop-nesting-your-dash-and-dive-events-in-gdevelop-heres-why-they-get",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-11-21T17:54:38.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/katanaworks/stop-nesting-your-dash-and-dive-events-in-gdevelop-heres-why-they-get-stuck-379k"
  },
  "original_language": "en",
  "account": "When you combine a dash and dive action within the same event condition in GDevelop, the game engine reads them as a single continuous logic chain. This results in the player getting stuck mid-animation, inputs stopping registration, and the character appearing frozen. The issue lies in GDevelop's evaluation of nested actions within the same frame tick.\n\nTo resolve this, separate the dive action into its own event block. Begin by preparing your sprite with both \"Dash\" and \"Dive\" animations. Install the Dive Dash behavior on your player object, but refrain from adjusting its default speed and distance values until the logic is functioning properly.\n\nNext, restructure your event sheet. First, create a condition for pressing the X key, followed by an action to simulate the dash. Then, create a separate event block with the X key press condition and an action to simulate the dive. This change ensures that each state transition is processed independently.\n\nTo prevent players from spamming dash/dive endlessly, implement animation-state guardrails. Add conditions checking the current animation name to avoid starting a new action while in the same state. This creates a cooldown tied to animation length, eliminating the need for timers.\n\nWith dash and dive now as independent states, you can introduce additional mechanics. For example, you can make destructible environments react to the player being in the \"Dive\" state upon collision with breakable blocks. Stomp attacks can trigger damage when the player dives into an enemy's top hitbox. These mechanics depend on cleanly separated movement states.\n\nThe key rules to remember are: if actions get stuck together, they were nested in the same event block; animations are state indicators, not just visuals, so use animation name checks to gate actions; and gate infinite movement early by implementing animation-based guardrails, which are more intuitive and cost-effective than timer-based cooldowns. By separating logic first, then polishing speeds, friction, and frame counts, you'll have a responsive platformer that runs smoothly.",
  "summary": "If you've ever wired up a dash and a dive in GDevelop and watched them fuse into one unmovable blob, you've hit the linked-event problem. It's one of the most common 2D platformer bugs in the engine, and the fix is simpler than you think. This isn't a beginner mistake. It's a GDevelop-specific gotcha that comes from how the engine processes event chains. Let's break it apart. What's Actually…",
  "key_points": [
    "Combining dash and dive in same event causes player to get stuck",
    "Separate actions into distinct event blocks for proper processing",
    "Use animation checks to prevent infinite movement and spamming"
  ],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}