Map Drawing Functions

During each frame of gameplay, a rectangular window of map data is drawn to the video memory. A combination of solid, masked, and backdrop tiles are brought together to form the static game world described by the map data. On top of this uninhabited world, the sprites are later drawn.

The screen is built tilewise in horizontal strips drawn left-to-right, with each strip drawn in top to bottom order. Transparent or uncovered areas of the map are filled with the backdrop image selected for the map. All tiles on the screen are fully redrawn during every frame, eliminating all need to erase screen content between calls. Page flipping is employed after each frame to ensure that a partially-updated screen is never shown to the user.

A Window to the World

The game window is 38 × 18 tiles in size, maintaining a one-tile blank border around its top, left, and right screen edges. This border remains black simply because nothing during the course of gameplay ever writes any nonzero data at those positions. The top-left tile inside the border is at screen position (1, 1) and reflects the map tile at position (scrollX, scrollY) – this controls which area of the map is visible as the player navigates through the game world (a world that is nearly 48 times larger than the scrolling window).

Game window position and scrolling variables.

scrollX and scrollY are bounded at all times to prevent the scrolling window from showing content outside the bounds of the map data.


The DrawMapRegion() function is called by the game loop and draws one complete frame of the static game world to the current draw page. This includes the solid and masked tiles read from the map data and the scrolling backdrop. The game window (everything except the status bar and the one-tile blank area around the perimeter of the screen) is fully redrawn during each call. This function does not draw any player/actor/decoration/etc. sprites; these will need to be drawn later.

The starting offset in the map data is governed by the scrollX and scrollY values. Changing these values will “pan” the window around the larger map area.

void DrawMapRegion(void)
    register word ymap;
    word dstoff = 321;
    word ymapmax;
    word yscreen = 1;
    word *mapcell;
    word bdoff;

This function maintains a fair number of long-lived variables:

Variable NameDescription
ymapThe vertical starting position where map data for the current tile row will be read from. It is an index into the mapData word array; changing the value by mapWidth moves one tile vertically. (Changing this value by one would move the read position horizontally by one tile, but this function does not do that.)
dstoffThe EGA address offset where the solid tiles are drawn into video memory to update the screen contents. Changing this value by one will address the next 8 × 1 pixel row horizontally. There are 40 of these across the width of the screen, and each new tile starts vertically on an 8 pixel row boundary. This is initialized to 321 to skip the first row of tiles on the screen (40 pixel rows, times 8 rows in a tile, producing the top border), incremented again to skip past the first tile on the left border.
ymapmaxThe stop position for ymap. Once this max value is reached, the final row of tiles has been drawn and there is nothing left for this function to do.
yscreenTracks the vertical drawing position on the screen, in tiles. This is used when drawing masked tiles, since the relevant drawing functions use a different addressing system than the solid tiles do. This starts at one to reflect the fact that the top row of tiles is skipped for the blank border.
mapcellPoints to the current tile in the source map data, and ultimately controls which solid or masked tile graphic is read for this screen position.
bdoffRepresents the vertical position of the current tile row relative to the game’s backdrop table. Each time a row of tiles is completed, this is incremented by 80 to skip one row down in the table.
bdsrcThe EGA address offset where the backdrop image data will be read from. There can be up to four versions of this data, each shifted in 4-pixel steps horizontally and/or vertically, to produce sub-tile scrolling effects. This is initialized to the distance between EGA_OFFSET_BDROP_EVEN and EGA_OFFSET_SOLID_TILES, which is explained below.
    if (hasHScrollBackdrop) {
        if (scrollX % 2 != 0) {
        } else {

If hasHScrollBackdrop is true, this block executes. This condition indicates that the map requests half-tile horizontal backdrop scrolling, and we will need to switch between two horizontal variants of the backdrop image: one that is unmodified, and another that has been shifted to the left by four pixels. Since every map shipped with the retail game uses horizontal scrolling, this block is never skipped.

The odd case (where scrollX % 2 is nonzero) is handled first. The constant EGA_OFFSET_SOLID_TILES is subtracted from EGA_OFFSET_BDROP_ODD_X, setting bdsrc to the constant value 7980h. This points to the first tile of backdrop image data for the horizontally-shifted variant of the backdrop, expressed in the way that DrawSolidTile() expects it.

Note: This warrants a special callout. DrawSolidTile() is usually called to draw solid tiles (hence the name), and biases its indexing such that a source offset of zero targets the first solid tile – not the first byte of the EGA memory segment. Contrarily, the EGA_OFFSET_* values are relative to the start of the EGA memory segment, necessitating a correction here.

In the case where scrollX is even, bdsrc is set based on the value of EGA_OFFSET_BDROP_EVEN instead, producing the constant value 6300h. This is the same value previously stored during bdsrc’s declaration earlier, making this a redundant assignment.

    if (scrollY > maxScrollY) scrollY = maxScrollY;

    if (hasVScrollBackdrop && (scrollY % 2 != 0)) {

Next is a bit of guard code. If scrollY managed to exceed the maximum defined in maxScrollY, clamp it to prevent scrolling off the bottom edge of the map. Such an error could influence the vertical background position, so it’s handled early here.

If hasVScrollBackdrop is true (the map requests vertical scrolling) and scrollY is odd, the backdrop needs to switch to its vertically-shifted variant.

To make sense of the increment to bdsrc, look at the EGA_OFFSET_* layout of the four backdrop variants:


The distance between EGA_OFFSET_BDROP_EVEN and EGA_OFFSET_BDROP_ODD_Y (2D00h) is the same as the distance between EGA_OFFSET_BDROP_ODD_X and EGA_OFFSET_BDROP_ODD_XY (2D00h). By adding either value to whatever horizontal component bdsrc already holds, we change “even” to “odd Y” and change “odd X” to “odd X and Y.”

    bdoff =
        (hasVScrollBackdrop ? 80 * ((scrollY / 2) % BACKDROP_HEIGHT) : 0) +
        (hasHScrollBackdrop ?       (scrollX / 2) % BACKDROP_WIDTH   : 0);

The other key bit of backdrop preparation is bdoff, which will point to a location within the backdrop table. To find the starting position (assuming the relevant scroll flags are enabled), scrollX and scrollY are each halved, and then wrapped modulo the BACKDROP_WIDTH and BACKDROP_HEIGHT respectively. The vertical component is multiplied by 80, which is the size of one row in the backdrop table’s data, then the horizontal and vertical components are added together to produce the final value of bdoff.

If either hasHScrollBackdrop or hasVScrollBackdrop is false, the relevant component contributes nothing to the value and the backdrop is pinned to the zeroth row and/or column.

This places bdoff somewhere inside the 40 × 18 quadrant at the top-left of the larger 80 × 36 backdrop table. The backdrop table exploits this setup to achieve horizontal and vertical wrapping of the backdrop image with zero additional overhead.


    ymapmax = (scrollY + SCROLLH) << mapYPower;
    ymap = scrollY << mapYPower;

This is the final bit of preparation before we can enter the drawing loops. EGA_MODE_LATCHED_WRITE() puts the EGA hardware in the appropriate state to draw solid tiles (the source data resides in EGA memory, and by leveraging the latches we can copy four bytes within EGA memory by manipulating a single memory byte with the CPU).

ymapmax is set to the sum of scrollY and SCROLLH (this is conceptually the first row of tiles that is obscured by the status bar at the bottom of the screen) and the result is shifted left by mapYPower to turn it into a map cell address. This is mathematically the same as multiplying it by the width of the map in tiles, except this is considerably faster.

ymap is calculated similarly, except it refers to the top row of map tiles about to be drawn on the screen.

    do {
        register int x = 0;

        do {
            mapcell = mapData.w + ymap + x + scrollX;

            if (*mapcell < TILE_STRIPED_PLATFORM) {
                DrawSolidTile(bdsrc + backdropTable[bdoff + x], x + dstoff);
            } else if (*mapcell >= TILE_MASKED_0) {
                DrawSolidTile(bdsrc + backdropTable[bdoff + x], x + dstoff);
                DrawMaskedTile(maskedTileData + *mapcell, x + 1, yscreen);
            } else {
                DrawSolidTile(*mapcell, x + dstoff);

        } while (x < SCROLLW);

        dstoff += 320;
        bdoff += 80;
        ymap += mapWidth;
    } while (ymap < ymapmax);

This pair of dowhile loops draws the screen. The outer loop runs 18 times in the vertical direction, and the inner loop runs 38 times per row to produce horizontal coverage. At the start of each outer loop iteration, x resets to zero. (x is explicitly declared using the register storage class to influence the compiler’s decision-making and match the way the original game was compiled.)

The inner loop works as follows: the word member of the mapData union is used as a base, to which ymap, x, and scrollX are added. This makes mapcell point to the tile of map data that is going to be drawn at this position on the screen.

Depending on the data read from *mapcell, one of three things can happen:

  • When *mapcell is less than TILE_STRIPED_PLATFORM, the map data should not be drawn. This tile is conceptually “air” or an invisible platform movement marker. In this case, DrawSolidTile() is called to fill this position with a tile of backdrop imagery. bdoff and x are summed to produce an index into backdropTable[], which results in an offset that gets added to bdsrc to locate the correct source offset in the EGA memory. The destination of this write is the vertical dstoff plus the current x position.
  • When *mapcell is equal to or greater than TILE_MASKED_0 (which is the boundary between the end of solid tiles and the start of masked tiles), then the game draws one masked tile superimposed on a backdrop tile. It draws the backdrop first, using the exact same approach as the previous bullet. DrawMaskedTile() then draws the masked tile over the backdrop that was just drawn by adding *mapcell’s value to the maskedTileData base address, and using x + 1 and yscreen as the destination tile coordinates. (x needs to be adjusted by one because it counts from zero, while the screen is drawn starting at column one due to the blank border.)
  • In the default case, *mapcell has a larger value than an air tile, but a smaller value than a masked tile. The solid tiles reside in this range. Drawing them is a simple matter of calling DrawSolidTile() with the *mapcell value to select the source tile image, and x + dstoff to locate the destination EGA offset to write this image to.

At the bottom of the inner loop, x is incremented to step one tile to the right in preparation for the next iteration. The loop stops once x reaches SCROLLW, indicating that the right edge of the tile row has been reached.

The bottom of the outer loop contains similar bookkeeping. dstoff is advanced by 320, which is the size (in EGA address space) of one tile row. (That’s 40 tiles, each containing 8 pixel rows, with each pixel row using one byte of address space.) yscreen is incremented by one, referring to the next row of tiles. bdoff is incremented by 80, which is the size of one data row in the backdrop table. ymap is incremented by the current value of mapWidth, which steps to the same horizontal position one tile down in the map data. The loop stops once ymap reaches ymapmax, indicating that the whole screen has been redrawn.


The DrawRandomEffects() function is called by the game loop and adds random decorative effects to the game world based on what is currently visible on the screen. It applies a sparkling effect to map tiles that have the “slippery” attribute, and adds raindrops (if rain is enabled on the map) in any unoccupied areas at the top edge of the screen.

void DrawRandomEffects(void)
    word x = scrollX + random(SCROLLW);
    word y = scrollY + random(SCROLLH);
    word maptile = GetMapTile(x, y);

The function starts by defining three variables. x selects a random position horizontally along the map, constrained to the area between scrollX and a position SCROLLW tiles to the right. Likewise y is a random map position between scrollY and SCROLLH tiles below it. This selects a point somewhere in map space that is currently visible within the scrolling game window.

These coordinates are passed to GetMapTile() to read the tile value from the map data. This is stored in maptile.

    if (random(2U) != 0 && TILE_SLIPPERY(maptile)) {
        NewDecoration(SPR_SPARKLE_SLIPPERY, 5, x, y, DIR8_STATIONARY, 1);

random() sets up a 50/50 chance that this block will execute, along with a test for TILE_SLIPPERY() on the maptile that was chosen earlier. If both conditions are true, NewDecoration is called to add SPR_SPARKLE_SLIPPERY to the map at this (x, y) position. The sparkle animation consists of five frames, does not move (DIR8_STATIONARY), and the effect plays only once per call.

Only one position on the map is considered per frame. If the chosen tile is not slippery, no decoration is added during that frame.

    if (hasRain) {
        y = scrollY + 1;

        if (GetMapTile(x, y) == TILE_EMPTY) {
            NewDecoration(SPR_RAINDROP, 1, x, y, DIR8_SOUTHWEST, 20);

Additionally, if the hasRain flag is true, the map has rain enabled and raindrop decorations should be added to the map.

The y position is fudged to the current scrollY position plus one. It is unclear why this addition is done, since it (incorrectly) prevents rain from appearing in the topmost tile row of the game window. The x position remains the random horizontal position selected at the top of the function.

GetMapTile() returns the tile value at this (x, y) position, and if it contains TILE_EMPTY then there is empty space at this location – a raindrop sprite can fit there. NewDecoration is called to add SPR_RAINDROP to the map at this (x, y) position. The raindrop consists of one frame, always moves in the DIR8_SOUTHWEST direction, and the decoration persists for a maximum of 20 loops. This is more than enough opportunity for it to reach the bottom of the game window, which is only 18 tiles high.

Umbrellas are futile!

The physics of rain in this game don’t make a lot of sense. Rain will not form where solid tiles occupy the top of the screen, yet existing raindrops will happily pass through any and all solid tiles anywhere below. An solid “umbrella”-type structure would do nothing to shield from the raindrops in this game, unless it happened to occupy the top edge where the raindrops initially spawn.

There is special-purpose code in MoveAndDrawDecorations that pertains to raindrop movement, causing them to travel faster than any other moving decoration in the game.


The DrawLights() function iterates through all the lights present on the current map and draws any that are currently scrolled into view. If areLightsActive is false, this function does nothing.

Each light is defined only by the upper edges of its cone; the brightening effect floods down in a one tile wide vertical strip from each light actor until it hits a solid map tile or it exceeds the episode’s LIGHT_CAST_DISTANCE limit. Lights have a “west” edge, a mirrored “east” edge, and a filled “middle” section directly beneath the light source. Taken together, these three different light types create a triangular area where anything touched by the light becomes brightened. As this modifies content already on the screen, this should be one of the last functions called while drawing a frame – anything drawn after this function returns will not receive the lighting effect.

Light types, typical construction, and flooding behavior.

Note: Pay special attention to the light fixture in the game screenshot on the left above. It does not contribute to the lighting effect; it is merely an arrangement of four solid map tiles, no different from any other decorative element in the game. Only the lightened gray trapezoidal area is part of the lighting system.

A map designer should be mindful of how many lights are present in the level and how many tiles they can cover. (The example image contains 18 lights: eight west, eight east, and two middle types. There is an additional 70 tiles of flooding.) The game must evaluate the full area flooded by every light on the map to determine if any part of the effect enters the scrolling game window. This is recomputed from scratch every frame. Conceivably this would allow for situations like moving platforms dynamically interrupting the flooded area and casting “shadows,” but none of the stock maps do this and the result looks unconvincing in practice:

Interaction between lights and platforms.

The unlit area beneath the platform moves as a shadow would.

void DrawLights(void)
    register word i;

    if (!areLightsActive) return;


The variable i is an index used later to iterate through each light present on the current map. The global areLightsActive variable is checked at the beginning to determine if the lights are turned on. If they are not, the value will be false and the function returns early.

Otherwise, the lights are on and we need to draw them. EGA_MODE_DEFAULT() resets the EGA hardware into its default state, which disables any latch-copying mode that might be left over from a previous solid tile drawing call.

    for (i = 0; i < numLights; i++) {
        register word y;
        word xorigin, yorigin;
        word side = lights[i].side;

        xorigin = lights[i].x;
        yorigin = lights[i].y;

A for loop iterates over all of the lights currently present on the map. These are stored sequentially as Light structures in the lights[] array. numLights controls how many array elements to read. xorigin and yorigin are set to the (X, Y) tile coordinates on the map where each light has been placed, while side holds a value that controls the shape of its top tile. y is an iterator variable used later in the vertical flooding loop.

        if (
            xorigin >= scrollX && scrollX + SCROLLW > xorigin &&
            yorigin >= scrollY && scrollY + SCROLLH - 1 >= yorigin
        ) {
            if (side == LIGHT_SIDE_WEST) {
                    (xorigin - scrollX) + 1, (yorigin - scrollY) + 1
            } else if (side == LIGHT_SIDE_MIDDLE) {
                    (xorigin - scrollX) + 1, (yorigin - scrollY) + 1
            } else {
                    (xorigin - scrollX) + 1, (yorigin - scrollY) + 1

This draws the topmost tile on a single vertical strip of light. The outer if checks if this tile is scrolled into view by ensuring that xorigin is between scrollX and the screen edge SCROLLW tiles to the right. The vertical test is the same, using yorigin, scrollY, and SCROLLH, although it chooses to adjust the bottom check by one tile so it can use a greater-or-equal test instead.

If the tile is determined to be within the bounds of the scrolling game window, another if block is evaluated. This one decides, based on the value in side, which type of light to draw here. LIGHT_SIDE_WEST results in a call to LightenScreenTileWest(), LIGHT_SIDE_MIDDLE leads to LightenScreenTile(), and the default case (logically must be LIGHT_SIDE_EAST) gets LightenScreenTileEast().

Regardless of the function selected, the arguments passed are the same each time. The screen space X coordinate is determined by subtracting the scrollX position from xorigin and adding one to compensate for the one-tile blank border at the left edge of the screen. Y is calculated the same way by taking the distance between yorigin and scrollY and correcting for the top border. The screen content at that position is brightened, producing different shapes depending on the specific function that was called.

        for (y = yorigin + 1; yorigin + LIGHT_CAST_DISTANCE > y; y++) {
            if (TILE_BLOCK_SOUTH(GetMapTile(xorigin, y))) break;

            if (
                xorigin >= scrollX && scrollX + SCROLLW > xorigin &&
                y >= scrollY && scrollY + SCROLLH - 1 >= y
            ) {
                    (xorigin - scrollX) + 1, (y - scrollY) + 1

The remainder of the loop body handles the downward flood that occurs under each light, which continues until it hits a blocking map tile or LIGHT_CAST_DISTANCE tiles have been covered. The for loop starts the y iterator variable at yorigin plus one because we start flooding immediately below the tile where the light originated. The loop continues incrementing y downward on the screen until one of its exit conditions is reached.

Note: This loop runs for every strip of every light on the map, no matter what is visible on the screen. This is due to the fact that there are scroll positions where the head tile of the light is not in view, but parts of its flood are.

At each step, GetMapTile(xorigin, y) reads the map tile in that position and checks its tile attributes using TILE_BLOCK_SOUTH(). If the tile contains an attribute bit that blocks southern movement, the loop breaks – the light has reached a solid surface that it should not pass into.

Otherwise, a visibility check occurs. This is identical to the earlier check that was performed on the head tile of the light, but this uses the current value of y. If this position is within the scrolling game window, the screen tile is lightened via a call to LightenScreenTile() similarly to how the head tile was.

At the conclusion of the flood loop, the outer “per light” loop repeats until all of the lights have been evaluated. Once that’s done, the function returns.