1988 · Elite Systems

About this page

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

The copy studied

The pages describe Elite Systems' 1988 disk, as a G64 image. A short boot program loads a fast loader, which shows the loading picture and reads the game from sectors that no file names, then starts it at cold_start. The game is one load: nothing is read from the disk again. The listing on the Source tab is built from memory saved at that moment. No game image is hosted here.

Data East's American disk of 1987 was also looked at. That disk holds a different program, by Quicksilver Software, and only its screens appear here, for comparison on the Overview.

Original game credits

The game's own title pages name its makers, in the text at $21EE.

Site contributors

Other places to love this game

Sources

  1. Zzap!64 35, March 1988, pages 12 and 13, the review of Elite's version, read in the scan at the Internet Archive (zzap64-magazine-035) on 17 November 2026: the story, the price, the ratings and the quotations.
  2. C64-Wiki, "Ikari Warriors (Elite)", in German, read 17 November 2026: the controls, the tokens' colours and the tips checked on the Gameplay page.
  3. Wikipedia, "Ikari Warriors", read 17 November 2026: the arcade original, by SNK in 1986, and its turning joysticks.
  4. GameBase64, "Ikari Warriors", read 17 November 2026: the credits, which also name Mark Cooksey for the music.
  5. MobyGames, "Ikari Warriors", read 17 November 2026: Quicksilver's American version and Elite's European one.
  6. The timings and tests on these pages: measured in the VICE emulator from a saved moment of play, and on the kit's 6502 running the game's own code, as facts.md records.

Research record

The write-up, facts and symbol map are available under CC BY-SA 4.0; code is under MIT.

Version, coverage and tools
Tiersilver
Coverage100 % of the bytes the game uses have a description
Comments checkedNot audited. No audit has checked every comment, and the last sample of 80 comments had 16 wrong, so between 13 and 30 % of the listing’s comments are likely wrong. How listings are checked
MediaCounting each copy once, the disk side holds 3 files and 25 runs of sectors no file holds. Of those, 15 are in the listings, 2 are data the game loads, 4 load the game and 7 are never loaded.
Build analysedG64 disk image: a 101-byte boot program and a 1,265-byte fast loader as files, and the game in raw sectors, its $4000-$CFFF EORed with $C9; one load, entered at $0F80
Copyagent-draft
Toolshost: Linux x86_64 (Claude cloud container), emulator: release v4.0.0, v4.0.0-linux-x86_64-gui.zip, disassembler: regenerator2000 (kit/c64/r2000.py), publication: Python 3; symbols_export.py and listing.py; a Python port of draw_map_row for the map, subagents: one checker agent for the 60-comment sample; one agent for everything else
Modelclaude-opus-5-5
Kit version0.0.353

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-5-5Looked the game up online (its manual, reviews or wiki pages) before reading its code.
Annotationclaude-opus-5-5Wrote the listing’s comments. 100 % of the program is described, in 570 comments.
every routine and table described on one model; the map objects' and tile sets' comments generated from the map script run on the kit's 6502 and checked against it
Sample 1claude-opus-5-516 of 80 comments wrong, so between 13 and 30 % of the listing is likely wrong. All 16 were then corrected.
20 drawn from the 182 generated comments (none wrong) and 60 from the 385 written ones (16 wrong)

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

What the game does, and how it was checked

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:

Features

FeatureStatusWhere
One player, or two at once as a team; either can shoot or grenade the other (Zzap!64)confirmedupdate_bullet_hits $BA25 tests every bullet against both players, skipping only the one who fired it; blast_hits $BE58 kills every player on foot but the thrower
Joystick in port 2 for player one (GameBase64); player two's portconfirmedlower_panel_irq $3D44: port 2 for player 1 and port 1 for player 2 in a two-player game; both ports ANDed in a one-player game
Eight directions of movement (C64-Wiki)confirmedmove_player $C485 moves a pixel in each direction the joystick holds
A short press of fire shoots, a long press throws a grenade (C64-Wiki)liveplayer_fire $233A: a bullet on the press, a grenade at the ninth count, counted every second frame; holds of 16 frames fired once, 20 and 30 threw a grenade
Limited bullets and grenades, both shown in the panel (99 and 50 at the start, reference/play-start.png)confirmedplayer_fire takes a bullet from the BCD count zpa_6D; draw_panel_digit
Tokens left by soldiers refill ammunition (Zzap!64)confirmeditem_cycle $B53C gives every so-many soldiers an item; drop_item $C192; pick_up_item
Power-ups by colour: purple, white and black add 50 bullets and/or grenades, black refuels a tank; green kills every enemy on screen with no points; red widens the grenade blast; yellow lengthens the shot; light blue shoots through obstacles (C64-Wiki)confirmedpick_up_item, colours from item_colours $C36E read as multicolour; black fills bullets, grenades and shells to 99 rather than adding 50; green also brings down a helicopter for 1,000
Every power-up is lost with a life (C64-Wiki)confirmedinit_player, called by respawn_players $C376
Tanks marked with a flashing IN can be boarded; immune to bullets, killed by grenades; a fuel bar drains, and the tank explodes when it runs dry or after a grenade, unless the player gets out in time (Zzap!64)confirmedplayer_fire boards and leaves; update_bullet_hits never hits a player in a tank; update_fuel $BC90: 100 frames from an empty tank or a hit to the explosion; sprite $DE is the sign
Gun emplacements, helicopters and enemy tanks: bullets do not hurt them, grenades do (Zzap!64)confirmedupdate_guns $263C; update_bullet_hits skips soldiers riding a vehicle; blast_hits destroys vehicles, a flying helicopter and guns
Land mines appear only when stood on, flashing and beeping, just in time to step off (Zzap!64, C64-Wiki)confirmedupdate_mines: shown within 16 by 32 pixels, set off within 5 by 12; the places come from route_list
Water: enemies dive under, the player slows down (C64-Wiki)confirmedmove_player slows a player on foot and stops a tank; a soldier in water uses frame $6F and is not hit by bullets
Standing still stops new enemies appearing, except in a few places that attack from behind (C64-Wiki)confirmedspawn_from_route $194E starts soldiers by scroll position, and the screen scrolls only while a player is above line $BC; the attacks from behind were not looked for
Extra lives from points (C64-Wiki, "valuable for the extra lives")liveadd_score: 20,000, 50,000 and every 50,000 after, run on the simulator
The start beside the crashed aircraft (Zzap!64; reference/play-start.png)live
One long vertically scrolling route to the village of Ikari, ending with Colonel Cook's rescue (C64-Wiki; the ending text at $B7FA)confirmedmap_script $92E1, 1,891 rows run by draw_map_row $7F80; checked live against 49 drawn rows
Ending: "Congratulations, you have rescued Colonel Cook" and a bonus of 100,000 points (the text at $B7FA)liveroute_finished; shown with the map script moved to its last commands
High-score table of ten, entry of a name for a top-ten score (reference/high-scores.png; the text at $CC88)confirmedenter_high_score $CA90: a name of nine letters spelt with the joystick
Title sequence: high scores, the island map with "Warriors" written across it, a demo (reference/title-attract.png, reference/high-scores.png)live
Music: a "film-style" soundtrack during play (Zzap!64); composer Jason C. Brooke, with Mark Cooksey (GameBase64; the game's own credits name only Jason Brooke)confirmedmusic_tick $E000; three tunes in tune_table $E681; the credits at $21EE
The loading picture, shown by the loader while the game loads (reference/loading-screen.png)liveGM1, $03C0-$03E1
Score panel and status bars drawn in the opened upper and lower borders (MobyGames; work/frame-play.json)confirmed$D011 writes on lines 249 and 308

Beyond the documentation

Found in the code, not in the manual.

Open questions

Memory footprint

Every byte of the C64's 64 KB, one pixel each, 512 to a row. Lit pixels are code, graphics, sound, text, tables and variables; dim areas are screen and working memory.

The symbol map is symbols.json; the listing behind the Source tab is listing.json.