Skip to content

Martin Walker

A game programmer’s decisions, week by week

Martin Walker’s C64 games and signed development diaries connect finished software with the choices behind its scrolling, sprite handling and music. His Citadel diary records experiments rather than a tidy retrospective recipe.

Martin Walker made Commodore 64 games and explained the work while it was still changing. His signed Walker’s Way columns in ZZAP!64 are particularly useful because they preserve decisions, delays and experiments that a finished game hides.

The diary connects Hunter’s Moon with the scrolling work on Citadel. These were related problems, but Walker did not present the earlier game’s routines as a solution to copy unchanged.

Preparing the next screen

In the September 1988 column, Walker describes rewriting the scrolling code. His earlier eight-direction approach prepared a second screen, introducing a delay which he wanted to reduce for the new game. The diary then considers keeping the player within a central area and starting a scroll when that area’s boundary is reached. This gives the program advance notice of the background work it will need.

The entries are dated steps in development, not proof that every proposal reached the released game unchanged. Their value is the reasoning: the position at which a scroll begins can make the next frame easier to prepare. That is a game-design choice as well as a drawing routine. (Walker’s Way, issue 41, printed pp. 100–101.)

Walker also discusses moving objects at the screen boundary. Smooth scrolling alone does not settle where sprites appear or how they cross a border. The background and the objects need to agree about the game world even when they use different display mechanisms.

Music has a schedule too

His July 1988 column explains rapidly changing notes and the repeated updates used to make a SID voice suggest a chord. The sound is a programmed sequence over time, not several simultaneous notes produced by one voice. This is the principle behind arpeggios.

Read together, the columns show a programmer dividing the machine’s time between a moving world and a changing sound. They also show why a diary is different evidence from a manual: a manual explains the available mechanism, while Walker records why he tried a particular arrangement and what he still wanted to improve.

Sources

  • Martin Walker, “Walker’s Way”, ZZAP!64 41, September 1988, printed pp. 100–101: dated Citadel development diary.
  • Martin Walker, “Walker’s Way”, ZZAP!64 39, July 1988, p. 97: music-driver explanation.
  • ZZAP!64 31, November 1987: contemporary coverage of Hunter’s Moon, distinct from the later development diary.

Checked. Verified against primary sources and signed off by a person.