<?xml version="1.0" encoding="utf-8" standalone="yes"?><?xml-stylesheet type="text/xsl" href="/rss.xsl"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:glthr="https://glthr.com/ns/rss"><channel><title>Myst IV: Revelation | GLTHR.com, by Guillaume Lethuillier</title><link>https://glthr.com/tag/revelation</link><description>Articles in Myst IV: Revelation on glthr.com.</description><language>en</language><lastBuildDate>Sat, 21 Nov 2026 00:00:09 +0000</lastBuildDate><atom:link href="https://glthr.com/tag/revelation/" rel="self" type="application/rss+xml"/><item><title>The Revelation Graph, 2: Where the Nodes Stand</title><link>https://glthr.com/revelation-graph-2</link><guid isPermaLink="true">https://glthr.com/revelation-graph-2</guid><pubDate>Sat, 21 Nov 2026 00:00:09 +0000</pubDate><dc:creator>Guillaume Lethuillier</dc:creator><description>What the Revelation graph shows that the game hides, on a 3D map: one passage from day to night, nodes close yet far apart, and eleven names without a node.</description><content:encoded><![CDATA[<aside class="callout callout-note">
  <span class="callout-emoji" aria-hidden="true">✎</span>
  <div class="callout-body"><p class="callout-title">Work in progress — November 21, 2026</p>
    <p>I am still working in <strong>Myst IV: Revelation</strong>. I will update these articles over the coming weeks, so please feel free to come back later to see what’s new.</p>
  </div>
</aside><aside class="callout callout-abstract">
  <span class="callout-emoji" aria-hidden="true">↘</span>
  <div class="callout-body">
    <p>Revelation stores where each of its 618 nodes stands, so its graph can be compared with its own map:</p>
<ul>
<li><strong>One passage:</strong> a single connection leads from Tomahna by day to Tomahna by night, and 557 nodes lie behind the node where it starts. No node stores it: it is written in compiled code.</li>
<li><strong>Near and far:</strong> nodes that stand a step apart can be eleven connections apart, and many nodes without a picture stand where the node they were copied from stands.</li>
<li><strong>Names without things:</strong> eleven targets that the discs do not store, a table of neighbors that lists fourteen nodes that no longer exist, and a transition that the day names and only the night stores.</li>
<li><strong>No picture:</strong> thirty nodes have no picture layer, among them the five photographs of the game’s easter eggs and the Dream that ends the game.</li>
</ul>
<p>The files show what was left behind, not why. This article contains spoilers.</p>
  </div>
</aside><h2 id="heading-introduction">Introduction<a class="anchor" href="#heading-introduction" aria-hidden="true" tabindex="-1">#</a></h2>
<p>The Revelation Graph, <a href="https://glthr.com/revelation-graph-1">introduced in the previous article</a>, draws the 618 nodes of Myst IV: Revelation and the references between them. <span class="inline-update sidenote" role="note"><em><span class="inline-update-bracket">[</span>Version of the game: Myst IV: Revelation 1.0, the original English release on two DVDs, September 2004. The node names are those of this release.<span class="inline-update-bracket">]</span></em></span> As with <a href="https://glthr.com/myst-graph-2">Myst</a>, <a href="https://glthr.com/riven-graph-2">Riven</a> and <a href="https://glthr.com/exile-graph-2">Exile</a>, I now look at what the graph shows that playing does not. To my knowledge, the findings presented here are new, except where I credit earlier work. Any node named below can be found <a href="https://glthr.com/revelation-graph">in the explorable graph</a>, where each link of this article opens the node it names.</p>
<h3 id="heading-visual-indicators">Visual Indicators<a class="anchor" href="#heading-visual-indicators" aria-hidden="true" tabindex="-1">#</a></h3>
<p>I keep the two indicators of <a href="https://glthr.com/myst-graph-2#heading-visual-indicators">the Myst findings</a>. A crossed-out eye on a view means that the game never displays it, as far as the stored references can tell: nothing leads to the node that holds it. An open eye means that the view is displayed in the game. Every view of this article has an open eye. <span class="inline-update sidenote" role="note"><em><span class="inline-update-bracket">[</span>Node labels such as <a href="https://glthr.com/revelation-graph#w5_z01_n020" data-stack="revelation-w5">w5_z01_n020</a> have a thick underline, in the color of their Age, and open that node in the graph browser.<span class="inline-update-bracket">]</span></em></span></p>
<p>A panorama is shown unrolled, twice as wide as it is high, with its front face at the center. Only the default picture of a node is shown: the movies, the water and the sky that the game adds are left out, and the sky is black. Edges under discussion are drawn in red, as in the earlier figures.</p>
<p>The maps are new. They draw the nodes as dots at the positions that the game stores, seen from above or from the side, with a line for each connection.</p>
<h3 id="heading-disclaimer">Disclaimer<a class="anchor" href="#heading-disclaimer" aria-hidden="true" tabindex="-1">#</a></h3>
<p>The <a href="https://glthr.com/revelation-graph-1#heading-disclaimer">disclaimer of the first article</a> applies. This article contains spoilers for the game, including its ending.</p>
<h2 id="heading-general">General<a class="anchor" href="#heading-general" aria-hidden="true" tabindex="-1">#</a></h2>
<h3 id="heading-shortest-theoretical-path">Shortest Theoretical Path<a class="anchor" href="#heading-shortest-theoretical-path" aria-hidden="true" tabindex="-1">#</a></h3>
<p>A new game begins in Tomahna by day, at <a href="https://glthr.com/revelation-graph#w5_z01_n010" data-stack="revelation-w5">w5_z01_n010</a>. The three Ages are reached from Tomahna by night. From the first node to the arrival in Serenia (<a href="https://glthr.com/revelation-graph#w4_z01_n010" data-stack="revelation-w4">w4_z01_n010</a>), the nearest of the three, the theoretical minimum distance is 32 edges:</p>
<p><a href="https://glthr.com/revelation-graph#w5_z01_n010" data-stack="revelation-w5">w5_z01_n010</a> → <a href="https://glthr.com/revelation-graph#w5_z01_n020" data-stack="revelation-w5">w5_z01_n020</a> → <a href="https://glthr.com/revelation-graph#w5_z02_n010" data-stack="revelation-w5">w5_z02_n010</a> → <a href="https://glthr.com/revelation-graph#w5_z02_n020" data-stack="revelation-w5">w5_z02_n020</a> → <a href="https://glthr.com/revelation-graph#w5_z02_n140" data-stack="revelation-w5">w5_z02_n140</a> → <a href="https://glthr.com/revelation-graph#w5_z02_n030" data-stack="revelation-w5">w5_z02_n030</a> → <a href="https://glthr.com/revelation-graph#w5_z02_n130" data-stack="revelation-w5">w5_z02_n130</a> → <a href="https://glthr.com/revelation-graph#w5_z01_n290" data-stack="revelation-w5">w5_z01_n290</a> → <a href="https://glthr.com/revelation-graph#w5_z01_n040" data-stack="revelation-w5">w5_z01_n040</a> → <a href="https://glthr.com/revelation-graph#w5_z01_n050" data-stack="revelation-w5">w5_z01_n050</a> → <a href="https://glthr.com/revelation-graph#w5_z04_n010" data-stack="revelation-w5">w5_z04_n010</a> → <a href="https://glthr.com/revelation-graph#w5_z04_n020" data-stack="revelation-w5">w5_z04_n020</a> → <a href="https://glthr.com/revelation-graph#w5_z04_n040" data-stack="revelation-w5">w5_z04_n040</a> → <a href="https://glthr.com/revelation-graph#w5_z04_n140" data-stack="revelation-w5">w5_z04_n140</a> → <a href="https://glthr.com/revelation-graph#w5_z04_n050" data-stack="revelation-w5">w5_z04_n050</a> → <a href="https://glthr.com/revelation-graph#w5_z04_n060" data-stack="revelation-w5">w5_z04_n060</a> → <a href="https://glthr.com/revelation-graph#w5_z04_n080" data-stack="revelation-w5">w5_z04_n080</a> → <a href="https://glthr.com/revelation-graph#w5_z01_n110" data-stack="revelation-w5">w5_z01_n110</a> → <a href="https://glthr.com/revelation-graph#w1_z01_n310" data-stack="revelation-w1">w1_z01_n310</a> → <a href="https://glthr.com/revelation-graph#w1_z01_n090" data-stack="revelation-w1">w1_z01_n090</a> → <a href="https://glthr.com/revelation-graph#w1_z04_n080" data-stack="revelation-w1">w1_z04_n080</a> → <a href="https://glthr.com/revelation-graph#w1_z04_n060" data-stack="revelation-w1">w1_z04_n060</a> → <a href="https://glthr.com/revelation-graph#w1_z04_n050" data-stack="revelation-w1">w1_z04_n050</a> → <a href="https://glthr.com/revelation-graph#w1_z04_n140" data-stack="revelation-w1">w1_z04_n140</a> → <a href="https://glthr.com/revelation-graph#w1_z04_n090" data-stack="revelation-w1">w1_z04_n090</a> → <a href="https://glthr.com/revelation-graph#w1_z04_n100" data-stack="revelation-w1">w1_z04_n100</a> → <a href="https://glthr.com/revelation-graph#w1_z04_n120" data-stack="revelation-w1">w1_z04_n120</a> → <a href="https://glthr.com/revelation-graph#w1_z03_n010" data-stack="revelation-w1">w1_z03_n010</a> → <a href="https://glthr.com/revelation-graph#w1_z03_n030" data-stack="revelation-w1">w1_z03_n030</a> → <a href="https://glthr.com/revelation-graph#w1_z03_n070" data-stack="revelation-w1">w1_z03_n070</a> → <a href="https://glthr.com/revelation-graph#w1_z03_n080" data-stack="revelation-w1">w1_z03_n080</a> → <a href="https://glthr.com/revelation-graph#w1_z03_n090" data-stack="revelation-w1">w1_z03_n090</a> → <a href="https://glthr.com/revelation-graph#w4_z01_n010" data-stack="revelation-w4">w4_z01_n010</a>.</p>
<p><a class="img-link" href="https://glthr.com/images/revelation-graph-2/revelation-shortest-path.w.png" title="Open full size (2400×1695)"><img class="has-dark" src="https://glthr.com/images/revelation-graph-2/revelation-shortest-path.w-1800w.png" alt="The complete Revelation graph at left, with a shortest route of 32 connections and 33 nodes highlighted in red from Tomahna by day through Tomahna by night to Serenia. At right, its endpoints have open eyes: the cabin at w5 z01 n010 and the cave entrance at w4 z01 n010." width="1800" height="1271" data-full="/images/revelation-graph-2/revelation-shortest-path.w.png" data-full-width="2400" loading="lazy" decoding="async"></a></p>
<p>The route spends seventeen edges in the day, crosses into the night and walks back through the same building in the dark: the same zone and, for four nodes in a row, the same numbers in the other order. For comparison, reaching the final destination took <a href="https://glthr.com/myst-graph-2#heading-shortest-theoretical-path">24 edges in Myst</a> and <a href="https://glthr.com/riven-graph-2#heading-shortest-theoretical-path">3 in Riven</a>, while reaching Narayan in <a href="https://glthr.com/exile-graph-2#heading-shortest-theoretical-path">Exile took 23</a>; here, 32 edges only reach the entrance of Serenia. As explained <a href="https://glthr.com/revelation-graph-1#heading-paths">in the first article</a>, a path in the graph is a distance between nodes, never a way to finish the game.</p>
<h3 id="heading-one-passage-into-the-night">One Passage Into the Night<a class="anchor" href="#heading-one-passage-into-the-night" aria-hidden="true" tabindex="-1">#</a></h3>
<p>Tomahna is stored twice. By day it has 67 nodes, by night 126. <strong>Of the 67 nodes of the day, 63 have a node of the night with the same zone and the same number, and 59 of those stand at exactly the same position.</strong> The night is the larger world: four of its eight zones have no counterpart by day.</p>
<p>The two worlds are almost sealed from each other. Apart from five close-ups that the day borrows from the night, described below, exactly one connection takes the player from the day into the night, and no node stores it: it is compiled, in the class of <a href="https://glthr.com/revelation-graph#w5_z01_n110" data-stack="revelation-w5">w5_z01_n110</a>:</p>
<p><a class="img-link" href="https://glthr.com/images/revelation-graph-2/revelation-day-night.w.png" title="Open full size (2400×1245)"><img class="has-dark" src="https://glthr.com/images/revelation-graph-2/revelation-day-night.w-1800w.png" alt="Top: the yellow box of the day node w5 z01 n110 joined by a dashed purple arrow, labeled engine, to the blue box of the night node w1 z01 n310. Below, the panoramas of the two nodes, with open eyes: by day, a wooden walkway with railings and lamp posts between red rocks and two domed buildings; by night, planks and steps between dark rocks under a blue light." width="1800" height="934" data-full="/images/revelation-graph-2/revelation-day-night.w.png" data-full-width="2400" loading="lazy" decoding="async"></a></p>
<p><em>The passage from day to night. The class of <a href="https://glthr.com/revelation-graph#w5_z01_n110" data-stack="revelation-w5">w5_z01_n110</a> builds it in compiled code: a transition to world 1, zone 1, node 310, with the panel of the node called <code>p_explosion</code>. <a href="https://glthr.com/revelation-graph#w1_z01_n310" data-stack="revelation-w1">w1_z01_n310</a> stands 2.7 units from where the day ends.</em></p>
<p>Everything else hangs from it. Of the 609 nodes that the first node reaches, <strong>557 lie behind <a href="https://glthr.com/revelation-graph#w5_z01_n110" data-stack="revelation-w5">w5_z01_n110</a></strong>: every route to them passes through that node. The route to the farthest node has 67 such unavoidable nodes, and the first seventeen are the way from the first node to that one.</p>
<p>The passage is not a click. When <a href="https://glthr.com/revelation-graph#w5_z01_n110" data-stack="revelation-w5">w5_z01_n110</a> becomes the current node, its class reads two variables of the power puzzle, <code>clap1_open</code> and <code>clap2_open</code>, and starts the transition only if both are false. A new game begins with both true, so the first walk through the node changes nothing. No command writes them: compiled classes do, and I did not read which act of the player sets them. The game’s own name for the movie of the passage is an explosion.</p>
<p>I tried it in the game. With both variables false, one step onto <a href="https://glthr.com/revelation-graph#w5_z01_n110" data-stack="revelation-w5">w5_z01_n110</a> plays the collapse of the walkway, and the player comes to at night in <a href="https://glthr.com/revelation-graph#w1_z01_n310" data-stack="revelation-w1">w1_z01_n310</a>. With both true, the same step is an ordinary one.</p>
<p><a class="img-link" href="https://glthr.com/images/revelation-graph-2/revelation-passage-ingame.png" title="Open full size (1920×360)"><img src="https://glthr.com/images/revelation-graph-2/revelation-passage-ingame-1800w.png" alt="Three frames of the game side by side. Left, by day, a wooden walkway with iron railings runs between red rocks toward a building with a domed roof. Middle, the same walkway tips over the water, its railing across the picture. Right, by night, a pale branch over dark rocks under a blue light." width="1800" height="338" data-full="/images/revelation-graph-2/revelation-passage-ingame.png" data-full-width="1920" loading="lazy" decoding="async"></a></p>
<p><em>The passage in the game: the walkway before the step, its collapse, and the first view of the night, <a href="https://glthr.com/revelation-graph#w1_z01_n310" data-stack="revelation-w1">w1_z01_n310</a>.</em></p>
<p><a href="https://media.glthr.com/revelation-graph-2/revelation-passage.mp4" target="_blank" rel="noopener"><img src="https://glthr.com/images/revelation-graph-2/revelation-passage-poster.jpg" alt="Myst IV Revelation by day, on the walkway to the laboratory, with both gates of the power puzzle shut: one click forward, the walkway gives way over the water, the screen goes black, and the player comes to at night among the rocks."></a></p><p>[Video: Myst IV Revelation by day, on the walkway to the laboratory, with both gates of the power puzzle shut: one click forward, the walkway gives way over the water, the screen goes black, and the player comes to at night among the rocks.]</p>
<p>The passage arrives at <a href="https://glthr.com/revelation-graph#w1_z01_n310" data-stack="revelation-w1">w1_z01_n310</a>, a panorama of the path outside, by night, with one hotspot, which leads to <a href="https://glthr.com/revelation-graph#w1_z01_n090" data-stack="revelation-w1">w1_z01_n090</a>, 4 units away. In the stored data, nothing leads to that node: no command, no parameter, no arrival record, and its neighbor has no hotspot toward it. Its entrance is three constants in the library of the day: 1, 1 and 310. The day has no node of that number, and the night has no node 110: <a href="https://glthr.com/revelation-graph#w5_z01_n110" data-stack="revelation-w5">w5_z01_n110</a> is one of four nodes of the day without a twin, with the first node of the game and the two nodes that lie beyond it.</p>
<p>What the data does name between the two worlds is a leftover. The day node <a href="https://glthr.com/revelation-graph#w5_z02_n160" data-stack="revelation-w5">w5_z02_n160</a> runs a class named for its twin of the night, and one of its parameters holds <code>w5_z02_n160.tr_w1_z02_n170</code>, a transition toward a node of the night. The day node stores no such transition; its twin, <a href="https://glthr.com/revelation-graph#w1_z02_n160" data-stack="revelation-w1">w1_z02_n160</a>, stores one of that name, toward its neighbor. The value was renamed with the rest of the node when one Tomahna was made from the other, and it points at nothing. The graph does not draw it.</p>
<p>The day and the night do share something: five close-ups, stored once, in the night. A drawer of the day opens on <a href="https://glthr.com/revelation-graph#w1_z02_n032" data-stack="revelation-w1">w1_z02_n032</a>, a node of the night, and so does the same drawer at night. These views store no way out. The engine goes back to the last node, whichever it was. <a href="https://glthr.com/revelation-graph-1#heading-returns-that-belong-to-the-caller">The first article</a> explains why the graph draws those returns and does not follow them: without that rule, the shortest path into the night would go through a drawer. That is a lot to ask of a drawer.</p>
<p>One name points the other way. Three nodes of the night use a class named for the day, <code>w5_z04_incub</code>, and each gives it the name of a close-up: <a href="https://glthr.com/revelation-graph#w1_z04_n110" data-stack="revelation-w1">w1_z04_n110</a> and <a href="https://glthr.com/revelation-graph#w1_z04_n120" data-stack="revelation-w1">w1_z04_n120</a> give <a href="https://glthr.com/revelation-graph#w1_z04_n102" data-stack="revelation-w1">w1_z04_n102</a>, a close-up of the night, and <a href="https://glthr.com/revelation-graph#w1_z04_n090" data-stack="revelation-w1">w1_z04_n090</a> still gives <a href="https://glthr.com/revelation-graph#w5_z04_n102" data-stack="revelation-w5">w5_z04_n102</a>, the same close-up by day. Two of the three names were changed when the day became the night, and the third was not. It changes nothing: the class does not open the close-up it names. It only compares the name with the last node the player visited, to know whether the player comes back from it. I tried it in the game: from these nodes, nothing on the incubator opens a close-up. The graph does not draw the name as a connection, and nothing leads from the night back to the day.</p>
<h3 id="heading-longest-shortest-theoretical-path">Longest Shortest Theoretical Path<a class="anchor" href="#heading-longest-shortest-theoretical-path" aria-hidden="true" tabindex="-1">#</a></h3>
<p>The longest shortest path follows 87 edges, from <a href="https://glthr.com/revelation-graph#w2_z05_n171" data-stack="revelation-w2">w2_z05_n171</a>, a fixed view at the end of Haven, to <a href="https://glthr.com/revelation-graph#w4_z06_n330" data-stack="revelation-w4">w4_z06_n330</a>, in the Dream of Serenia. One pair of nodes reaches it:</p>
<p><a class="img-link" href="https://glthr.com/images/revelation-graph-2/revelation-longest-shortest-path.w.png" title="Open full size (2400×1695)"><img class="has-dark" src="https://glthr.com/images/revelation-graph-2/revelation-longest-shortest-path.w-1800w.png" alt="The complete Revelation graph at left, with the longest shortest route of 87 connections and 88 nodes highlighted in red from Haven through Tomahna by night to the Dream of Serenia. At right, the source w2 z05 n171 has an open eye over a view of a wooden mechanism among leaves. The destination w4 z06 n330 has a dashed empty frame because no picture is stored." width="1800" height="1271" data-full="/images/revelation-graph-2/revelation-longest-shortest-path.w.png" data-full-width="2400" loading="lazy" decoding="async"></a></p>
<p>The path leaves Haven by its whole length, links back to the room of the books in Tomahna, crosses the night to the link to Serenia and walks Serenia to its end. In Exile, the same measure was 189 edges; in Riven, 125; in Myst, 130. Revelation is the smallest graph of the four and the most compact: the average distance between two of its nodes is 30.2 edges, against 58 in Exile.</p>
<h3 id="heading-what-zip-mode-buys">What Zip Mode Buys<a class="anchor" href="#heading-what-zip-mode-buys" aria-hidden="true" tabindex="-1">#</a></h3>
<p>Zip mode is a ribbon of thumbnails: a click on one sends the player to a node already visited, in the same Age. The thumbnails are stored, two pictures per place, and they give the list: <strong>28 Zip places</strong>, seven in Tomahna by night, six in Haven, six in Spire, five in Serenia and four in Tomahna by day.</p>
<p>Zip places are not drawn in the graph: each can be entered from every node of its Age, once visited. Adding them to the model gives what the mode buys. The longest shortest path falls from 87 to 24, the average distance from 30.2 to 7.9, and the farthest node from the first one is 22 edges away instead of 74.</p>
<h3 id="heading-few-hubs">Few Hubs<a class="anchor" href="#heading-few-hubs" aria-hidden="true" tabindex="-1">#</a></h3>
<p>The busiest node is <a href="https://glthr.com/revelation-graph#w1_z07_n030" data-stack="revelation-w1">w1_z07_n030</a>, a room of Tomahna by night: seven connections lead to it and ten leave it. No node has more than ten exits. Ninety percent of the connections join two nodes that stand less than 11 units apart: the graph is a set of corridors, as in Exile, and its hubs are rooms.</p>
<h2 id="heading-the-graph-and-the-map">The Graph and the Map<a class="anchor" href="#heading-the-graph-and-the-map" aria-hidden="true" tabindex="-1">#</a></h2>
<h3 id="heading-neighbors-that-are-far-apart">Neighbors That Are Far Apart<a class="anchor" href="#heading-neighbors-that-are-far-apart" aria-hidden="true" tabindex="-1">#</a></h3>
<p>With positions, a new question can be asked: which nodes stand close to each other and are far apart in the graph?</p>
<p><a href="https://glthr.com/revelation-graph#w1_z02_n010" data-stack="revelation-w1">w1_z02_n010</a> and <a href="https://glthr.com/revelation-graph#w1_z02_n150" data-stack="revelation-w1">w1_z02_n150</a> are two panoramas of the same building, 3.5 units apart, which is the length of an ordinary step of this game. The shortest path between them has <strong>11 edges</strong>.</p>
<p><a class="img-link" href="https://glthr.com/images/revelation-graph-2/revelation-near-and-far.w.png" title="Open full size (2400×1350)"><img class="has-dark" src="https://glthr.com/images/revelation-graph-2/revelation-near-and-far.w-1800w.png" alt="Two drawings of the same nodes of Tomahna by night as dots joined by lines, from above and from the side. Two dots circled in red stand next to each other. A thick red line leaves one, goes around through nine other dots and comes back to the other." width="1800" height="1013" data-full="/images/revelation-graph-2/revelation-near-and-far.w.png" data-full-width="2400" loading="lazy" decoding="async"></a></p>
<p><em>Two nodes a step apart in space and eleven edges apart in the graph. The red line is the shortest path between them.</em></p>
<p>The side view shows why: <a href="https://glthr.com/revelation-graph#w1_z02_n150" data-stack="revelation-w1">w1_z02_n150</a> stands 2.5 units higher, on the upper level. The path to it goes around the whole building. The graph measures the walk, the map measures the room, and their difference is the architecture.</p>
<p>The same comparison finds <a href="https://glthr.com/revelation-graph#w4_z06_n170" data-stack="revelation-w4">w4_z06_n170</a> and <a href="https://glthr.com/revelation-graph#w4_z06_n230" data-stack="revelation-w4">w4_z06_n230</a>, in Serenia: 4 units and 10 edges.</p>
<h3 id="heading-positions-that-were-copied">Positions That Were Copied<a class="anchor" href="#heading-positions-that-were-copied" aria-hidden="true" tabindex="-1">#</a></h3>
<p>The opposite case is a connection between two nodes that stand far apart. Half of the connections are shorter than 3.2 units, and nine in ten are shorter than 11. A few are much longer. Inside a zone, the longest ones all have one end in a node that stores no picture.</p>
<p>The reason is in the numbers themselves. <a href="https://glthr.com/revelation-graph#w2_z01_n181" data-stack="revelation-w2">w2_z01_n181</a> is a journal of Haven, a fixed view without a picture. It stands 189 units from the panorama it belongs to, at the position, to a tenth of a unit, of <a href="https://glthr.com/revelation-graph#w1_z03_n091" data-stack="revelation-w1">w1_z03_n091</a>: a journal of Tomahna. <a href="https://glthr.com/revelation-graph#w4_z02_n181" data-stack="revelation-w4">w4_z02_n181</a>, a journal of Serenia, stands exactly where <a href="https://glthr.com/revelation-graph#w2_z06_n153" data-stack="revelation-w2">w2_z06_n153</a>, a journal of Haven, does. Five nodes of three Ages share one position to the last decimal: <a href="https://glthr.com/revelation-graph#w1_z04_n115" data-stack="revelation-w1">w1_z04_n115</a>, <a href="https://glthr.com/revelation-graph#w5_z04_n115" data-stack="revelation-w5">w5_z04_n115</a>, <a href="https://glthr.com/revelation-graph#w1_z07_n034" data-stack="revelation-w1">w1_z07_n034</a>, <a href="https://glthr.com/revelation-graph#w2_z06_n012" data-stack="revelation-w2">w2_z06_n012</a> and <a href="https://glthr.com/revelation-graph#w3_z03_n054" data-stack="revelation-w3">w3_z03_n054</a>. It is the position of <a href="https://glthr.com/revelation-graph#w1_z04_n111" data-stack="revelation-w1">w1_z04_n111</a>, a fixed view of Tomahna. These five are not journals: they are the photographs of the game’s easter eggs, <a href="#heading-thirty-nodes-without-a-picture">described below</a>, and <a href="https://glthr.com/revelation-graph#w1_z04_n111" data-stack="revelation-w1">w1_z04_n111</a> is the close-up that opens one of them.</p>
<p><strong>These matching positions suggest that nodes were copied and their coordinates left unchanged.</strong> A journal copied from another Age would bring its old position with it, even though the new view needs none. The maps of this study leave these 30 nodes out. Their coordinates offer clues to how the nodes were made, rather than reliable places on the map.</p>
<p>Between two zones, a few long connections join nodes that both have a picture. The longest is in Spire: <a href="https://glthr.com/revelation-graph#w3_z02_n500" data-stack="revelation-w3">w3_z02_n500</a> and <a href="https://glthr.com/revelation-graph#w3_z04_n100" data-stack="revelation-w3">w3_z04_n100</a> are 227 units apart and one click apart, in both directions. That one is a journey.</p>
<h2 id="heading-nodes-without-an-entrance">Nodes Without an Entrance<a class="anchor" href="#heading-nodes-without-an-entrance" aria-hidden="true" tabindex="-1">#</a></h2>
<p>Five nodes outside the menu are not reached from the first node. Seven nodes are entered only by compiled code: five of them are reached that way, and two are not.</p>
<h3 id="heading-entered-by-compiled-code">Entered by Compiled Code<a class="anchor" href="#heading-entered-by-compiled-code" aria-hidden="true" tabindex="-1">#</a></h3>
<p><a href="https://glthr.com/revelation-graph#w2_z05_n082" data-stack="revelation-w2">w2_z05_n082</a> to <a href="https://glthr.com/revelation-graph#w2_z05_n086" data-stack="revelation-w2">w2_z05_n086</a>, five fixed views of Haven, are the five branches of one compiled choice: the same call changes node with 82, 83, 84, 85 or 86 as its last number. The routine belongs to the class of <a href="https://glthr.com/revelation-graph#w2_z05_n080" data-stack="revelation-w2">w2_z05_n080</a>, which picks the branch from an index, and a class that the five views share leads back to it. <a href="https://glthr.com/revelation-graph#w4_z06_n310" data-stack="revelation-w4">w4_z06_n310</a> and <a href="https://glthr.com/revelation-graph#w4_z06_n320" data-stack="revelation-w4">w4_z06_n320</a>, in the Dream, are two more constants, side by side in the library of Serenia: the class of <a href="https://glthr.com/revelation-graph#w4_z06_n260" data-stack="revelation-w4">w4_z06_n260</a> reads a variable and goes to the first when it is 0, to the second when it is 1.</p>
<p>None of these routines names a node. Each is given to a node by its class: the method that calls the routine or hands it over, and the node that lists the class (<a href="https://glthr.com/revelation-graph-1#heading-what-the-compiled-classes-do">the first article</a> describes the reading). The five views of Haven are reached that way. The two nodes of the Dream are not, since their own origin is not.</p>
<h3 id="heading-three-others">Three Others<a class="anchor" href="#heading-three-others" aria-hidden="true" tabindex="-1">#</a></h3>
<p><a href="https://glthr.com/revelation-graph#w3_z01_n032" data-stack="revelation-w3">w3_z01_n032</a> is a vision of the amulet in Spire. A vision is normally named by the node it belongs to, and names it in return. This one names <a href="https://glthr.com/revelation-graph#w3_z01_n031" data-stack="revelation-w3">w3_z01_n031</a> as the node to go back to, and <a href="https://glthr.com/revelation-graph#w3_z01_n031" data-stack="revelation-w3">w3_z01_n031</a> does not name it. Changing one settings line lets the game <a href="https://glthr.com/revelation-visions-the-amulet-never-showed#heading-one-line-to-start-anywhere">open and play this unused vision directly</a>.</p>
<p><a href="https://glthr.com/revelation-graph#w3_z04_n200" data-stack="revelation-w3">w3_z04_n200</a> is a panorama of Spire without a picture. One of the two nodes that the interface treats as fixed whatever their kind, it stores limits for a pitch, a yaw and a zoom: it is a view through an instrument. <a href="https://glthr.com/revelation-graph#w3_z04_n190" data-stack="revelation-w3">w3_z04_n190</a> records the direction to face when arriving from it, and nothing stored goes the other way.</p>
<p><a href="https://glthr.com/revelation-graph#w4_z06_n260" data-stack="revelation-w4">w4_z06_n260</a> belongs to the Dream, which a later section describes: it leads to <a href="https://glthr.com/revelation-graph#w4_z06_n310" data-stack="revelation-w4">w4_z06_n310</a> and <a href="https://glthr.com/revelation-graph#w4_z06_n320" data-stack="revelation-w4">w4_z06_n320</a>, and both lead back to it, but nothing that path search follows enters the three.</p>
<h2 id="heading-what-the-discs-name-and-do-not-hold">What the Discs Name and Do Not Hold<a class="anchor" href="#heading-what-the-discs-name-and-do-not-hold" aria-hidden="true" tabindex="-1">#</a></h2>
<h3 id="heading-eleven-nodes-that-are-not-there">Eleven Nodes That Are Not There<a class="anchor" href="#heading-eleven-nodes-that-are-not-there" aria-hidden="true" tabindex="-1">#</a></h3>
<p>Eleven targets are named by the data and have no archive on the disc:</p>
<p><a class="img-link" href="https://glthr.com/images/revelation-graph-2/revelation-absent-nodes.w.png" title="Open full size (2400×1170)"><img class="has-dark" src="https://glthr.com/images/revelation-graph-2/revelation-absent-nodes.w-1800w.png" alt="Eleven pairs of boxes. In each pair, a colored box for a stored node points with a red arrow to a dashed white box for a target that is not stored: three targets named by one node of Tomahna by night, three targets of Haven, four of Spire and one of Serenia." width="1800" height="878" data-full="/images/revelation-graph-2/revelation-absent-nodes.w.png" data-full-width="2400" loading="lazy" decoding="async"></a></p>
<p>Two are named by commands. In Spire, a click in <a href="https://glthr.com/revelation-graph#w3_z02_n060" data-stack="revelation-w3">w3_z02_n060</a> runs <code>ContextChange(3,02,080)</code>, and in Serenia a click in <a href="https://glthr.com/revelation-graph#w4_z06_n230" data-stack="revelation-w4">w4_z06_n230</a> runs <code>ContextChange(4,06,090)</code>. Neither node exists. What would start these commands is stored as well, a click on a hotspot of that name, but not the hotspots themselves: neither node keeps a shape for them, so no click can reach them. Of the 1,017 clicks that the data ties to a move, these are two of the six without a hotspot.</p>
<p>The nine others are named by compiled code: hotspot names written as constants in the libraries, or parameters of compiled classes. The library of the night names three hotspots of <a href="https://glthr.com/revelation-graph#w1_z07_n030" data-stack="revelation-w1">w1_z07_n030</a>, the busiest node of the graph: <code>h_to_w1_z01_n031</code>, <code>h_to_w1_z01_n032</code> and <code>h_to_w1_z01_n033</code>. The node has none of them. Its own are called <code>h_to_w1_z07_n031</code> to <code>h_to_w1_z07_n033</code>, and they lead to three close-ups that are stored. By the convention of the node numbers, the names of the code would be three fixed views of a panorama numbered 30 in zone 1, and that panorama is not stored either.</p>
<p>A name that leads nowhere is not necessarily a mistake. Compiled code can name a hotspot that it never uses, or use it for something other than a move. The graph records the name and draws the target as virtual.</p>
<h3 id="heading-a-table-of-neighbors-from-an-earlier-version">A Table of Neighbors From an Earlier Version<a class="anchor" href="#heading-a-table-of-neighbors-from-an-earlier-version" aria-hidden="true" tabindex="-1">#</a></h3>
<p>Beside the node archives, the main archive holds a small file, <code>nodedb.ndb</code>: a table that gives, for each node, the nodes next to it. According to <a href="https://github.com/rsheasby/m4fix/blob/main/docs/TECHNICAL.md" target="_blank" rel="noopener">a study of the engine’s performance</a>, the routine that would read it is an empty stub in the released program, so the game never uses it. The same study notes that the table is stale: some of its names are of nodes that no longer exist, and 249 nodes have no entry.</p>
<p>The table has 383 entries, and the graph shows the earlier state of the game that it describes:</p>
<ul>
<li><strong>14 of its entries are for nodes that no longer exist</strong>, such as <code>w1_z01_n004</code>, <code>w4_z02_n014</code> or <code>w4_z06_n188</code>, and four more names of that kind appear only among the neighbors: 18 in all. Twelve of the 14 have a number that ends in 4.</li>
<li><strong>249 of the 618 stored nodes have no entry.</strong></li>
<li>Where it joins two stored nodes, the graph already joins them: the table adds no connection.</li>
</ul>
<p>The table and the virtual targets overlap. <a href="https://glthr.com/revelation-graph#w3_z02_n080" data-stack="revelation-w3">w3_z02_n080</a> and <a href="https://glthr.com/revelation-graph#w4_z06_n090" data-stack="revelation-w4">w4_z06_n090</a>, the two nodes that commands still ask for, are also listed in it as neighbors.</p>
<h3 id="heading-names-that-kept-an-older-number">Names That Kept an Older Number<a class="anchor" href="#heading-names-that-kept-an-older-number" aria-hidden="true" tabindex="-1">#</a></h3>
<p>The parameters of the compiled classes have names, and seven names disagree with their values. In Spire, the class of <a href="https://glthr.com/revelation-graph#w3_z05_n030" data-stack="revelation-w3">w3_z05_n030</a> has a parameter called <code>m_h_to_w3_z05_n040</code>. Its value is the hotspot <code>h_to_w3_z05_n050</code>. There is no node 40 in that zone: the parameter was named when there was one, and the name is compiled into the library.</p>
<p>Two of the seven show how the night was made. The class of the day node <a href="https://glthr.com/revelation-graph#w5_z01_n020" data-stack="revelation-w5">w5_z01_n020</a> has a parameter named for a node of the night, and the class of the night node <a href="https://glthr.com/revelation-graph#w1_z02_n130" data-stack="revelation-w1">w1_z02_n130</a> has one named for a node of the day. The two Tomahnas share their classes, and each class was named in one world and reused in the other.</p>
<p>In all, the parameters mention 20 names of nodes that are not stored.</p>
<h3 id="heading-commands-that-were-switched-off">Commands That Were Switched Off<a class="anchor" href="#heading-commands-that-were-switched-off" aria-hidden="true" tabindex="-1">#</a></h3>
<p>Much like <a href="https://glthr.com/myst-graph-2#heading-mysterious-missing-direct-link-from-myst-island-to-selenitic-age">Myst’s commented-out HyperTalk lines</a>, a command that starts with a semicolon is ignored. The game stores <strong>1,185 such lines</strong> among its 28,980. Most are settings that were tried and replaced. A few name things that the node no longer has: the first block of <a href="https://glthr.com/revelation-graph#w1_z01_n020" data-stack="revelation-w1">w1_z01_n020</a> still holds, switched off, a command that sets the state of a panel called <code>p_levi_vehi</code> and another that selects a state of the picture called <code>state_w1_z01_vehicule_hidder</code>. Neither the panel nor the state is stored in the node. <em>Véhicule</em> is French for vehicle: something that could be hidden once stood there. Between the French <em>véhicule</em> and the English <em>hidder</em> (with a spare <em>d</em>), the commented-out line also preserves a small bilingual souvenir of Montreal.</p>
<h2 id="heading-thirty-nodes-without-a-picture">Thirty Nodes Without a Picture<a class="anchor" href="#heading-thirty-nodes-without-a-picture" aria-hidden="true" tabindex="-1">#</a></h2>
<p>Thirty nodes store no picture layer at all. Most are fixed views whose content is a movie or a book: the journals, which the game draws page by page on a panel, and several close-ups of mechanisms. Five have no class either, and <a href="#heading-positions-that-were-copied">one position for all five</a>: they are the photographs of the game’s five easter eggs, long known to its players. Each stores an animation that carries a photograph of one of the teams that made the game, and a close-up opens it after eight taps in a given order, which a compiled class called <code>easter_egg</code> counts.</p>
<p>Seven are panoramas. One is the view through an instrument of Spire, <a href="https://glthr.com/revelation-graph#w3_z04_n200" data-stack="revelation-w3">w3_z04_n200</a>, <a href="#heading-three-others">described above</a>. The six others, <a href="https://glthr.com/revelation-graph#w4_z04_n240" data-stack="revelation-w4">w4_z04_n240</a>, <a href="https://glthr.com/revelation-graph#w4_z04_n250" data-stack="revelation-w4">w4_z04_n250</a>, <a href="https://glthr.com/revelation-graph#w4_z06_n260" data-stack="revelation-w4">w4_z06_n260</a>, <a href="https://glthr.com/revelation-graph#w4_z06_n310" data-stack="revelation-w4">w4_z06_n310</a>, <a href="https://glthr.com/revelation-graph#w4_z06_n320" data-stack="revelation-w4">w4_z06_n320</a> and <a href="https://glthr.com/revelation-graph#w4_z06_n330" data-stack="revelation-w4">w4_z06_n330</a> are panoramas of Serenia, and they are the Dream.</p>
<p><a class="img-link" href="https://glthr.com/images/revelation-graph-2/revelation-no-picture.w.png" title="Open full size (2400×1245)"><img class="has-dark" src="https://glthr.com/images/revelation-graph-2/revelation-no-picture.w-1800w.png" alt="Top: the box of w4 z06 n220 joined by a dashed green arrow, labeled automatic, to the box of w4 z06 n330. Below, on the left, a panorama with an open eye: a chamber of pipes, wheels and a ladder of metal under a rock ceiling. On the right, a dashed empty frame with the words: no picture is stored, the Dream is drawn as it is played." width="1800" height="934" data-full="/images/revelation-graph-2/revelation-no-picture.w.png" data-full-width="2400" loading="lazy" decoding="async"></a></p>
<p><em>The entrance of the Dream. <a href="https://glthr.com/revelation-graph#w4_z06_n220" data-stack="revelation-w4">w4_z06_n220</a> has a panorama; <a href="https://glthr.com/revelation-graph#w4_z06_n330" data-stack="revelation-w4">w4_z06_n330</a>, where its command sends the player, has none.</em></p>
<p>In the rest of the game, a node is a picture rendered in advance, with movies laid over it. In the Dream, the classes of the nodes take objects, halos, particles and positions as parameters, and no cube: the scene is drawn while it is played. The world of pictures that began with Myst ends here, inside its fourth game, in six nodes.</p>
<p>The Dream is also where the two automatic connections of the graph are. A command called <code>cmd_dream_mask_effect</code>, started by a class and by no click, changes node: the player does not walk into the Dream.</p>
<p>And it is where the graph stops. <a href="https://glthr.com/revelation-graph#w4_z06_n260" data-stack="revelation-w4">w4_z06_n260</a> is not reached from the first node: the one command that leads to it from a reached node is among the nine that nothing stored starts, and the two other nodes that lead to it are entered from it alone. The last steps of the game are compiled.</p>
<h2 id="heading-conclusion">Conclusion<a class="anchor" href="#heading-conclusion" aria-hidden="true" tabindex="-1">#</a></h2>
<p>The graph of Revelation is the smallest of the series and the most regular. Outside the menu, its numbers follow a rule without exception, its commands can be read aloud, and nearly every step can be walked back.</p>
<p>What it adds is a second drawing. Because each node knows where it stands, the graph can be laid over the place it describes, and the differences between the two are findings of their own: a level that turns one step into eleven, a journal of Haven that stands in Tomahna, a whole world behind one node.</p>
<p>What is left over is thin and precise: a transition that the day names and only the night stores, eleven names without a node, a table of neighbors from an earlier version, a vehicle switched off. And the ending is where the method runs out, in six nodes that have no picture to show.</p>
]]></content:encoded></item><item><title>The Revelation Graph, 1: The 2004 Game as a Graph</title><link>https://glthr.com/revelation-graph-1</link><guid isPermaLink="true">https://glthr.com/revelation-graph-1</guid><pubDate>Sat, 21 Nov 2026 00:00:09 +0000</pubDate><dc:creator>Guillaume Lethuillier</dc:creator><description>Myst IV: Revelation (2004) as a graph of 618 nodes to explore in two and three dimensions: its panoramas, fixed views, commands, and the positions it stores.</description><content:encoded><![CDATA[<aside class="callout callout-note">
  <span class="callout-emoji" aria-hidden="true">✎</span>
  <div class="callout-body"><p class="callout-title">Work in progress — November 21, 2026</p>
    <p>I am still working in <strong>Myst IV: Revelation</strong>. I will update these articles over the coming weeks, so please feel free to come back later to see what’s new.</p>
  </div>
</aside><aside class="callout callout-abstract">
  <span class="callout-emoji" aria-hidden="true">↘</span>
  <div class="callout-body">
    <p>I represent the original Myst IV: Revelation (2004) as a directed graph of 618 stored nodes and 11 virtual targets. Its 1,355 typed connections combine readable commands, class parameters, constants in compiled code and 63 inferred connections, which are marked as such. For the first time in the series, the game also stores where each node stands, so the graph can be drawn as a map in three dimensions. This first article explains the graph, its browser view and its limits. It describes structural relationships, without executing the state that determines which ones a player can follow.</p>
  </div>
</aside><p>After <a href="https://glthr.com/myst-graph-1">Myst</a>, <a href="https://glthr.com/riven-graph-1">Riven</a> and <a href="https://glthr.com/exile-graph-1">Exile</a>, the fourth game was not an obvious candidate. <span class="inline-update sidenote" role="note"><em><span class="inline-update-bracket">[</span>Version of the game: Myst IV: Revelation 1.0, the original English release on two DVDs, September 2004. The node names are those of this release.<span class="inline-update-bracket">]</span></em></span> Revelation was made by Ubisoft Montreal, with an engine of its own.</p>
<p>Revelation can nevertheless be viewed as a graph:</p>
<p><a class="img-link" href="https://glthr.com/images/revelation-graph-1/revelation-graph-overview.w.png" title="Open full size (2448×2132)"><img class="has-dark" src="https://glthr.com/images/revelation-graph-1/revelation-graph-overview.w-1800w.png" alt="The complete Revelation graph inside a thin rectangular frame, titled The Revelation Graph with the subtitle Myst IV: Revelation (2004) as a Graph. Small labeled nodes are colored by Age and joined by arrows: Tomahna by day in yellow and by night in blue, Haven in green, Spire in purple and Serenia in pink. A selection rectangle connects to a magnified inset at the bottom right: the main page of the menu, w6 z06 n011, joined by a thick dashed arrow to the first node of a new game, w5 z01 n010, which leads to the panorama w5 z01 n020 and its fixed view. Below the frame, the footer reads glthr.com." width="1800" height="1568" data-full="/images/revelation-graph-1/revelation-graph-overview.w.png" data-full-width="2448" loading="lazy" decoding="async"></a></p>
<p>The Revelation Graph can be <a href="https://glthr.com/revelation-graph"><strong>explored in the browser</strong></a>, where any node can be found by its name, and where the same nodes can be seen as a map.</p>
<h2 id="heading-disclaimer">Disclaimer<a class="anchor" href="#heading-disclaimer" aria-hidden="true" tabindex="-1">#</a></h2>
<p>This is an unofficial, non-commercial study of Myst IV: Revelation (2004), independent of Cyan Worlds and Ubisoft. The game artwork remains the work of its creators. The analysis contains spoilers and reads the released data without executing every possible world state. Stored references, parameters of compiled classes, constants read in compiled code and inferred connections are identified separately.</p>
<h2 id="heading-introduction">Introduction<a class="anchor" href="#heading-introduction" aria-hidden="true" tabindex="-1">#</a></h2>
<h3 id="heading-roadmap">Roadmap<a class="anchor" href="#heading-roadmap" aria-hidden="true" tabindex="-1">#</a></h3>
<p><em>(1)</em> In this article, I introduce the Revelation Graph and explain its nodes, arrows and colors. <a href="#heading-archives-inside-archives">Archives Inside Archives</a> describes where the game keeps its navigation.</p>
<p><em>(2)</em> In <a href="https://glthr.com/revelation-graph-2">the second article</a>, I compare the graph with the game’s pictures and positions: theoretical paths, the one passage from day to night, nodes that stand close and are far apart, eleven targets that are named and not stored, and thirty nodes without a picture. The figures use the same node labels, graph excerpts and eye indicators as the Myst, Riven and Exile findings.</p>
<h3 id="heading-one-archive-per-node">One Archive per Node<a class="anchor" href="#heading-one-archive-per-node" aria-hidden="true" tabindex="-1">#</a></h3>
<p>Like Exile, Revelation is a world of places: the player stands in a <strong>node</strong> and looks all around. Turning loads nothing. A node is either a <strong>panorama</strong>, seen in every direction, or a <strong>fixed view</strong>, a close-up of a drawer, a lever or a page that the player cannot turn in.</p>
<p>The game stores each node as one archive. Inside it are the picture, the hotspots, the sounds, the movies and the instructions of that node, and nothing of another node. The picture of a panorama is a cube of six faces, and each face is cut into 36 tiles of 128 pixels. A tile that is entirely transparent is not stored: the sky is drawn behind the cube by other means.</p>
<p><a class="img-link" href="https://glthr.com/images/revelation-graph-1/revelation-tiles-to-node.w.png" title="Open full size (2400×1350)"><img class="has-dark" src="https://glthr.com/images/revelation-graph-1/revelation-tiles-to-node.w-1800w.png" alt="Left: one face of the cube of the node w5 z01 n020, a round metal doorway at the end of a wooden walkway, under a red grid of six by six tiles. An arrow leads to the panorama assembled from the six faces, twice as wide as it is high, on which two red squares mark the two hotspots of the node. Below, the single box that this node occupies in the graph, labeled with its name and the word panorama." width="1800" height="1013" data-full="/images/revelation-graph-1/revelation-tiles-to-node.w.png" data-full-width="2400" loading="lazy" decoding="async"></a></p>
<p><em>A node of Tomahna as the game stores it (six faces of 36 tiles), as this study displays it (one panorama, the front face at its center) and as the graph draws it (one box).</em></p>
<p>Revelation has <strong>618 nodes</strong>: 382 panoramas and 236 fixed views. Exile has 820 places and Riven 2,307 cards. The figure is small for a game on two DVDs, and the reason is the same as in Exile: a node is a whole sphere, and here a sphere over which movies, water and moving light are laid.</p>
<h3 id="heading-what-is-in-this-graph">What Is in This Graph?<a class="anchor" href="#heading-what-is-in-this-graph" aria-hidden="true" tabindex="-1">#</a></h3>
<p>The game names a node by three numbers: a world, a zone and a node. <code>w5_z01_n020</code> is node 20 of zone 1 of world 5. The worlds are the Ages, with two particularities. Tomahna is stored twice, by day and by night. And the menu is a world of its own, whose nodes are its pages.</p>
<div class="table-wrap">
<table>
  <thead>
      <tr>
          <th>World</th>
          <th>Age</th>
          <th style="text-align: right">Zones</th>
          <th style="text-align: right">Nodes</th>
          <th style="text-align: right">Panoramas</th>
          <th style="text-align: right">Fixed views</th>
      </tr>
  </thead>
  <tbody>
      <tr>
          <td><code>w5</code></td>
          <td>Tomahna, by day</td>
          <td style="text-align: right">4</td>
          <td style="text-align: right">67</td>
          <td style="text-align: right">43</td>
          <td style="text-align: right">24</td>
      </tr>
      <tr>
          <td><code>w1</code></td>
          <td>Tomahna, by night</td>
          <td style="text-align: right">8</td>
          <td style="text-align: right">126</td>
          <td style="text-align: right">72</td>
          <td style="text-align: right">54</td>
      </tr>
      <tr>
          <td><code>w2</code></td>
          <td>Haven</td>
          <td style="text-align: right">8</td>
          <td style="text-align: right">154</td>
          <td style="text-align: right">97</td>
          <td style="text-align: right">57</td>
      </tr>
      <tr>
          <td><code>w3</code></td>
          <td>Spire</td>
          <td style="text-align: right">6</td>
          <td style="text-align: right">120</td>
          <td style="text-align: right">69</td>
          <td style="text-align: right">51</td>
      </tr>
      <tr>
          <td><code>w4</code></td>
          <td>Serenia</td>
          <td style="text-align: right">6</td>
          <td style="text-align: right">136</td>
          <td style="text-align: right">101</td>
          <td style="text-align: right">35</td>
      </tr>
      <tr>
          <td><code>w6</code></td>
          <td>Menu</td>
          <td style="text-align: right">2</td>
          <td style="text-align: right">15</td>
          <td style="text-align: right">0</td>
          <td style="text-align: right">15</td>
      </tr>
      <tr>
          <td><strong>Total</strong></td>
          <td></td>
          <td style="text-align: right"></td>
          <td style="text-align: right"><strong>618</strong></td>
          <td style="text-align: right"><strong>382</strong></td>
          <td style="text-align: right"><strong>236</strong></td>
      </tr>
  </tbody>
</table>
</div>
<p>Eleven virtual targets bring the total to 629 nodes. World and zone are attributes used for labels, colors and filters: they have no vertices of their own.</p>
<p>The node numbers carry a convention that the data never states and, outside the menu, always follows. Every panorama has a number that ends in 0, and no fixed view does: the fixed views of a panorama take the numbers that follow it, and <a href="https://glthr.com/revelation-graph#w1_z01_n021" data-stack="revelation-w1"><code>w1_z01_n021</code></a> is a close-up of <a href="https://glthr.com/revelation-graph#w1_z01_n020" data-stack="revelation-w1"><code>w1_z01_n020</code></a>.</p>
<p>The names are the game’s own, and one of them even decides where it opens: changing the first line of the settings file <code>data.dsc</code> starts the game directly in any stored node, as shown in <a href="https://glthr.com/revelation-visions-the-amulet-never-showed#heading-one-line-to-start-anywhere">Visions the Amulet Never Showed</a>.</p>
<h2 id="heading-basic-properties-of-the-revelation-graph">Basic Properties of the Revelation Graph<a class="anchor" href="#heading-basic-properties-of-the-revelation-graph" aria-hidden="true" tabindex="-1">#</a></h2>
<p><em>Node labels such as <a href="https://glthr.com/revelation-graph#w5_z01_n020" data-stack="revelation-w5">w5_z01_n020</a> have a thick underline, in the color of their Age, and open that node in the graph browser.</em></p>
<h3 id="heading-nodes-and-edges">Nodes and Edges<a class="anchor" href="#heading-nodes-and-edges" aria-hidden="true" tabindex="-1">#</a></h3>
<p>The graph has 629 nodes: 618 stored nodes and the 11 virtual targets described <a href="#heading-virtual-targets">below</a>. Its 1,355 typed connections are summarized in <a href="#heading-reading-a-connection">the table of connections</a>.</p>
<h3 id="heading-paths">Paths<a class="anchor" href="#heading-paths" aria-hidden="true" tabindex="-1">#</a></h3>
<p>A new game begins at <a href="https://glthr.com/revelation-graph#w5_z01_n010" data-stack="revelation-w5">w5_z01_n010</a>, in Tomahna by day. The first node of the night, <a href="https://glthr.com/revelation-graph#w1_z01_n310" data-stack="revelation-w1">w1_z01_n310</a>, is 18 connections away. The arrival in Serenia, <a href="https://glthr.com/revelation-graph#w4_z01_n010" data-stack="revelation-w4">w4_z01_n010</a>, is 32 connections away, and the arrivals in Haven and in Spire are 40 away. The two most distant nodes of the graph are 87 connections apart (189 in Exile, 125 in Riven, 130 in Myst). As in the earlier games, a path is a distance between nodes and says nothing about the puzzles that stand on it. <a href="https://glthr.com/revelation-graph-2">The second article</a> gives the routes.</p>
<h3 id="heading-clusters">Clusters<a class="anchor" href="#heading-clusters" aria-hidden="true" tabindex="-1">#</a></h3>
<p>The drawing groups nodes by Age, and the grouping is nearly exact: only 20 connections join two worlds. Tomahna by night sits in the middle. Haven and Spire are entered from one of its rooms and return to it, and Serenia is reached from it. Tomahna by day leads to the night once and is never returned to.</p>
<p>From the first node, 609 of the 629 nodes are reached. The 20 others are the 15 pages of the menu and 5 nodes that <a href="https://glthr.com/revelation-graph-2">the second article</a> examines.</p>
<h3 id="heading-a-graph-that-has-a-shape">A Graph That Has a Shape<a class="anchor" href="#heading-a-graph-that-has-a-shape" aria-hidden="true" tabindex="-1">#</a></h3>
<p>The graphs of Myst, Riven and Exile have no shape of their own. Their drawings are computed: a program places the boxes so that the arrows are short, and another program would place them differently.</p>
<p>Revelation is different. <strong>Each node stores three numbers that are its position</strong>, in the axes of its Age, the third one upward. Two nodes that a connection joins stand, in the median, 3.2 units apart. Two nodes of the same Age picked at random stand about 48 units apart. The numbers are therefore the place where the node was rendered, and the nodes of an Age, drawn at their positions, give its map. The 30 nodes that store no picture are the exception: <a href="https://glthr.com/revelation-graph-2#heading-positions-that-were-copied">many of their positions appear to be copies</a>, so the maps leave all 30 out.</p>
<p><a class="img-link" href="https://glthr.com/images/revelation-graph-1/revelation-stored-positions.w.png" title="Open full size (2400×1350)"><img class="has-dark" src="https://glthr.com/images/revelation-graph-1/revelation-stored-positions.w-1800w.png" alt="Two drawings of dots joined by thin lines. Left, Tomahna by night seen from above: clusters of dots for the buildings, joined by longer lines for the walkways. Right, Spire seen from the side: a tall stack of dots, a long horizontal line to a small group far to the left, and another group below." width="1800" height="1013" data-full="/images/revelation-graph-1/revelation-stored-positions.w.png" data-full-width="2400" loading="lazy" decoding="async"></a></p>
<p><em>Two Ages drawn from the stored positions alone. Tomahna by night, from above, is 60 units by 48. Spire, from the side, is 155 units high.</em></p>
<p>The <a href="https://glthr.com/revelation-graph">graph browser</a> therefore has two drawings. The graph is the one of the earlier articles. The map places the nodes where the game stores them and can be turned and zoomed, one Age at a time or the five together. The game says nothing of where an Age lies from another, since they are different worlds: in the view of all five, their arrangement is a choice of the page.</p>
<p>The hotspots agree with the positions. A hotspot that leads to another node is stored with its own offset from the node, and that offset points at the destination: for 754 of the 872 hotspots that I could compare, the angle between the two directions is under 30 degrees.</p>
<h2 id="heading-legend-how-to-read-the-graph">Legend: How to Read the Graph<a class="anchor" href="#heading-legend-how-to-read-the-graph" aria-hidden="true" tabindex="-1">#</a></h2>
<p>The <a href="https://glthr.com/revelation-graph">browser graph</a> uses a node’s Age for its color, its references for its connections, and distinct borders or arrowheads for special cases. The following legend explains those conventions before the findings put them to use.</p>
<h3 id="heading-reading-a-node">Reading a Node<a class="anchor" href="#heading-reading-a-node" aria-hidden="true" tabindex="-1">#</a></h3>
<h4 id="heading-labels-and-colors">Labels and Colors<a class="anchor" href="#heading-labels-and-colors" aria-hidden="true" tabindex="-1">#</a></h4>
<p>Each Age has its own color. A label is the name that the game gives the node, unchanged: <a href="https://glthr.com/revelation-graph#w5_z01_n020" data-stack="revelation-w5">w5_z01_n020</a> is world 5, zone 1, node 20. The name is complete in itself: no two nodes share one.</p>
<p>Under the label, each box says whether the node is a panorama or a fixed view.</p>
<p><a class="img-link" href="https://glthr.com/images/revelation-graph-1/revelation-node-label.w.png" title="Open full size (2400×840)"><img class="has-dark" src="https://glthr.com/images/revelation-graph-1/revelation-node-label.w-1800w.png" alt="The box w5 z01 n020, panorama, in the yellow of Tomahna by day, annotated: world 5, zone 1, node 20, and panorama or fixed view. Beside it, the panorama of the node, a wooden walkway between rocks leading to a round metal doorway, with an open eye." width="1800" height="630" data-full="/images/revelation-graph-1/revelation-node-label.w.png" data-full-width="2400" loading="lazy" decoding="async"></a></p>
<p><em>The label of <a href="https://glthr.com/revelation-graph#w5_z01_n020" data-stack="revelation-w5">w5_z01_n020</a> and its view. The open eye identifies a view that the game displays, following the <a href="https://glthr.com/revelation-graph-2#heading-visual-indicators">figure convention</a> of the findings.</em></p>
<h4 id="heading-panoramas-fixed-views-and-layers">Panoramas, Fixed Views and Layers<a class="anchor" href="#heading-panoramas-fixed-views-and-layers" aria-hidden="true" tabindex="-1">#</a></h4>
<p>A <strong>panorama</strong> stores six faces. A <strong>fixed view</strong> stores one, and the game shows it flat. Most fixed views are entered from a panorama and go back to it.</p>
<p>What a node shows is not one picture. Besides its default cube, a node can hold masks that are drawn over it, and panels on which movies play: a door that opens, a lever that moves, a character who speaks. This study displays the default cube only. Thirty nodes have no cube at all, and <a href="https://glthr.com/revelation-graph-2#heading-thirty-nodes-without-a-picture">the second article</a> says what they are.</p>
<h4 id="heading-sources-sinks-and-isolated-nodes">Sources, Sinks and Isolated Nodes<a class="anchor" href="#heading-sources-sinks-and-isolated-nodes" aria-hidden="true" tabindex="-1">#</a></h4>
<p>The usual graph terms apply. A <strong>source</strong> has no incoming connection from another node; a <strong>sink</strong> has no outgoing connection to another node; an <strong>isolated</strong> node has neither.</p>
<p>These properties describe a graph projection, without establishing access in the game. Some nodes are entered by compiled code whose origin I could not establish. They appear as isolated nodes, and the browser says so in their record.</p>
<h4 id="heading-virtual-targets">Virtual Targets<a class="anchor" href="#heading-virtual-targets" aria-hidden="true" tabindex="-1">#</a></h4>
<p>Thirteen connections lead to eleven nodes that this release does not store, such as <a href="https://glthr.com/revelation-graph#w3_z02_n080" data-stack="revelation-w3">w3_z02_n080</a>. I keep each target as a virtual node, with a distinct border, rather than discard the reference. The second article <a href="https://glthr.com/revelation-graph-2#heading-eleven-nodes-that-are-not-there">comes back to them</a>.</p>
<p><a class="img-link" href="https://glthr.com/images/revelation-graph-1/revelation-node-types.w.png" title="Open full size (2400×705)"><img class="has-dark" src="https://glthr.com/images/revelation-graph-1/revelation-node-types.w-1800w.png" alt="Boxes of the graph and what their colors mean: one box per Age in its pastel color, Tomahna by day, Tomahna by night, Haven, Spire, Serenia and the menu; then a green source, a salmon sink, a yellow isolated node, and the dashed box of an absent target." width="1800" height="529" data-full="/images/revelation-graph-1/revelation-node-types.w.png" data-full-width="2400" loading="lazy" decoding="async"></a></p>
<h3 id="heading-reading-a-connection">Reading a Connection<a class="anchor" href="#heading-reading-a-connection" aria-hidden="true" tabindex="-1">#</a></h3>
<p>An arrow has a source and a destination. If both directions exist, the nodes are mutually connected. If only one exists, following it does not imply that the player can simply reverse the move.</p>
<p>As in Exile, the way back is usually behind the player: <strong>95.1% of the 1,336 pairs of nodes have their reverse pair</strong>, against 90.4% for Exile, 66.4% for Riven and 55.5% for Myst. The 66 one-way pairs are rides, falls, links and the passage from day to night.</p>
<p>There are several kinds of connection:</p>
<div class="table-wrap">
<table>
  <thead>
      <tr>
          <th>Kind</th>
          <th style="text-align: right">Typed connections</th>
          <th>Meaning</th>
      </tr>
  </thead>
  <tbody>
      <tr>
          <td>Move</td>
          <td style="text-align: right">1,031</td>
          <td>A command started by a hotspot changes node, or a transition plays a movie and arrives elsewhere.</td>
      </tr>
      <tr>
          <td>Return</td>
          <td style="text-align: right">209</td>
          <td>A fixed view goes back to a node.</td>
      </tr>
      <tr>
          <td>Engine</td>
          <td style="text-align: right">95</td>
          <td>The destination is stored as data, and a compiled class makes the move.</td>
      </tr>
      <tr>
          <td>Amulet</td>
          <td style="text-align: right">9</td>
          <td>The vision that the amulet opens on an object.</td>
      </tr>
      <tr>
          <td>Automatic</td>
          <td style="text-align: right">2</td>
          <td>A command that no click starts changes node.</td>
      </tr>
      <tr>
          <td>Unreferenced command</td>
          <td style="text-align: right">9</td>
          <td>A command changes node, and nothing stored starts it.</td>
      </tr>
      <tr>
          <td><strong>Total</strong></td>
          <td style="text-align: right"><strong>1,355</strong></td>
          <td>All exported kinds together.</td>
      </tr>
  </tbody>
</table>
</div>
<p>Path calculations leave out the 9 unreferenced commands and 10 of the returns, for a reason given <a href="#heading-returns-that-belong-to-the-caller">below</a>. They retain 1,336 unique ordered pairs of nodes.</p>
<p><a class="img-link" href="https://glthr.com/images/revelation-graph-1/revelation-edge-types.w.png" title="Open full size (2400×1290)"><img class="has-dark" src="https://glthr.com/images/revelation-graph-1/revelation-edge-types.w-1800w.png" alt="Seven sample arrows between pairs of boxes, each with its meaning: a plain arrow for a move, a thick line in the color of the Age it leaves for a link between two Ages, a dashed green arrow for a conditional move, a gray arrow for the return of a fixed view, a dashed purple arrow for a move made by a compiled class, a dashed gold arrow for a vision of the amulet, and a hollow arrowhead for a command that nothing stored starts." width="1800" height="968" data-full="/images/revelation-graph-1/revelation-edge-types.w.png" data-full-width="2400" loading="lazy" decoding="async"></a></p>
<p><em>From top to bottom: <a href="https://glthr.com/revelation-graph#w5_z01_n020" data-stack="revelation-w5">w5_z01_n020</a> → <a href="https://glthr.com/revelation-graph#w5_z02_n010" data-stack="revelation-w5">w5_z02_n010</a>, <a href="https://glthr.com/revelation-graph#w1_z06_n010" data-stack="revelation-w1">w1_z06_n010</a> → <a href="https://glthr.com/revelation-graph#w2_z02_n010" data-stack="revelation-w2">w2_z02_n010</a>, <a href="https://glthr.com/revelation-graph#w1_z06_n040" data-stack="revelation-w1">w1_z06_n040</a> → <a href="https://glthr.com/revelation-graph#w1_z06_n030" data-stack="revelation-w1">w1_z06_n030</a>, <a href="https://glthr.com/revelation-graph#w1_z01_n021" data-stack="revelation-w1">w1_z01_n021</a> → <a href="https://glthr.com/revelation-graph#w1_z01_n020" data-stack="revelation-w1">w1_z01_n020</a>, <a href="https://glthr.com/revelation-graph#w3_z01_n200" data-stack="revelation-w3">w3_z01_n200</a> → <a href="https://glthr.com/revelation-graph#w3_z02_n010" data-stack="revelation-w3">w3_z02_n010</a>, <a href="https://glthr.com/revelation-graph#w1_z03_n093" data-stack="revelation-w1">w1_z03_n093</a> → <a href="https://glthr.com/revelation-graph#w1_z03_n094" data-stack="revelation-w1">w1_z03_n094</a>, and <a href="https://glthr.com/revelation-graph#w4_z06_n020" data-stack="revelation-w4">w4_z06_n020</a> → <a href="https://glthr.com/revelation-graph#w4_z06_n010" data-stack="revelation-w4">w4_z06_n010</a>.</em></p>
<p>Several pieces of evidence can support the same edge. I merge references only when their source, destination and kind agree, while keeping every contributing instruction in its evidence.</p>
<h4 id="heading-commands-are-sentences">Commands Are Sentences<a class="anchor" href="#heading-commands-are-sentences" aria-hidden="true" tabindex="-1">#</a></h4>
<p>The instructions of Revelation are not numbered operations. They are lines of text, grouped in named blocks, and the line that moves the player reads <code>ContextChange(1,01,021)</code>: world 1, zone 1, node 21. The game stores 28,980 such lines in 6,913 blocks. Of them, 1,029 change node.</p>
<p>A block does nothing by itself. Something has to start it, and the node says what: a small parameter file ties a hotspot to three blocks, one for the pointer entering it, one for the pointer leaving it and one for a click. A move of the graph is a <code>ContextChange</code> in a block that a click starts.</p>
<h4 id="heading-conditions-are-rare">Conditions Are Rare<a class="anchor" href="#heading-conditions-are-rare" aria-hidden="true" tabindex="-1">#</a></h4>
<p>A block can test a variable and jump. The extractor keeps these tests beside the connection and never evaluates them. Only <strong>28 connections are conditional</strong>, against <a href="https://glthr.com/exile-graph-1#heading-local-conditions-remain-visible">316 in Exile</a>. This does not mean that Revelation has fewer locked doors. It means that the locks are elsewhere: in the compiled classes. Ten of the 28 are tests read in their code; among them, <a href="https://glthr.com/revelation-graph-2#heading-one-passage-into-the-night">the passage from day to night</a> waits for two variables of a puzzle.</p>
<h4 id="heading-what-the-compiled-classes-do">What the Compiled Classes Do<a class="anchor" href="#heading-what-the-compiled-classes-do" aria-hidden="true" tabindex="-1">#</a></h4>
<p>Each node lists the <strong>classes</strong> that run in it, with their parameters. A class is compiled code, shipped in the libraries of the game. Most are general: a hotspot that plays a sound, a movie that loops. Others belong to one node, such as <code>w1_z01_n020</code>, the class of a door with an iris and a lever.</p>
<p>A class does what the commands cannot: wait for a lever to be pulled all the way, play a ride, open a linking book. When it moves the player, the destination is usually still data, and I found it in five forms:</p>
<ul>
<li>a hotspot named for its destination, such as <code>h_to_w4_z01_n010</code>, that no command serves;</li>
<li>three parameters that give a world, a zone and a node, such as the <code>m_world_to_go</code>, <code>m_zone_to_go</code> and <code>m_node_to_go</code> of an elevator of Spire;</li>
<li>a transition movie of the node named for its destination, such as <code>w1_z06_n050.p_tr_w1_z09_n030_default_transit</code>;</li>
<li>the name of such a hotspot written as a constant in a library;</li>
<li>on the side of the destination, the direction to face when arriving from a named node.</li>
</ul>
<p>These are the <strong>engine</strong> connections: 95 in all. The links between the Ages are among them. In the room of Tomahna that holds the linking books, <a href="https://glthr.com/revelation-graph#w1_z06_n010" data-stack="revelation-w1">w1_z06_n010</a>, the hotspots to Haven and to Spire are parameters of the class of the room.</p>
<p>A few destinations are written in the compiled code itself, as three constants pushed before the call that changes node. The libraries hold 62 of them. Some stand apart from their call, behind other instructions, and I read those by hand. To give a destination to a node, I follow its routine back to the class that owns it, through the method that calls the routine or hands it over, and to the node that lists the class. That names the node of 51 of the 62. The 11 others are recorded on their destination, without an arrow, since nothing says where they start. The passage from day to night is one of the constants set apart from their call: it belongs to the class <code>w5_z01_n110</code>, which bears the name of its node.</p>
<h4 id="heading-returns-that-belong-to-the-caller">Returns That Belong to the Caller<a class="anchor" href="#heading-returns-that-belong-to-the-caller" aria-hidden="true" tabindex="-1">#</a></h4>
<p>A fixed view goes back where the player came from. For 140 of them, the view records the node to go back to. For 59 others it records nothing, and the engine remembers the last node: I infer those returns from the nodes that enter the view, and mark them as inferred.</p>
<p>Five fixed views are entered from two nodes. They are close-ups stored once, in Tomahna by night, and used by day as well: the names of what opens them, in French, speak of a drawer (<em>tiroir</em>), a porthole (<em>hublot</em>) and a door (<em>porte</em>). Each has two inferred returns, one to the day and one to the night, and each return belongs to the node the player came from. Entering such a view by day and leaving it into the night would be a shortcut that the game does not have. The graph keeps these 10 returns, draws them with a hollow arrowhead and leaves them out of path search, as <a href="https://glthr.com/riven-graph-1#heading-hollow-arrows-for-a-continuing-handler">the Riven Graph does for its caller-owned continuations</a>.</p>
<h4 id="heading-commands-that-nothing-starts">Commands That Nothing Starts<a class="anchor" href="#heading-commands-that-nothing-starts" aria-hidden="true" tabindex="-1">#</a></h4>
<p>Nine blocks change node and are started by nothing that the data stores: no hotspot, no parameter of a class, no other block. Some are probably started by compiled code that builds their name. The graph draws them with a hollow arrowhead and path search ignores them.</p>
<h2 id="heading-archives-inside-archives">Archives Inside Archives<a class="anchor" href="#heading-archives-inside-archives" aria-hidden="true" tabindex="-1">#</a></h2>
<p>The format had been described by players of the game who wanted to look at its pictures (<a href="https://github.com/coderjo/myst4tools/blob/master/m4b-format.md" target="_blank" rel="noopener">myst4tools</a>, <a href="https://tomahnaproject.github.io/tomahna-project-wiki/myst4/file-reference/bigfile" target="_blank" rel="noopener">the Tomahna project</a>): an archive is a tree of names, sizes and offsets, followed by the files, uncompressed. Archives nest. The main one holds 618 node archives, and a node archive holds one archive per picture layer.</p>
<p>The names in the binary files are lightly scrambled: in every byte, each pair of neighboring bits is exchanged. Applying the same exchange again gives the text back. Comparing a scrambled name with the name it had to be revealed the rule.</p>
<h2 id="heading-no-engine-to-lean-on">No Engine to Lean On<a class="anchor" href="#heading-no-engine-to-lean-on" aria-hidden="true" tabindex="-1">#</a></h2>
<p>For Myst, Riven and Exile, an open-source program that plays the game says what each instruction means and what the engine does on its own. Revelation has no such program. Two things made up for it.</p>
<p>The first is that the game explains itself. Commands are sentences, parameters have names, and the names were chosen by people who had to find their way in them: a hotspot that leads to a node is called <code>h_to_</code> followed by the name of that node.</p>
<p>The second is that the libraries can be read without being run. They import one function to change node. Where the three numbers of the destination are constants pushed just before the call, I read them in the disassembly. Where they are loaded from an object, they come from the parameters, which the node archives already hold.</p>
<h2 id="heading-what-is-inferred">What Is Inferred<a class="anchor" href="#heading-what-is-inferred" aria-hidden="true" tabindex="-1">#</a></h2>
<p>Every connection keeps its evidence, and 63 of the 1,355 are inferred rather than read:</p>
<ul>
<li>59 returns of fixed views that record no node to go back to;</li>
<li>3 entries into fixed views that record their node and that nothing stored opens;</li>
<li>1 connection set by hand, from the first node of a new game. <a href="https://glthr.com/revelation-graph#w5_z01_n010" data-stack="revelation-w5">w5_z01_n010</a> is a scene, not a place to walk in, and it stores no exit. Its library holds one compiled transition to another node, <a href="https://glthr.com/revelation-graph#w5_z01_n020" data-stack="revelation-w5">w5_z01_n020</a>, and I attribute it to the first node.</li>
</ul>
<p>The browser marks each of them, and their tooltips say so in the drawing.</p>
<h2 id="heading-was-everything-read">Was Everything Read?<a class="anchor" href="#heading-was-everything-read" aria-hidden="true" tabindex="-1">#</a></h2>
<p>The node archives are listed by the main archive, so none can be missed: 618 archives, 618 nodes. Their small files were all decoded without an error. What can be missed is a move, in three cases: a destination computed in compiled code from something other than a parameter, a compiled constant that I could not attribute, and a compiled constant that the reading does not recognize. The third happened: a first reading missed eight of the 62 constants, the passage from day to night among them. <a href="https://glthr.com/revelation-graph#w1_z01_n310" data-stack="revelation-w1">w1_z01_n310</a>, where the night begins, stood in the graph as a complete node without an entrance, until a wider reading of the libraries found its entrance, three constants of the library of the day set apart from their call, and with it the way to five fixed views of Haven and to two nodes of the Dream.</p>
<p>The word “decompile” needs a precise scope here. The project decodes the game’s archives, commands and parameters into readable structures, and reads constants in the compiled libraries. It does not recover the engine’s source code or fully model how its classes use those parameters.</p>
<h2 id="heading-conclusion">Conclusion<a class="anchor" href="#heading-conclusion" aria-hidden="true" tabindex="-1">#</a></h2>
<p>Revelation keeps the world of places that Exile introduced and stores it differently: one archive per node, sentences for commands, and compiled classes for everything that is not a simple click. The graph that comes out of it is smaller than the earlier ones and nearly symmetric.</p>
<p>It is also the first of the series that has a shape. In <a href="https://glthr.com/revelation-graph-2">the next article</a>, I use that shape: to follow paths, to measure what stands close and is far apart, and to look at what the discs name and do not hold.</p>
]]></content:encoded></item><item><title>Visions the Amulet Never Showed: Myst IV: Revelation (2004)</title><link>https://glthr.com/revelation-visions-the-amulet-never-showed</link><guid isPermaLink="true">https://glthr.com/revelation-visions-the-amulet-never-showed</guid><pubDate>Sat, 21 Nov 2026 00:00:06 +0000</pubDate><dc:creator>Guillaume Lethuillier</dc:creator><description>One line of a settings file starts Myst IV: Revelation anywhere, even on a vision it never plays, and a console its makers switched off prints puzzle values.</description><content:encoded><![CDATA[<aside class="callout callout-note">
  <span class="callout-emoji" aria-hidden="true">✎</span>
  <div class="callout-body"><p class="callout-title">Work in progress — November 21, 2026</p>
    <p>I am still working in <strong>Myst IV: Revelation</strong>. I will update these articles over the coming weeks, so please feel free to come back later to see what’s new.</p>
  </div>
</aside><aside class="callout callout-abstract">
  <span class="callout-emoji" aria-hidden="true">↘</span>
  <div class="callout-body">
    <p>One line in a settings file changes where Myst IV: Revelation (2004) begins, letting the player start inside an unused vision of the amulet in Spire. The game also keeps a disabled console that displays debug information and prints values for a puzzle.</p>
<p>Each section explains how to try the finding in the game. This article contains spoilers.</p>
  </div>
</aside><p>The <a href="https://glthr.com/page/revelation-graph">Revelation Graph</a> 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. <span class="inline-update sidenote" role="note"><em><span class="inline-update-bracket">[</span>Node labels such as <a href="https://glthr.com/revelation-graph#w5_z04_n111" data-stack="revelation-w5">w5_z04_n111</a> have a thick underline, in the color of their Age, and open that place in the graph browser of the game.<span class="inline-update-bracket">]</span></em></span></p>
<p>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. <span class="inline-update sidenote" role="note"><em><span class="inline-update-bracket">[</span>Version of the game: Myst IV: Revelation, version 1.03 for Windows.<span class="inline-update-bracket">]</span></em></span></p>
<h2 id="heading-one-line-to-start-anywhere">One Line to Start Anywhere<a class="anchor" href="#heading-one-line-to-start-anywhere" aria-hidden="true" tabindex="-1">#</a></h2>
<p><strong>How to reach it.</strong></p>
<ol>
<li>
<p>Quit the game. In the folder where the game is installed, open the folder <code>data</code>, which holds <code>data.m4b</code>.</p>
</li>
<li>
<p>Create there a text file named <code>data.dsc</code> with these lines, the settings packed in <code>data.m4b</code> with their first line changed, putting the name of a stored node of the <a href="https://glthr.com/page/revelation-graph">Revelation Graph</a> in place of <code>w5_z04_n111</code>:</p>
<pre tabindex="0"><code>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)
}
</code></pre></li>
<li>
<p>Start the game: it opens in that node, with no logo, no film and no menu.</p>
</li>
<li>
<p>To get the ordinary start back, delete the file.</p>
</li>
</ol>
<p>The engine reads its settings from text files.<sup id="fnref:1"><a href="#fn:1" class="footnote-ref" role="doc-noteref">1</a></sup> One of them, <code>data.dsc</code>, begins with the line <code>set_initial_context(w6_z01_n021)</code>, and that name is a node of the graph (<a href="https://glthr.com/revelation-graph#w6_z01_n021" data-stack="revelation-w6">w6_z01_n021</a>): 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 <code>data.m4b</code>, 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.</p>
<p>With <code>set_initial_context(w5_z04_n111)</code>, six seconds after its window appears, the game stands in front of a box of the laboratory of Tomahna, by day (<a href="https://glthr.com/revelation-graph#w5_z04_n111" data-stack="revelation-w5">w5_z04_n111</a>), with its hand, its interface and its sound. No logo, no film and no menu come first.</p>
<p><img src="https://glthr.com/images/revelation-visions-the-amulet-never-showed/revelation-start-box.png" alt="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." width="1600" height="900" data-full="/images/revelation-visions-the-amulet-never-showed/revelation-start-box.png" data-full-width="1600" loading="lazy" decoding="async"></p>
<p><em>The first picture of the game, with one line changed.</em></p>
<p><a href="https://media.glthr.com/revelation-behind-the-ages/revelation-start-node.mp4" target="_blank" rel="noopener"><img src="https://glthr.com/images/revelation-visions-the-amulet-never-showed/revelation-start-node-poster.jpg" alt="Myst IV Revelation started with one line changed in a settings file: its window opens straight on a close view in the laboratory of Tomahna, with no logo, no film and no menu."></a></p><p>[Video: Myst IV Revelation started with one line changed in a settings file: its window opens straight on a close view in the laboratory of Tomahna, with no logo, no film and no menu.]</p>
<p>The engine reads <code>game.dsc</code> first, then a loose <code>data.dsc</code> if one exists, then <code>user.dsc</code>, and finally the packed <code>data.dsc</code> only if no loose copy was found. Because a setting read twice keeps its last value, the start line does nothing in <code>game.dsc</code> or <code>user.dsc</code> in an unmodified install, where the packed <code>data.dsc</code> runs last and overwrites it. Once a loose <code>data.dsc</code> is in place, the packed one is skipped and <code>user.dsc</code> runs last: a file <code>bin\user.dsc</code> holding the start line alone then decides where the game opens, whatever <code>data.dsc</code> says. Any stored node can serve as the starting point. The graph’s virtual targets have no node archive to load.</p>
<p>Among them is a place that the game never shows. <a href="https://glthr.com/revelation-graph#w3_z01_n032" data-stack="revelation-w3">w3_z01_n032</a> is a vision of the amulet in Spire that no place names: in the cell where it belongs, <a href="https://glthr.com/revelation-graph#w3_z01_n031" data-stack="revelation-w3">w3_z01_n031</a>, the amulet plays a film instead.<sup id="fnref:2"><a href="#fn:2" class="footnote-ref" role="doc-noteref">2</a></sup> 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.</p>
<p><img src="https://glthr.com/images/revelation-visions-the-amulet-never-showed/revelation-vision.png" alt="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." width="1600" height="900" data-full="/images/revelation-visions-the-amulet-never-showed/revelation-vision.png" data-full-width="1600" loading="lazy" decoding="async"></p>
<p><em><a href="https://glthr.com/revelation-graph#w3_z01_n032" data-stack="revelation-w3">w3_z01_n032</a>, opened by the start line.</em></p>
<p><a href="https://media.glthr.com/revelation-behind-the-ages/revelation-vision.mp4" target="_blank" rel="noopener"><img src="https://glthr.com/images/revelation-visions-the-amulet-never-showed/revelation-vision-poster.jpg" alt="Myst IV Revelation started on a vision of the amulet that no place names: the cell of Spire, clean and lit behind its bars in a mist, then a white flash, and the same cell, dark and ruined."></a></p><p>[Video: Myst IV Revelation started on a vision of the amulet that no place names: the cell of Spire, clean and lit behind its bars in a mist, then a white flash, and the same cell, dark and ruined.]</p>
<h2 id="heading-a-console-switched-off-by-one-instruction">A Console Switched Off by One Instruction<a class="anchor" href="#heading-a-console-switched-off-by-one-instruction" aria-hidden="true" tabindex="-1">#</a></h2>
<p><strong>How to reach it.</strong></p>
<ol>
<li>Copy the folder of the game (version 1.03) and work in the copy.</li>
<li>In <code>bin\m4_thor_rd.dll</code>, find the twelve bytes <code>5F 88 9E AD 00 00 00 8B C6 5E 5D 5B</code>, which occur once (at offset <code>0x1FCDC</code>), and replace the six that follow <code>5F</code> with <code>90 90 90 90 90 90</code>.</li>
<li>Start the game from the copy and press the key left of 1 (<code>`</code> on a US keyboard, <code>²</code> on a French one). The same key closes the console.</li>
</ol>
<p>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.</p>
<p><img src="https://glthr.com/images/revelation-visions-the-amulet-never-showed/revelation-console.png" alt="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." width="1600" height="644" data-full="/images/revelation-visions-the-amulet-never-showed/revelation-console.png" data-full-width="1600" loading="lazy" decoding="async"></p>
<p><em>The console over the round door of Serenia: its header, then six lines printed by the key M.</em></p>
<p>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 <code>m4_ai_debug</code> that it does not have.</p>
<p>One library still writes to it. In front of that round door, the close view of a puzzle (<a href="https://glthr.com/revelation-graph#w4_z06_n061" data-stack="revelation-w4">w4_z06_n061</a>), 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.</p>
<p><a href="https://media.glthr.com/revelation-behind-the-ages/revelation-console.mp4" target="_blank" rel="noopener"><img src="https://glthr.com/images/revelation-visions-the-amulet-never-showed/revelation-console-poster.jpg" alt="Myst IV Revelation with its console switched on, in front of a round door of Serenia: the key left of 1 opens a header that names the node, and after the key M the console shows six lines of generated puzzle values."></a></p><p>[Video: Myst IV Revelation with its console switched on, in front of a round door of Serenia: the key left of 1 opens a header that names the node, and after the key M the console shows six lines of generated puzzle values.]</p>
<h2 id="heading-conclusion">Conclusion<a class="anchor" href="#heading-conclusion" aria-hidden="true" tabindex="-1">#</a></h2>
<p>Unlike <a href="https://glthr.com/exile-linking-without-a-book">Exile’s typed developer code</a>, Revelation leaves no in-game cheat code to type, yet its configuration files and compiled libraries remain surprisingly open, much like <a href="https://glthr.com/end-of-ages-commands-beyond-the-slate">Myst V’s encrypted settings files</a> 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.</p>
<div class="footnotes" role="doc-endnotes">
<hr>
<ol>
<li id="fn:1">
<p>The settings files themselves are known: a <code>game.dsc</code> of one line to play in a window has been passed around since 2011 at least, and <a href="https://www.pcgamingwiki.com/wiki/Myst_IV:_Revelation" target="_blank" rel="noopener">PCGamingWiki</a> gives it; the fan tool <a href="https://github.com/tomysshadow/M4Revolution" target="_blank" rel="noopener">M4Revolution</a> writes a <code>user.dsc</code>, and the notes of <a href="https://github.com/rsheasby/m4fix" target="_blank" rel="noopener">m4fix</a> name <code>data.dsc</code>. The Revelation Editor of realXCV has opened the nodes of the game in its own viewer since 2009.&#160;<a href="#fnref:1" class="footnote-backref" role="doc-backlink">&#x21a9;&#xfe0e;</a></p>
</li>
<li id="fn:2">
<p>The <a href="https://glthr.com/revelation-graph-2#heading-three-others">second Revelation Graph article</a> found it in the data: the vision names the cell as the place to go back to, and the cell does not name it.&#160;<a href="#fnref:2" class="footnote-backref" role="doc-backlink">&#x21a9;&#xfe0e;</a></p>
</li>
</ol>
</div>
]]></content:encoded></item></channel></rss>