1982 · Commodore
What the code does that the instructions never mention: cats that kill, a bonus rat that pays out once, and a whole game decided before you press F1.
01 · Secrets
None of these are in the instructions, and several contradict what has been published about the game. Every one came out of the code. Each ends with where to look.
Published descriptions say the cats only slow you down. In this build they kill the rat exactly like a red rat does: one routine checks the rat's position against both, and both set the same "caught" flag. Only the red rats are slowed by cats. Cats never show on the radar, so you only see one when it scrolls into view.
player_collision_check at $F344
The title screen says BONUS RAT FOR 20000 PTS, and published descriptions turn that into an extra life every 20,000 points. The code gives one per game. It checks whether the middle two digits of the score are exactly "20", and a flag stops it paying out again. That flag is only cleared when the game ends. Every instruction that could write to it has been checked, including the indexed writes that could reach it indirectly: nothing else does.
add_score at $F02A · the flag at $99 is reset only by game_over_reset
The first round's cats and cheese are placed before the title screen appears, so the first game after loading always gets the same round 1. After that the random number generator is only moved on once per tick while the title screen waits for F1, never during play. How long you wait before pressing F1 decides the layout of every later round in the game, and nothing you do in the maze changes it. Try it in Placement, on How it works.
prng_next at $EE2E is called from placement and the title loop only
The ROUND counter on screen keeps going up, but the table index behind it wraps after 15. Round 16 has round 1's red rats, cats, speed and maze. Once you have survived 15 rounds the game never gets any harder.
next_round at $F2BF resets the index when it reaches 15
One cheese has a small red "2x" in its corner. It doesn't just double the next slice: from that one on, every slice scores double and X2 flashes on the panel, until you lose a life. Losing a life also resets the slice value to 100. Slices are worth 100, 200, 300… the tenth is worth 1,000, and each unit of TIME left at the end of a round is worth 60 more.
check_meal_eaten at $F0CA · score_doubler at $C0, cleared when a life starts
In rounds 3, 7, 11 and 15 the red rats sit frozen on their spawn points and only start chasing when TIME runs out. There's a catch in the other direction too: if you're caught during a SPEED RUN, it's over. You lose the life and go straight on to the next round.
red_rat_move_countdown = $FF · timeout_handler at $EAC0
When the TIME bar empties nothing dramatic happens. You can't drop stars any more, and every two-thirds of a second the rat gets a little slower, until it moves at a third of its normal speed. The rat never stops, either: with no input it keeps going, and at a wall it turns right by itself, or left if right is blocked.
timeout_handler at $EAC0 · move_player at $E78C
A red rat never plans a route. At each cell it compares its position with yours along one axis and steps toward you if that cell is open; once it is level with you it switches axis. If the way toward you is a wall, it carries straight on, or turns right, or turns left, and only tries again at the next cell. It has no idea that the way round is the other way.
red_rat_chase_direction at $E23C · move_all_red_rats at $E088
The red rats test their next step against the 224-byte maze bitmap. The rat's own movement never touches it: it reads back the characters already painted on screen. The same wall is stored twice, in two formats, and each reader uses the one it can check more cheaply.
red_rat_can_step reads the bitmap · read_screen_in_direction reads screen RAM
When your score passes the high score, the game sets a flag saying so. The game never reads that flag. Whatever it was meant to trigger never made it into this build.
new_hiscore_flag at $0217 · set at $F090, cleared at game over, never read
Three Blind Mice runs continuously under the whole game, and the melody table is read from the last entry to the first. Every tune in the game is stored that way except the round-complete jingle. Counting an index down until it goes negative is a common 6502 idiom: the end test is a single branch on the sign flag.
music_tick at $EA2B · index counts 15 down to 0, reloads, repeats
Tucked in the string table is COMMODORE V.02. The game keeps its text in two
alphabets: ordinary labels use standard screen codes, while the banners (GAME OVER,
SPEED RUN) use a private set of bright glyphs where S is $1B instead of
$13. Four of them, P, L, semicolon and full stop, double as the key diagram on
the title screen.
str_speed_run at $FD33 · str_version at $FD7C