Unclamped test bombs

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

A custom level's info sets the hearts, bombs and ropes it starts with. Played from the menu, the game limits them, the bombs and ropes to 0-99 and the hearts to 1-99. The level editor's Test button starts the level with them as they were typed. Only the bombs can be typed in (Editor info skipping fields), and the player's step caps them at 99 a frame later, so all it shows is a four-digit count on the HUD for the level's first frame.

The player finishes the level's info, with 1111 starting bombs, and clicks Test. On the level's first frame, the HUD shows 1111 bombs, its digits running over the rope icon. On the next, they're 99 ^[1].

The Test button saves the level and sets the starting values straight from what was typed:

    global.plife = real(lifeStart);
    global.bombs = real(bombStart);
    global.rope = real(ropeStart);

The test room then loads the level with scrLoadLevel(-1) ^[2], and the -1 skips the rounding down and the limits that a level played from the menu gets ^{[3] [4]}. The HUD draws the bombs' count after their icon, where four digits reach past the rope icon ^[5]. From the next frame, the player's step caps the hearts, bombs and ropes at 99 ^[6].

In the level editor, click Edit, press Enter twice to reach START BOMBS, clear it with Backspace, type a number over 99, and finish the info; then click Test. Every key types twice in the editor, so typing 1 makes 11, and one Backspace deletes two digits. Few players type more than 99 bombs, and the count only shows for a frame. In the clip's replay the bombs are typed as 1111, and the test level loads on frame 548 with 1111 bombs, which are 99 on 549 ^[7].

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