HDanke's GD Editor Docs

Appearance

Spawn Triggers ​

[FIXED] Internal Remap Instance IDs are remappable ​

Version: 2.208
Date: 19/01/2026

Description ​

Every Spawn trigger with remaps is assigned a Remap Instance ID on level load in the order they are loaded in. Spawn triggers without remaps are assigned ID 0.

This Remap Instance ID is remappable which has the following effects:

  • Spawn triggers may accidentally use the wrong set of remaps
  • The game will crash if the ID is remapped to a remap instance that does not exist

Video ​

https://youtu.be/ZDzuKXkeM8g?si=mSGYaf9Lda75WfYV

[FIXED] Instant Collision resets remaps ​

Version: 2.208
Date: 19/01/2026

Description ​

Groups spawned by a remapped Instant Collision do not inherit remaps.

Checkpoint resets remaps ​

Version: 2.208
Date: 19/01/2026

Description ​

Groups spawned by a remapped Checkpoint do not inherit remaps.

Spamming restart (R key) skips spawn activation ​

Version: 2.208
Date: 19/01/2026

Description ​

Spamming R quickly can skip the activation of spawns placed before the origin line in Platformer. This can also happen but only on the very first attempt in Classic.

I assume the reason this happens is because the level restarts before the spawn limit is reset, so the triggers are spawn limited on the next restart.

Count spawn inheritance without Multi Activate ​

Version: 2.208
Date: 18/03/2026

Description ​

Count triggers without Multi Activate only use their own remaps if there is no other Count trigger that activates after them on the same Item ID, if they exist then the non-multi Count trigger will use their remaps instead.

Triggers that are not remappable or not fully remappable ​

Version: 2.208
Date: 19/01/2026

Description ​

The following triggers cannot be remapped, or have some IDs that are not remappable. I have highlighted the ones that cause some issues or make things more difficult in certain situations.

These triggers are not remappable:

  • Color
  • Rotate Gameplay
  • Gradient (ID can get remapped but it always disables the gradient)
  • Checkpoint
  • Legacy Enter Effect triggers (not spawnable)
  • Keyframe (trigger is remappable, groups inside keyframe objects are not)

These triggers have IDs that are not remappable:

  • Pulse (Color ID)
  • Spawn (Original Group ID)
  • Area Triggers (Effect ID)
  • Area Tint, Enter Tint (Color Channel)

Stopping a spawn trigger with delay from another Spawn trigger with delay makes the last Spawn delay spawn again without remaps ​

Version: 2.208
Date: 19/01/2026

Description ​

Stopping any Spawn trigger with delay while spawn delays are checked makes the game check the last Spawn delay trigger twice, which if it were to spawn in the same tick would activate twice.

It doesn't matter if you stop a Spawn trigger that has already been activated in the current tick, one waiting to activate or you make the Spawn trigger stop itself.

Due to the spawn limit, this bug is only noticeable if the spawn trigger is remapped. The first activation will be remapped while the second spawn activation will have no remaps.

You can use a Spawn trigger with a very high delay value to counteract this bug, as even if it's checked twice it will not spawn.

This bug also affects Spawn Ordered, but only when spawning triggers that were moved.

The spawn delay of triggers spawned by Spawn Ordered depends partly on their current position, which can be affected by move triggers.

Not every move is affected, movements caused by Area triggers are completely ignored.

This behavior is inconsistent however, the game stops ignoring the new delays in some situations, and some spawns may be delayed until another spawns just like those placed on the timeline.

Last updated: