A client-side JavaScript port of the 1991 Amiga game, built from the original source and data files.
To play, open index.html in a browser. There is no server, build step or external library. All of the original data is embedded in js/assets.js, so it also runs from file://.
The menu sets a device for each player, just like the original: joysticks 1-4, mouse, or four keyboard layouts.
| Device on the menu | Up / Down / Left / Right | Fire |
|---|---|---|
| Arrow keys (default for player 1) | Cursor keys | Right Shift, or Space* |
| Numeric pad | 8 / 2 / 4 / 6 | Enter |
| Q A W E | Q / A / W / E | Left Ctrl, Left Alt or Cmd |
| R F U I | R / F / U / I | Space |
| Joystick 1-4 | Gamepad 1-4 (stick or D-pad) | Any face button |
| Mouse 1 | Mouse movement | Left button |
* Space fires for the cursor keys unless a player is using R F U I. With no gamepad connected, joystick 1 (the original's "joystick 2" port) falls back to the cursor keys, and the menu can always be driven with them.
| Key | During the game |
|---|---|
| P or Caps Lock | Pause |
| M | Mute |
| H or Insert | Help: retry the room from the state you entered it in |
| Del | Restart at the entry room |
| Esc | Give up (goes to the Game Over panel) |
Hold fire and press a direction to push a block or shoot (with the weapon bonus). In the endgame puzzle, hold fire and press a direction to slide a tile. High score names can be entered with the joystick, as on the Amiga, or by typing them.
Touch screen: the middle third of the game picture is fire (Space and Right Shift), and the rest is split between its top, bottom, left and right edges, which act as the cursor keys. The black bars around the picture count as the nearest edge. This works on every screen, and several fingers count at once. Touch always plays the first active player, whichever device the menu shows for them.
In the game and the endgame, an edge can also push by itself, without a second finger on fire:
| Gesture on an edge | What it does |
|---|---|
| Double tap (keep the second tap down to keep pushing) | Fire and that direction: push a block, shoot with the weapon bonus, or slide a tile |
| Long press | The same, once the player has stood still for 0.4 s. A player who is walking keeps walking, so holding a direction across a room still works |
On the menu and high score screens, one tap moves one step and holding repeats after half a second. The Game Over panel ignores the gestures, so a finger still down when you die can't pick an answer by accident: use the middle to continue, or a direction plus the middle for the other two choices. Pause, mute, help and give up, and the hidden game below, still need a keyboard or mouse.
The hidden game: when the Breadline logo has finished appearing on the loader screen, right-click (the original's right mouse button) or press G to start The Breadline Shoot 'Em Up Loader. Left-click leaves it.
| Original | Port | Notes |
|---|---|---|
game/game.s | js/game.js | All block, enemy, nasty and bonus logic, doors, pads, stairs, rooms remembered when revisited, wall sprites, roller / quake / upside-down effects |
selection/ | js/selection.js | Device menu and validation rules, walking Moochies, blinking eyes, story and credit pages |
castleanimation/ | js/castle.js | The walk over the bridge, lightning, water, gate |
loaderscreen/ | js/loader.js | Dot line, chess floor, stars, logo dissolve, hidden shooter |
endgame/ | js/endgame.js | The 5x5 sliding puzzle, score countdown, the machine's animation |
highscore/ | js/highscore.js | Masked table writing, fireworks, name entry |
qdos/QDOS.s main loop | js/main.js | Module order, attract mode, starting points |
Explode, mt_music, play_sfx | js/amiga.js, js/audio.js | Runs the IMP! files and MOD tunes directly on four emulated Paula voices |
Each blocking loop in the assembler became a JavaScript generator: yield means "wait for the next vertical blank". The game logic runs at a fixed 50 Hz. Rooms keep their exact 280-byte layout, and the names in game.js follow game.s, so the two can be read side by side.
circle table instead of editing a copper list. The right-hand door's 4 pixels of wrap-around into the next line are clipped.localStorage instead of on the disk.Everything else, including quirks such as the follow-left block's mismatched read_down and the blocks that write to absolute address input_device, was kept as written.
index.html?nointro=1: skip the loader and castle.index.html?level=2&room=11&sound=0&p=15,17,0,0: start directly in a room. sound is -1 music, 1 effects, 0 silence. p is the input device number for each player.index.html?credits=5: start with that many credits instead of 3; the first game uses one, so 5 gives 4 continues. * means unlimited. The Game Over panel only has room for one digit, so it shows 9 for anything higher.index.html?cheat=1: F9 / F10 change room, F8 goes straight to the endgame, and F1 in the endgame marks the puzzle solved.index.html?endgame=1: start directly in the endgame, with cheat mode on and player 1 on the arrow keys (or the devices given with p=). No keys are needed, so this also works on a phone. In both cases the game counts as 96% solved, and an active player with no score gets 10000 points, because the puzzle's clock runs off the score. Add score= to set every active player's score instead, for example index.html?endgame=1&score=500. The clock takes 50 points a second, the highest score is 999999, and 0 leaves every player out.js/assets.js is generated from the original files. To regenerate it after changing any data:
python3 web/tools/build_assets.py
Run it from the SOURCE folder. It needs only standard Python 3.