Visions the Amulet Never Showed: Myst IV: Revelation (2004)

One settings line, a silenced console, and an unused vision of Spire

Part 4 of 5 in Behind the Ages

The Revelation Graph maps the connections between the game’s 618 stored nodes. Alongside that network, Ubisoft Montreal’s engine also leaves behind two ways to step behind the curtain: a plain-text configuration line that opens any stored node on launch, and a developer console disabled by a single instruction. [Node labels such as w5_z04_n111 have a thick underline, in the color of their Age, and open that place in the graph browser of the game.]

Revelation’s five easter eggs, photographs of the teams that made the game, are known to its players, with the taps that open them. Beyond those, the files reveal how to choose the starting node and how to turn the console back on. [Version of the game: Myst IV: Revelation, version 1.03 for Windows.]

One Line to Start Anywhere

How to reach it.

  1. Quit the game. In the folder where the game is installed, open the folder data, which holds data.m4b.

  2. Create there a text file named data.dsc with these lines, the settings packed in data.m4b with their first line changed, putting the name of a stored node of the Revelation Graph in place of w5_z04_n111:

    set_initial_context(w5_z04_n111)
    
    {autoload
        ai(true)
        interpolator(true)
        lightsets(true)
        layer(true)
        panel(true)
        commandblock(true)
        hotspot(true)
        flare(true)
        geometry(true)
        rail(true)
        overlay(true)
        water(true)
        skyreflection(true)
        widget(true)
        zplane(true)
        soundloader(true)
    }
    
    {localisation
        default_language( english )
        {languages
            english(true)
            french(true)
            dutch(true)
            spanish(true)
            italian(true)
            german(true)
            japanese(true)
        }
    }
    
    {ai_library
        m4_ai_thor      (true)
        m4_ai_global    (true)
        m4_ai_w1        (true)
        m4_ai_w2        (true)
        m4_ai_w3        (true)
        m4_ai_w4        (true)
        m4_ai_w5        (true)
        m4_ai_w6        (true)
        m4_ai_all       (true)
    }
    
  3. Start the game: it opens in that node, with no logo, no film and no menu.

  4. To get the ordinary start back, delete the file.

The engine reads its settings from text files.1 One of them, data.dsc, begins with the line set_initial_context(w6_z01_n021), and that name is a node of the graph (w6_z01_n021): the one that plays the logos and the opening film. Another name there, and the game opens somewhere else. This file is packed inside the archive data.m4b, and a loose file of the same name, beside the archive, takes its place. The rest of the packed file lists the parts of the engine to load, the languages and the game’s libraries. The start line alone is not enough: without the list of libraries, the game never opens its window.

With set_initial_context(w5_z04_n111), six seconds after its window appears, the game stands in front of a box of the laboratory of Tomahna, by day (w5_z04_n111), with its hand, its interface and its sound. No logo, no film and no menu come first.

A close view in the laboratory of Tomahna by day: a rounded brass box closed by a shutter of dark slats with a handle at the bottom, and red leaves behind a window at the left.

The first picture of the game, with one line changed.

The engine reads game.dsc first, then a loose data.dsc if one exists, then user.dsc, and finally the packed data.dsc only if no loose copy was found. Because a setting read twice keeps its last value, the start line does nothing in game.dsc or user.dsc in an unmodified install, where the packed data.dsc runs last and overwrites it. Once a loose data.dsc is in place, the packed one is skipped and user.dsc runs last: a file bin\user.dsc holding the start line alone then decides where the game opens, whatever data.dsc says. Any stored node can serve as the starting point. The graph’s virtual targets have no node archive to load.

Among them is a place that the game never shows. w3_z01_n032 is a vision of the amulet in Spire that no place names: in the cell where it belongs, w3_z01_n031, the amulet plays a film instead.2 With its name in the line, the game opens on it: the cell, clean and lit behind its bars, misty at the edges as the amulet’s visions are, with a sound of its own. After about 14 seconds a white flash ends it, and the game stands in the cell itself, dark and ruined.

The amulet’s vision of a cell of Spire, slightly hazy: a tall bell-shaped cell of pale metal, lit from above, seen through its open door, with bars and a bed behind them, crystals of rock at the left and clouds at the right.

w3_z01_n032, opened by the start line.

A Console Switched Off by One Instruction

How to reach it.

  1. Copy the folder of the game (version 1.03) and work in the copy.
  2. In bin\m4_thor_rd.dll, find the twelve bytes 5F 88 9E AD 00 00 00 8B C6 5E 5D 5B, which occur once (at offset 0x1FCDC), and replace the six that follow 5F with 90 90 90 90 90 90.
  3. Start the game from the copy and press the key left of 1 (` on a US keyboard, ² on a French one). The same key closes the console.

The engine holds a whole console: pages of text, a command line with its history, and a header that draws the frame rate, the orientation of the camera and the name of the current node. Its constructor sets it up and, in its last instruction, switches it off. The function that would switch it on again is exported, and no library of the game calls it. The change above removes that last instruction.

The round door of a puzzle of Serenia, dark metal crossed by two bars, under green and orange text: a header with PAGE NAME default, FOV 90.00, the node name w4 z06 n061, the frame rate and the time of a frame, PITCH 0.0 and YAW 0.0, then a dark box of six lines: Solution Spot#0 is 1, Spot#1 is 200, Spot#2 is 2, Spot#3 is 2, Spot#4 is 1, Spot#5 is 100.

The console over the round door of Serenia: its header, then six lines printed by the key M.

You can type anything you like at the prompt; the console clears the line with great composure and does nothing at all. No library of the game listens to it, and at each start the game looks for a library named m4_ai_debug that it does not have.

One library still writes to it. In front of that round door, the close view of a puzzle (w4_z06_n061), the key M (the M of a QWERTY keyboard; on a French one, the comma) generates six puzzle values and prints them, from “Solution Spot#0” to “Solution Spot#5”, each with a value among 1, 2, 10, 20, 100 and 200. The values differ between new games. The code writes them to the puzzle’s variables before printing them, but a game saved just after M still holds those variables empty. I have not established whether the door uses the printed values.

Conclusion

Unlike Exile’s typed developer code, Revelation leaves no in-game cheat code to type, yet its configuration files and compiled libraries remain surprisingly open, much like Myst V’s encrypted settings files would a year later. One edited line restores a complete vision of Spire that the amulet never plays, and six nopped bytes bring back a developer console that still reports the current node and prints debug output for Serenia’s puzzle.


  1. The settings files themselves are known: a game.dsc of one line to play in a window has been passed around since 2011 at least, and PCGamingWiki gives it; the fan tool M4Revolution writes a user.dsc, and the notes of m4fix name data.dsc. The Revelation Editor of realXCV has opened the nodes of the game in its own viewer since 2009. ↩︎

  2. The second Revelation Graph article found it in the data: the vision names the cell as the place to go back to, and the cell does not name it. ↩︎