The music: what shipped, and how it was put together

A game score from the mid-nineties is a strange object. It is not a recording. It is a file that contains both the notes and the instruments, and the machine rebuilds the performance every time it plays. That format, the tracker module, shaped how the music sounds far more than any stylistic choice the composer made.

The sample budget

Every instrument in a module is an audio sample stored inside the file. A richer string sound costs kilobytes, and those kilobytes come out of the same budget as the drums, the bass and every other track. Composers learned to reuse one sample across octaves, to build a kit from three or four hits, and to get variety from arrangement rather than from timbre. The tight, dry, percussive character people remember from that era is mostly a consequence of arithmetic.

Looping without seams

Game music repeats, sometimes for hours. A loop that works has to hide its own return point. The usual solutions were a pickup bar that lands naturally on the downbeat, a tail that overlaps the head, or a structure with no obvious beginning at all. Get it wrong and the player hears the stitch on the second pass and never stops hearing it.

Adaptive before middleware

Long before commercial audio middleware, scores were already reacting to the game. The cheap version was a second module that swapped in when combat started. The better version kept one arrangement running and muted or unmuted channels, so the transition was a change in density rather than a cut. That idea, layers that come and go over a constant bed, is still the backbone of adaptive scoring today. The tooling changed. The technique did not.

Reading the files

Module formats are open and the players are free. If you are curious how a particular score works, you can open it, solo a channel, and watch the pattern data scroll past. There is no better way to understand the craft than to see the arrangement laid out as a grid of notes and effects.