Jetpacks vanishing while the player is invisible

Verified against the spelunky.ai port v0.1.10 on 28 October 2026.

A Jetpack lying on the floor, in a shop or in the player's hands is gone the moment he turns invisible, which only happens as he dies. Nobody sees it go: without the Ankh the game-over screen follows, and with it, he's visible again before any Jetpack looks.

The player walks past a Jetpack lying on the floor into a Mantrap, which swallows him. On the next step the Jetpack behind him is gone ^[1].

The Jetpack's step has one check of its own:

if (instance_exists(oPlayer1))
    if (not oPlayer1.visible) instance_destroy();

It's the worn Cape's check, word for word ^[2]. The Cape is drawn on the player's back, so it should go when he does. A worn Jetpack isn't an object at all, only a flag (global.hasJetpack), so the oJetpack that runs the check is the pickup: the one lying in the level, for sale, or held.

The player turns invisible when he's crushed, when his hearts fall below -99 ^[3], or when a Mantrap or the Ghost takes him ^{[4] [5]}. After a crush or the hearts, every Jetpack goes in the same step, as the player steps first; after a Mantrap or the Ghost, in the next, as their collisions come after the steps. With the Ankh it never happens: the revival makes him visible again before any Jetpack's step runs ^[6].

Die out of sight with a Jetpack nearby, without the Ankh: walk into a Mantrap or let the Ghost take the player. The game-over screen hides it, so it only shows in the step between. The replay of the clip's staged scene, on a custom level, has a Mantrap eat the player and the Jetpack on the floor behind him destroyed on the next step ^[7]. The Ankh's case is only the code's and the event order's: no replay has a Jetpack near an Ankh revival.

The spelunky.ai port reproduces it exactly: it's in docs/quirks.md's list of the 1.1 source's bugs ^[6], and the oracle's fingerprint of the replay pins the step it goes. No option turns it off.