1988 · Mastertronic
Every byte of the C64's 64 KB, one pixel each, 512 to a row. Lit pixels are what this game is: its code, graphics, level data, sound, text, tables and variables, exactly where they sit in memory. Dim areas are screen and working memory; dark is unused.
This game is in 13 parts. The map is of Shared gameplay engine, which stays in memory; the band marked as varying holds whichever of the 12 parts loaded over it is there. The Source tab has the listing of each part that has one.
| Tier | silver |
|---|---|
| Coverage | 100 % of the bytes the game uses have a description |
| Comments checked | Not audited. No audit has checked every comment, and the last sample of 80 comments had 3 wrong, so between 1 and 10 % of the listing’s comments are likely wrong. How listings are checked |
| Media | Counting each copy once, the 2 disk sides hold 14 files and 1 run of sectors no file holds. Of those, 12 are in the listings, 2 load the game and 1 is never loaded. |
| Build analysed | Two Mastertronic G64 disk variants, with disk IDs AD and TO |
| Copy | agent-draft |
| Tools | emulator: vice-mcp release v3.13.2, v3.13.2-macos-arm64-gui.dmg; C64SC, disassembler: regenerator2000 0.9.20, host: macOS 27.2 on Apple silicon (arm64) |
| Model | gpt-6.1-sol |
| Kit version | 0.0.353 |
Every step that measured the Source tab’s comments or made them more accurate, in the order it happened, with the models that did it. Accuracy of the Source explains each step and what the row above makes of them.
| Step | By | What it found | Of the listing |
|---|---|---|---|
| Research | gpt-6.1-sol | Looked the game up online (its manual, reviews or wiki pages) before reading its code. | |
| Annotation | gpt-6.1-sol | Wrote the listing’s comments. 100 % of the program is described, in 1,493 comments. | |
| Sample 1 | gpt-6.1-sol | 3 of 80 comments wrong, so between 1 and 10 % of the listing is likely wrong. All 3 were then corrected. |
likely wrong the sample’s range corrected right, or likely right not yet measured
None listed yet. Know a write-up, port or forum thread about this game? Add it to game.json.
The supplied AD and TO G64s, run in VICE with PAL video and drive emulation. Title and first mission captures are in reference/. Both titles show 1988 and name Technos Japan as licensor and Binary Design for the conversion. AD credits Arcadia Software; TO credits Mastertronic. The disk directory and byte comparison are recorded in orientation.md and media.json.
The 1988 Melbourne House instructions have a separate Commodore 64 section. The controls, stage count and programmer's note below come from that section. The July 1989 Compute! review describes the Arcadia release. Its reports are hypotheses to check on these two disks.
| Feature | Status | Evidence or question |
|---|---|---|
| Title offers one or two players | live | The TO title labels keys 1 and 2. On both disks, key 1 began a one-player game and key 2 set the two-player selector at $2F0A. The two-player port assignment was also tested. |
| Opening street | live | First mission screenshot shows a fighter outside a garage next to the English Tearoom frontage. |
| Status panel | live | First mission screenshot has counters and coloured bars for each side and a central countdown display. The timer decreased from 70 to 68 in the 800-frame test on both disks. The health refill and life loss after 00 were verified in VICE. The full score rules remain open. |
| Joystick movement and combat | live | Port 2 moved the lone fighter right and down on both disks. Fire changed the animation state. The two facing-dependent action tables and one partner hit branch were checked. Other contact and recovery cases remain open. |
| Mission progression and ending | confirmed | On both disks, setting the requested load index then letting the native transition run reached six street or interior scenes and the ending. The clear check and delay are traced. Later level loads retain the alternate tile set from L1. A complete winning route remains open. |
| Game over display | confirmed | Setting the game-over flag led both builds through their separate display routines. The two captured GAME OVER screens are pixel-identical. |
| Music and effects | live | VICE measured about one update per frame in the title, gameplay and ending. The page plays all twelve selections from the original driver. The title/ending, clear, weapon and several contact callers are traced. The callers for all twelve selections remain open. |
| Differences between AD and TO during play | live | The six level files match byte for byte and the same joystick port moves the lone fighter. Both Game Over screens match visually, though the loaders use different routines. Broader gameplay equivalence remains open. |
| Eight directions and fire combinations | live | The manual gives eight ways to move. It lists punch, kick, elbow, head-butt, hair grab, turning kick and three jump directions. It says to reverse the horizontal directions when facing left. All 36 unarmed fire input cases agreed across the disks. Contact rules and the effect of carried weapons remain open. |
|---|---|---|
| Dropped weapons | documented | The manual says a player can take and use an opponent's weapon after defeating them. Trace how the game distinguishes a bat, whip and other objects. |
| Cooperative play | live | Key 2 started a simultaneous game on both disks. Port 2 moved the first actor and port 1 moved the second in separate controlled tests. |
| Running out of time | live | The manual warns that the timer costs a life. Both disks keep the life when 01 becomes 00, then subtract a life, refill health, clear held weapons and reset the timer to 70 on the following tick. |
| Five stages and a victory cue | documented | The manual says a tune plays on completion and counts five stages. Native loading exposed six numbered resources and a separate ending. Establish the relation between the six files and the printed stage count. |
| Sprite stacking and the waist gap | traced | The programmers' note describes the use of sprite stacking and warns of a gap at the waist. The raster code positions a pair of shapes above the waist, then assigns another pair below it. The exact circumstances of the gap remain open. |
| Upper edge jump affects enemy movement | open | Compute! reported that jumping at the top of the play area freezes enemy movement while they can still attack. Reproduce it and compare against jumping farther down. |
| Return from the ending | live | Each disk reached the final pose, then entered the title at $1A60 on fire. The TO test used port 1 and the AD test used port 2. |
Each part of the game has its own symbol map and listing, parts/<id>/symbols.json and parts/<id>/listing.json; the ids are the ones in its Source pages’ addresses. Write-ups, facts and symbol maps are CC BY-SA 4.0. The game itself is not hosted here.