<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>HOLD: Last Dawn — Signal Log (EN)</title>
    <link>https://playholdgame.com/en/devlog/</link>
    <atom:link href="https://playholdgame.com/en/devlog/feed.xml" rel="self" type="application/rss+xml" />
    <description>The development log of HOLD: Last Dawn. One entry per work day, by Black Signal.</description>
    <language>en</language>
    <generator>Astro</generator>
    <item>
      <title>DAY 90 — Five Seconds to the Door</title>
      <link>https://playholdgame.com/en/devlog/c4-kontor/</link>
      <guid isPermaLink="true">https://playholdgame.com/en/devlog/c4-kontor/</guid>
      <pubDate>Sun, 20 Sep 2026 00:00:00 GMT</pubDate>
      <description>Today a door came off its hinges for the first time. Also: KONTOR, a robot trader who hasn't seen a customer in a long while, and the decision to make your own explosives harmless.</description>
      <content:encoded><![CDATA[<p>Today a door came off its hinges for the first time.</p>
<p>That sounds like a small thing, but there is more hanging on a door than you would think. It has to look like it really sits in the wall. It has to tell you that it is shut and why. It has to offer a way to open it, and that way has to have been earned somewhere else first. And when it opens, it must not feel like flipping a switch.</p>
<figure>
  <video class="devlog-clip" autoplay loop muted playsinline
         poster="/devlog/c4-kontor.png" width="1280" height="720">
    <source src="/img/c4-kontor.webm" type="video/webm" />
    <source src="/img/c4-kontor.mp4" type="video/mp4" />
  </video>
  <figcaption>Walk up, place, five seconds, door. The countdown runs slightly faster in the clip than in the game. (Loop)</figcaption>
</figure><h2>Five seconds</h2>
<p>The sequence is deliberately short. You walk up to the door and a charge point appears across the leaf, outlined with a running dashed border. The C4 has to be in your pack and assigned to one of the two quick slots, and then one press sticks the charge on.</p>
<p>From there the detonator counts. No floating text above the door, but a small display on the charge itself going from 05 down to 01, with a red diode next to it. Diode and beep speed up on the same beat. That mattered to me: what the player needs to know should live inside the game, not beside it.</p>
<p>At zero the hand wheel bursts first, and then the fireball comes. The first version had it the other way around, and it looked wrong. The fireball covers the door completely for half a second, so the door visibly only started opening after the explosion. Now the animation starts 0.22 seconds before the blast. Sounds like nothing. Makes all the difference.</p>
<p><img src="/img/c4-kontor-tuerzustaende.png" alt="Eight states of the same door side by side"></p>
<h2>The decision that kills nobody</h2>
<p>The question I sat on longest: does the player take damage standing next to it?</p>
<p>The answer is no, for a reason that goes beyond convenience. The explosive is his. He found it, put it on a slot and placed it himself, with five seconds of warning, a display and a beep. Standing still after that is not a mistake, it is watching. Tearing him apart for it would punish the solution, not an error. And the second time around he would run off on reflex without looking. The very explosion I spent an evening layering, he would never see again.</p>
<p>So proximity only costs a harder shake. Whatever else is standing in front of the door very much feels it, though, at more than double a grenade&#39;s damage. Time it right and you get two things done at once.</p>
<p>And the blast is not without consequence: it raises brood pressure. Underground, that kind of noise travels.</p>
<h2>The shop that went a long time without a customer</h2>
<p>C4 does not fall from the sky. You find the blueprint, and after that somebody sells it to you. That somebody is called KONTOR.</p>
<p><img src="/img/c4-kontor-shop.png" alt="KONTOR under his lamp, surrounded by shelves of spare parts and powered-down robot heads"></p>
<p>The Robo-Shop is not a menu with a portrait next to it, it is a room you walk into. KONTOR stands behind his counter and waits. When nobody comes for a while he runs maintenance on himself or drops into standby. When somebody walks in, he perks up and his visor brightens.</p>
<p>You have to talk to him yourself. He does not start on his own, and he does not repeat himself while he still has something unsaid.</p>
<p><img src="/img/c4-kontor-spruch.png" alt="KONTOR speaking: Light does not make the corridor shorter. It only makes it bearable."></p>
<blockquote>
<p>Light does not make the corridor shorter. It only makes it bearable.</p>
</blockquote>
<p>Trading happens at the terminal in the shop, which opens the same tab you can reach from the base. One interface, two ways in.</p>
<p><img src="/img/c4-kontor-dawn.png" alt="The trading tab in DAWN with buying and selling"></p>
<p>His stock is limited and refills overnight. When selling, the list merges pack and depot and sells from the depot first, so you do not accidentally part with what you are carrying. And the C4 only shows up on his shelf once you have found the blueprint. Before that, KONTOR does not know the thing exists.</p>
<h2>What you do not see</h2>
<p>The invisible part of the day was the door itself. A frame simply painted onto a wall sticks to it like a sticker. To make it sit inside, it gets a tight dark shadow gap around its silhouette, and behind the opening there is no wall but a real recess with a shaded lintel and darkened reveals.</p>
<p>The nice part: the clear opening is measured, not entered. The engine looks for the transparent pixels that cannot be reached from the image border, and works out where the hole in the frame is by itself. A new door variant needs no new number at all.</p>
<p>That will matter. From the first level underground on, almost every room gets a door like this. The state of each one now lives in the save file.</p>
<p>And somewhere down there the reactor core factory is waiting. As of today, it sits behind a steel door.</p>
<p><em>— Black Signal</em></p>
]]></content:encoded>
      <enclosure url="https://playholdgame.com/devlog/c4-kontor.png" type="image/png" length="0" />
      <category>c4</category>
      <category>robo-shop</category>
      <category>setpiece</category>
      <category>items</category>
    </item>
    <item>
      <title>DAY 84 — Building rooms instead of typing them</title>
      <link>https://playholdgame.com/en/devlog/level-editor/</link>
      <guid isPermaLink="true">https://playholdgame.com/en/devlog/level-editor/</guid>
      <pubDate>Mon, 14 Sep 2026 00:00:00 GMT</pubDate>
      <description>HOLD is meant to ship with more than 50 explorable rooms. Hand-typed, they would never have been finished. Today the editor that builds them is done, and the first room was built with it.</description>
      <content:encoded><![CDATA[<p><strong>HOLD</strong> is meant to ship with more than 50 explorable rooms. Bunkers, depots, factory halls, boss chambers. Until now each one was written as code: work out the coordinates, wire them in, launch, look, work them out again. That is fine for one reference room. It does not work for fifty.</p>
<h2>The bottleneck</h2>
<p>A room is really just a stack of images with a line the character stands on. The engine was never the problem, getting there was. Moving one tile twelve pixels meant changing a number, rebuilding, reloading. With three backdrops and a handful of props that is thirty round trips for a single room. The rooms were not hard to build, they were unbearably slow to build.</p>
<h2>The decisions</h2>
<p>So: tool first, rooms after. Three things had to be locked down before an editor made any sense.</p>
<p><strong>A grid.</strong> Every tile is 688 by 384 pixels, every room a multiple of that in width. It sounds arbitrary, but it is the size the pixel art comes out of cleanly and fits the viewport without scaling. Nothing gets blurred, ever.</p>
<p><strong>One walk line.</strong> Rooms in HOLD are flat side views, not angled ones. There is exactly one height you walk on, and the editor draws it as a yellow line across the scene. The magnet pulls an object there by its footline, not by its centre. That sounds like a detail, but it decides whether a crate stands on the floor or sinks into it.</p>
<p><strong>Six layers.</strong> Two behind the stage for parallax and depth, the stage itself where you walk, and three in front that darken progressively and occlude the character. They are now named the way you see them, not the way they are called internally.</p>
<p>On top of that, a camera you can orbit around the scene. The layers stay exactly where they are, only the viewpoint tilts, and you can see at a glance what sits behind what.</p>
<h2>The first room</h2>
<p>What got built with it is the looted explosives depot: a security airlock, stripped weapon racks, a heap of pried-open containers. Three tiles, placed in minutes instead of calculated over an evening. Save in the editor, reload the game, walk in.</p>
<p>Still missing: the vents the brood comes out of once you pick up the charge, and the way back, which by then is not a way back. But the bottleneck is gone. The next fifty rooms are a question of images and taste now, not of coordinates.</p>
<p><em>— Black Signal</em></p>
]]></content:encoded>
      <enclosure url="https://playholdgame.com/devlog/level-editor-1.png" type="image/png" length="0" />
      <category>tools</category>
      <category>rooms</category>
      <category>editor</category>
    </item>
    <item>
      <title>DAY 67 — Scaling the Command Console</title>
      <link>https://playholdgame.com/en/devlog/console-scaling/</link>
      <guid isPermaLink="true">https://playholdgame.com/en/devlog/console-scaling/</guid>
      <pubDate>Fri, 28 Aug 2026 00:00:00 GMT</pubDate>
      <description>A polish pass on D.A.W.N., the command console: it now scales cleanly to any screen, from a laptop to an ultrawide, and the War-Rig loadout got a tidy-up.</description>
      <content:encoded><![CDATA[<p>Between the siege nights in <strong>HOLD</strong>, you spend your time in <strong>D.A.W.N.</strong> — the command console where you spec your commander, wire up perks, and kit out the War-Rig. It&#39;s a big part of the game, so it has to feel like a real machine on <em>any</em> screen. Today was about making that true.</p>
<h2>The problem</h2>
<p>On large and ultrawide monitors the console rendered its text at a fixed pixel size. The bigger your screen, the tinier and lonelier everything looked, with a dead zone stranded in the middle — not great for something you are meant to live in.</p>
<h2>The fix</h2>
<p>The whole console is now built at a fixed reference and scaled to fit your display as one piece, the way games handle their HUDs. Text, panels and frames grow together, stay razor-sharp, and read the same whether you are on a 13-inch laptop or a 34-inch ultrawide. Along the way a wild pile of font sizes collapsed into one consistent scale.</p>
<p>While we were in there: the <strong>Splitter matrix</strong> — your perk grid — now spans the full width instead of huddling in the middle; an ugly scrollbar that had crept into the <strong>Bestiary</strong> is gone; and the <strong>War-Rig loadout</strong> got reworked. The live rig preview now sits at a fixed size under the buy panel — no more jumping around as you click between weapons — the wall-of-text weapon descriptions are gone (the stat sheets say it better), and we banished a &quot;SPLASH-RADIUS: undefined&quot; gremlin haunting the Cryo-Lance. Turns out a freeze weapon has no splash; it shows Frost buildup instead.</p>
<p>None of this is flashy on its own. But this is the stuff that turns a menu into an interface — and an interface into a machine you trust. Back to the arsenal next.</p>
<p><em>— Black Signal</em></p>
]]></content:encoded>
      <enclosure url="https://playholdgame.com/devlog/console-scaling.png" type="image/png" length="0" />
      <category>dawn</category>
      <category>ui</category>
      <category>war-rig</category>
    </item>
    <item>
      <title>DAY 63 — Night Siege: waves that learn to read</title>
      <link>https://playholdgame.com/en/devlog/night-siege-pacing/</link>
      <guid isPermaLink="true">https://playholdgame.com/en/devlog/night-siege-pacing/</guid>
      <pubDate>Mon, 24 Aug 2026 00:00:00 GMT</pubDate>
      <description>The Brood gets a memory: siege waves analyze last night's damage log and probe the weakest stretch of your perimeter.</description>
      <content:encoded><![CDATA[<p>Until now the nights were honest but stupid: the Brood came in waves, the waves came from left and right, and with enough turrets you could watch an assault the way you watch rain. Starting this week, the Brood looks back.</p>
<h2>The Brood&#39;s memory</h2>
<p>Every siege now logs where your perimeter took damage: per wall segment, per night. The next siege reads that log and weights its spawns toward the weakest third. Neglect the south gate for three nights and the fourth night brings visitors. Many visitors.</p>
<p>It mattered to us that the system stays readable: the Brood isn&#39;t a dice cup, it&#39;s an opponent with legible logic. You can feed it: a deliberately weak segment as bait, the mech waiting on its rail behind it. That this trick works is not a bug. That it doesn&#39;t work twice in a row isn&#39;t either.</p>
<h2>Probes in phase 1</h2>
<p>Also new: probe attacks in the first phase of the night: single runners that test segments and vanish. They barely do damage; they collect. Intercept them before they return and the Brood&#39;s log stays blurry.</p>
<p>That finally gives the first half of the night a job of its own. It used to be a warm-up; now it&#39;s counter-intelligence.</p>
]]></content:encoded>
      <enclosure url="https://playholdgame.com/covers/night-siege-pacing.png" type="image/png" length="0" />
      <category>siege</category>
      <category>ai</category>
      <category>balancing</category>
    </item>
    <item>
      <title>DAY 57 — The War Rig: A Fortress on Rails</title>
      <link>https://playholdgame.com/en/devlog/war-rig/</link>
      <guid isPermaLink="true">https://playholdgame.com/en/devlog/war-rig/</guid>
      <pubDate>Tue, 18 Aug 2026 00:00:00 GMT</pubDate>
      <description>The War Rig is the colony's heavy, rail-bound colossus — transport, weapons platform, and the only way into the depths. An overview of what it is and everything it will be able to do.</description>
      <content:encoded><![CDATA[<p>If the base is home and the mech is the fist, then the War Rig is the fist that fits on the rails. It&#39;s the heaviest moving part of the game: an armored, modular locomotive that runs on a rail network through the colony and deep beneath it. Two influences are in there, openly — the War Rig from <strong>Mad Max: Fury Road</strong> and the human-built colossi of <strong>Pacific Rim</strong>. A vehicle you earn, upgrade, and won&#39;t want to give up until the very end.</p>
<h2>A train you drive yourself</h2>
<p>The War Rig isn&#39;t a cutscene vehicle. The commander stands in front of it, presses SPACE, and is aboard; from then on you drive it yourself — left, right, accelerate, hold. It&#39;s built from individual modules on a fixed 72×72 grid: locomotive, cars, superstructures. Because everything is modular, the rig can grow without us redrawing it — just like the base facade.</p>
<h2>The way into the depths</h2>
<p>The colony doesn&#39;t sit on a single level. Beneath the surface lies a rail network connecting several levels, and the War Rig is how you move through it. You drive east out of one level and back in on the west side of the next — the depths open up as one long, continuous route, not a menu choice. By now the rig is even the <strong>only</strong> way to change levels; the old elevator is gone, and even the mech travels on the same principle. If you want to go deeper, you drive.</p>
<h2>Three slots, nine weapons</h2>
<p>The heart of the War Rig is its loadout. It has three kinds of weapon mounts, and for each there are three weapons to choose from:</p>
<ul>
<li><strong>Flank</strong> — the side guns. <strong>Plasma</strong>, <strong>twin-barrel</strong> and the <strong>rail gun</strong> are already here, each in three tiers. The rail gun punches through: one shot takes several enemies on a line with it.</li>
<li><strong>Inner</strong> — the heavy, arcing weapons: <strong>mortar</strong>, <strong>rocket silo</strong>, <strong>frost</strong>. They hit what the flanks can&#39;t reach.</li>
<li><strong>Main</strong> — the systems that can turn a night: <strong>Tesla</strong>, <strong>main cannon</strong>, <strong>killer drone</strong>.</li>
</ul>
<p>You equip one weapon per kind — one flank, one inner, one main. That&#39;s already a lot of combinations, and each plays differently: a rig with rail gun and mortar keeps its distance, one with twin-barrel and Tesla wants the enemies close. The flank weapons already ride along; inner and main are coming piece by piece.</p>
<h2>Upgrading in the terminal</h2>
<p>All of this is managed in the War Rig area of the D.A.W.N. terminal: an upgrade tree with several branches, where you buy, equip and level up weapons — with a live preview that immediately shows what changes on the rig. No blind number-pushing: you see what you build.</p>
<h2>What it all comes down to</h2>
<p>The War Rig isn&#39;t just a tool for the road — it&#39;s the vehicle for the finale. Far below, at the end of the line, waits the thing the colony came here for in the first place. No more will be revealed here. Only this: whatever you&#39;ve bolted onto the rig on the way down decides whether you arrive.</p>
<p>Like everything in HOLD, the War Rig too was built back to front — first the rail and the colossus on it, then the drive, then the weapons, then the meaning behind it. The red stripe stays. The rest grows.</p>
<p><em>— Black Signal</em></p>
]]></content:encoded>
      <enclosure url="https://playholdgame.com/devlog/war-rig.png" type="image/png" length="0" />
      <category>warrig</category>
      <category>mech</category>
      <category>weapons</category>
      <category>roadmap</category>
    </item>
    <item>
      <title>DAY 50 — Core reactor: fuel storage and overdrive</title>
      <link>https://playholdgame.com/en/devlog/reactor-tab/</link>
      <guid isPermaLink="true">https://playholdgame.com/en/devlog/reactor-tab/</guid>
      <pubDate>Tue, 11 Aug 2026 00:00:00 GMT</pubDate>
      <description>The reactor gets a 5×4 fuel storage grid and an overdrive mode: more power traded against wear.</description>
      <content:encoded><![CDATA[<p>Until now the reactor was a number: power in, power out. That&#39;s enough for a spreadsheet, not for a feeling. As of v2_27 it&#39;s a place with decisions in it.</p>
<h2>The fuel storage</h2>
<p>The reactor tab of the D.A.W.N. terminal now has a storage grid, 5×4. Every fuel element is a physical object: mined below, processed in the shipyard, stored in the bunker. One glance tells you how many nights the colony has left. And that glance is supposed to hurt when the grid runs empty.</p>
<p>Twenty slots sounds like plenty. It isn&#39;t. A normal day burns just under one element; a siege night with every turret firing can take three. If your storage is full, you left something else lying on the surface.</p>
<h2>Overdrive</h2>
<p>The new overdrive mode gives +40% output at the flip of a switch: every turret fires faster, the perimeter lights reach further. The price is wear: every overdriven night damages a random reactor module, and repairs cost shipyard time that nobody has to spare during the day.</p>
<blockquote>
<p>Perimeter holds as long as the reactor does. The reactor holds as long as you do.</p>
</blockquote>
<p>The idea: overdrive should feel like a commander&#39;s decision, not a buff. You throw that switch on the night that matters, and you pay for it the morning after.</p>
<h2>The numbers</h2>
<p>Base drain drops from 0.62 to 0.556. Sounds tiny, but it moves the break-even line: a colony running two turrets now survives one more night without resupply. Playtest telemetry showed that days 12–15 ended at the energy wall too often. That&#39;s exactly where the curve should breathe, not break.</p>
<p>Also fixed: under certain conditions, the mech&#39;s layer change froze its rail segments, leaving the mech standing at the north gate as a very expensive statue. The Brood found that considerably less threatening than we did.</p>
]]></content:encoded>
      <enclosure url="https://playholdgame.com/covers/reactor-tab.png" type="image/png" length="0" />
      <category>dawn</category>
      <category>reactor</category>
      <category>ui</category>
    </item>
    <item>
      <title>DAY 44 — The New Base Design: One Facade, Six Bays</title>
      <link>https://playholdgame.com/en/devlog/hq-facade/</link>
      <guid isPermaLink="true">https://playholdgame.com/en/devlog/hq-facade/</guid>
      <pubDate>Wed, 05 Aug 2026 00:00:00 GMT</pubDate>
      <description>The base used to be a row of separate buildings. Now it's a single continuous facade with six roller shutters that rise at dawn — and behind them, six workshops you can enter.</description>
      <content:encoded><![CDATA[<p>For a long time the base was a collection: a shipyard building here, a reactor there, a dock beside it. Each its own icon, each on its own. That works, but it feels like a menu you look at from the outside — not like a place where 800 people live and work. So we rebuilt the base: as <strong>one continuous facade</strong> with six roller shutters set into it.</p>
<figure>
  <video class="devlog-clip" autoplay loop muted playsinline poster="/devlog/hq-facade.png" width="1640" height="470">
    <source src="/img/hq-facade.webm" type="video/webm" />
    <source src="/img/hq-facade.mp4" type="video/mp4" />
  </video>
  <figcaption>Dawn over the colony: the roller shutters rise and reveal the workshops. At night they fall again. (Loop)</figcaption>
</figure><h2>One building instead of six icons</h2>
<p>Technically the facade is its own module that assembles the front bay by bay from individual parts — shell, shutter, shell, shutter. That sounds cosmetic, but it&#39;s the foundation for everything else: because the bays sit at fixed positions, the game always knows where the center of each door is. The controls hang on exactly that later. And because the front is modular, a seventh bay can be added without repainting the whole picture.</p>
<h2>What lies behind the shutters</h2>
<p>Each of the six bays has its own interior, visible when it&#39;s open:</p>
<ul>
<li><strong>Shipyard</strong> — the robot arm welding drones and parts together. The sparks are the first thing you see in the morning.</li>
<li><strong>Reactor</strong> — the green pulsing heart of the colony. Its glow isn&#39;t decorative: it brightens or dims depending on how well the reactor is running.</li>
<li><strong>Upgrades</strong> — the workbench with the forge fire and the blueprint screens where weapons and gear are built.</li>
<li><strong>Mech Dock</strong> — still the quietest room: an empty maintenance corridor waiting for its mech.</li>
<li><strong>Bank</strong> — hologram, chair, terminal. This is where credits and resources are managed.</li>
<li><strong>Robo-Shop</strong> — the purple-lit store with the merchant robot behind the counter.</li>
</ul>
<p>Six rooms, six moods. Together they say more about the colony than any status readout.</p>
<h2>Day and night</h2>
<p>The roller shutters are tied to the day phase. At dawn they rise softly and expose the workshops; when night comes they fall again and the front becomes a closed, defensible wall. That&#39;s not just atmosphere — it tells the rhythm of the game without a single line of text: by day the base is open and productive, by night locked down and under cover.</p>
<h2>SPACE at the right bay</h2>
<p>Because the game knows the center of each bay, the commander only has to stand in front of it and press SPACE — and the matching area in the D.A.W.N. terminal opens. In front of the shipyard, the drone shipyard; in front of the reactor, the reactor tab. No menu to click through: you walk up to where the thing stands and use it. Diegetic, like the whole game.</p>
<h2>Back to front</h2>
<p>Like the whole base, the facade too was built back to front: first the night sky and the concrete, then the outlines, then the light in the windows and the life behind the shutters. The look stays that of the last human city — cold machine light, warm fire, deep black-green. When the shutters rise in the morning and six workshops start to glow at once, that&#39;s exactly the moment all of this was built for.</p>
<p><em>— Black Signal</em></p>
]]></content:encoded>
      <enclosure url="https://playholdgame.com/devlog/hq-facade.png" type="image/png" length="0" />
      <category>dawn</category>
      <category>base</category>
      <category>art</category>
      <category>ui</category>
    </item>
    <item>
      <title>DAY 20 — D.A.W.N. — the Terminal in the Bunker</title>
      <link>https://playholdgame.com/en/devlog/dawn-terminal/</link>
      <guid isPermaLink="true">https://playholdgame.com/en/devlog/dawn-terminal/</guid>
      <pubDate>Sun, 12 Jul 2026 00:00:00 GMT</pubDate>
      <description>The bunker has a computer, and everything runs through it: shipyard, reactor, War Rig, mech, outposts — and the commander themselves. A look at the D.A.W.N. terminal.</description>
      <content:encoded><![CDATA[<p>HOLD doesn&#39;t have a pause menu where you manage numbers. It has D.A.W.N. — a terminal that stands inside the bunker, where the commander runs everything that keeps the colony alive. You don&#39;t open it, you step up to it.</p>
<h2>One terminal for everything</h2>
<p>Along the top, the areas run like tabs in an operating system: Bunker, Outposts, Commander, War Rig, Mech, Aegis. Behind each sits its own system — the drone shipyard, the reactor, the bank, the inventory. Instead of six different menus in six different places, there&#39;s one place where it all comes together. Stand in front of the right bay in the bunker, press Space, and you jump straight into the matching area.</p>
<h2>The commander tab</h2>
<p>The screenshot shows the commander: your own figure in the center, unit &quot;SHIELD,&quot; assault rifle. On the right, the six attributes — Strength, Precision, Stamina, Tech, Leadership, Resonance — plus the splinter energy that powers abilities, and the free skill points you can spend. On the left, the deployment and the campaign: which grade you&#39;re playing, how many nights you&#39;ve survived, how high the brood pressure sits. At the bottom, the loadout — grenade and medkit on slots Q and E — and the carry weight that limits what you haul around.</p>
<p>It&#39;s a character sheet, but it feels like a person&#39;s cockpit, not a table.</p>
<h2>Why it looks like this</h2>
<p>The interface should feel like the view from inside your own helmet: bracket corners instead of boxes, monospace labels, the cold cyan of the machine against the warm amber of a warning. Nothing about it is a menu laid on top — it&#39;s a terminal in the world, with a figure standing at it and working. That&#39;s exactly what &quot;diegetic&quot; means: the UI belongs to the story, not above it.</p>
<p>The names in the screenshot — colony, client, grade — are still placeholders from the test phase and will change. The scaffolding underneath is standing.</p>
<p><em>— Black Signal</em></p>
]]></content:encoded>
      <enclosure url="https://playholdgame.com/devlog/dawn-terminal.png" type="image/png" length="0" />
      <category>dawn</category>
      <category>ui</category>
      <category>commander</category>
    </item>
    <item>
      <title>DAY 1 — Day 1: An Abandoned Mine</title>
      <link>https://playholdgame.com/en/devlog/day-1/</link>
      <guid isPermaLink="true">https://playholdgame.com/en/devlog/day-1/</guid>
      <pubDate>Mon, 22 Jun 2026 00:00:00 GMT</pubDate>
      <description>The first Signal Log is a look back: on June 22, 2026, at 19:41, the very first playable build ran. Here's what the start screen said back then — and what still holds today.</description>
      <content:encoded><![CDATA[<p>Every devlog needs a first entry. This one is a look back — written long after the day it&#39;s about. But it belongs at the beginning, because this is where everything started.</p>
<p>On <strong>June 22, 2026, at 19:41</strong>, the first build you could actually play was running. It still had a different name and a different face, but the core was already there. This is what the start screen said back then:</p>
<blockquote>
<p>ECHOES OF EXOGENESIS · PROTOTYPE — MINE VECTOR-7. An abandoned mine, reclaimed by nature. Secure the collection hall, raise the banner of the Iron Bull over the bunker and build it up level by level. Explore the enterable rooms on every floor — canteen, control room, lab — they tell what happened here, and hold mech blueprints. Your mech is unique in every game: its name, crew and weapons depend on what you find. At night the floodlights come on and the xenos pour out of the shafts.</p>
</blockquote>
<p><em>(Translated from the original German start screen.)</em></p>
<h2>What was already there</h2>
<p>Reading this today, it&#39;s striking how much of it stuck. The mine you hold level by level. Rooms you can walk into that tell a story instead of serving it in a cutscene. A mech that&#39;s different every run. And the night, when the light tips and something comes out of the shafts.</p>
<p>Even the colors were set: the cold cyan and the warm amber that still tint everything in the game.</p>
<h2>What changed</h2>
<p>The &quot;banner of the Iron Bull&quot; is gone. The title is a different one. The world no longer takes place in an abandoned mine somewhere, but on an alien planet — and what waits down in the depths has become a different story than I imagined on day 1.</p>
<p>But the thing about holding, building, waiting for the night: that was there from the very first minute. Which is exactly why the game is called what it&#39;s called today.</p>
<p>Welcome to the Signal Log. From here on, this is where you&#39;ll regularly find what came out of a build day — with images, sometimes a clip, and no detours.</p>
<p><em>— Black Signal</em></p>
]]></content:encoded>
      <category>origin</category>
      <category>making-of</category>
      <category>signal-log</category>
    </item>
  </channel>
</rss>