Free bomb arrows

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

With the Bow fully drawn, the bomb key readies a bomb arrow instead of throwing a Bomb. It asks for a bomb, and never takes one. The same key does nothing while the Bow is still drawing, so the player has to wait for the full draw.

From a ledge, the player presses the bomb key with the Bow barely drawn, and nothing happens: he shoots a plain arrow. Drawn all the way, the key makes a bomb arrow, which sticks in a wall and blows up there, while his bombs stay at four ^[1].

The bomb key readies a bomb arrow if the player has a bomb, the Bow is drawn and he isn't whipping ^[2]:

else if (inGame and kBombPressed and global.bombs > 0 and not whipping and bowArmed)
{
    holdArrow = ARROW_BOMB;
    alarm[11] = 1;
}

A bomb thrown the usual way takes one with global.bombs -= 1 ^[3]. Nothing does for the bomb arrow: not these lines, not the script that shoots it, which only gives it what's left of its fuse, nor its explosion ^[4].

Later in the same step, the draw sets the arrow back to a plain one on every step the Bow is still drawing, so the bomb key's arrow lasts only while the draw is full ^[5]. A bomb arrow's 80-step fuse runs from the step it's readied, and if the player is still holding it when it runs out, it explodes in his hands ^{[6] [7]}.

Hold the Bow's attack key until it's fully drawn, with at least one bomb, then press the bomb key and let go. The replay of the clip's staged scene pins it: the bomb key at a light draw leaves a plain arrow, and at full draw readies a bomb arrow that explodes 80 steps on, with the bombs still at four ^[8].

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