1982 · Brøderbund Software

About this page

This minisite was contributed by air. It’s agent-generated and needs a human editor. Clone https://github.com/gamesexplained/gamesexplained and follow kit/START.md to curate games/c64/choplifter with me to Gold.

Footprint

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.

Status

Tiersilver
Coverage100 % of the bytes the game uses have a description
Comments checkedNot measured. No sample of the listing’s comments has been checked. How listings are checked
Build analysedcartridge image, CBM80 header at $8004, cold start $9593
Copyagent-draft
Toolsemulator: VICE x64sc 3.10 with vice-mcp, disassembler: regenerator2000 0.9.20
Modelclaude-opus-5 (Claude Code), with nine subagents on the same model
Kit version0.0.1

How the listing was checked

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.

StepByWhat it foundOf the listing
Researchclaude-opus-5Looked the game up online (its manual, reviews or wiki pages) before reading its code.
Annotationclaude-opus-5Wrote the listing’s comments.
nine subagents on the same model
Annotationclaude-opus-5-5[1m]Wrote the listing’s comments. 100 % of the program is described, in 761 comments.
the 43 inline words after the drawing calls described with line comments; the loader's leftovers excluded with their reasons

likely wrong the sample’s range corrected right, or likely right not yet measured

Contributors

Other places to love this game

What the game does, and where we found it

Read this before annotating code. What the game is documented to do, with verification status against the binary. Statuses: open (documented, not found yet), traced (in the code, could not be exercised; say what was tried), confirmed (in the code, consistent with the emulator), live (observed directly), differs (the code does something else). "Absent" is not a status.

Sources: the C64 manual scanned at archive.org (text only; no images were taken from it), the C64 entry on c64-wiki (c64-wiki.com), the game's own title screen, and play in the emulator. Every screenshot in reference/ was taken from the emulator during this run.

Features

FeatureStatusWhere
Helicopter flown with a joystick in control port 1liveread at $DC01 from $976A, $97AD, $A71A, $A741
A short press of the fire button shootslive$9774 compares the hold counter $96 with 15; under 15 it calls $97D2
A longer press turns the helicopterlive15 or more calls $97F1; the turn continues while the button is held
Direction of the turn follows the stickdiffersthe stick is read only when $59 is 0 or ±1. At a full facing the hold simply flips the machine to the other side, whatever the stick does ($9816)
64 hostages in totalconfirmed$0CEE + $0CEF is compared with #$40 at $9683
Hostages are held in sheds that have to be blown openlive$B652 sets $0CF4,x; the shed body switches from shape 71 to 72
Eighteen hostages per barracksdiffers$BE52 puts 16 in each of sheds 1 to 3 and 8 in shed 4, which starts open
At most 16 hostages ride at onceconfirmed$9D18 refuses to board when $0CF1 holds 16
Hostages walk to the helicopter and climb inlive$9B7D; boarding at a signed distance of +8/+9 or −11/−10
The helicopter can run its own people overconfirmeda hostage at −9 to +7 with the machine down and still is killed ($9E14)
Status bar counts killed, aboard and deliveredlivethree BCD counters written by $A978; $0CFC, $0CFE, $0CFD
Tanks attack from the far side of the borderliveactor type 3, handler $A0BB, five gun elevations
Jets appear after the first sortieconfirmedthe type-9 cap at $A3B6 is 0 at difficulty 0 and rises to 1 and 2
Drones appear on the third sortietracedactor type 10, handler $B73D, released from sortie 2 on, one at a time, homing on the helicopter. The shared emulator stayed on sortie 0 for the whole watch, so this rests on the code and the shape, not on seeing one
Three helicopters per gamelivethe life count is sortie_number ($0CFF). A sortie ends only when the helicopter is destroyed: the settle counter $62 runs to 6 ($A875), sets sortie_end_delay ($63), the main loop adds 3 a pass until it goes negative ($968E) and jumps to sortie_start, which increments $0CFF ($964B) after the message. $0CFF = 3 at $9621 is THE END. Live: a full-speed crash with $0CFF = 2 ran the whole chain and ended the game
No points are scored, only hostages countedconfirmedthere is no score variable; the only counters are the three on the bar
Sorties are announced as FIRST / SECOND / THIRD SORTIElivemessage table at $8AD7, drawn into a raster text window by $8A8B
THE END and MAGNIFICENT! end messagesconfirmedsame table, shown from $96E4 and $96E8
RUN/STOP pauseslive$98BC reads the KERNAL scan code $3F from $C5
Q ends the gameopenno read of the Q key was found. The game's only keyboard input is the RUN/STOP poll at $98BC, reached through $C5, and the only other keyboard code is the KERNAL scan the raster handler calls. Searched: every $DC00/$DC01/$C5/$CB/$0277 access in $8000-$BFFF, and every immediate comparison against the matrix code for Q ($3E) and its PETSCII ($51)

Beyond the documentation

Open questions

The symbol map for this game is symbols.json; the listing behind the Source tab is listing.json. Write-ups, facts and symbol maps are CC BY-SA 4.0. The game itself is not hosted here.