The north wall is at six percent and the countdown reads eleven.
That is a screenshot from an actual Night 1 raid in the current Wreckhold build. It is not a placeholder. The wall percentages are real, the DAWN IN timer is real, and the raider breach that knocked the north face from 89 to 6 while the south dropped to 33 happened in about thirty seconds of active play. Everything devlog 01 described about the day loop and the scrap economy — route planning, carry triage, the six competing claims on your material budget — feeds into this moment. The night is where you find out whether the day shift was good enough.
This devlog covers what happens after dusk: the night raid system, the DAWN IN countdown, the wall integrity model, and what a full AI QA pass revealed about the build’s readiness for human hands.
The Night Shift in Practice
Devlog 01 described the night loop in design terms: raids escalate, active defense matters, post-raid clarity teaches the player why they failed. That was the plan. Here is what the implemented system actually looks like.
When dusk falls, the HUD transforms. The warm amber field goes dark crimson. The day-shift instruments — DUSK IN countdown, HAUL counter, STOCK readout — are replaced by a combat HUD: SCRAP, KILLS, DAWN IN, directional WALLS health, WAVE progress, and a RADAR overlay in the corner.
The critical number is DAWN IN. It appears as a large countdown in the center of the screen during active raids. Every decision the player makes at night is measured against that number. Repair the north wall or hold position? Fire a flare to reveal the next wave or conserve charges? The DAWN IN clock is the governing constraint, the same way the DUSK IN clock governs the day shift. Both loops have a timer. Both timers create the same pressure: you cannot do everything before the clock runs out.
RAIDERS appears in the top bar when hostiles are active. The original HUD layout put RAIDERS and DAWN IN adjacent, which created a visual collision — the two most important pieces of night information competing for the same read space. That collision was caught during QA and resolved. The labels now have clear separation. Small fix, but night readability is the difference between a player who responds to a breach and a player who does not see the breach until the wall is gone.
Wall Integrity: Four Faces, Four Problems
The fortress is not a single health bar. Each wall face — north, east, south, west — tracks its own integrity percentage. The directional health panel in the top-right corner of the night HUD shows all four values simultaneously: N 89%, E 88%, S 63%, W 77% at raid start, for instance.
Raiders do not distribute damage evenly. They pick a direction. The INTEL readout during the day shift hints at which face will take the first hit — INTEL: NORTH THREAT or INTEL: WEST THREAT — but multi-wave raids can shift direction. A player who shores up the north face because the intel said north, then ignores the south, gets a 33% south wall and a breach path they were not watching.
The EXPOSED tag appears on any wall face that drops below a critical threshold. It is not subtle. Red text, hard to miss, positioned directly on the compromised section. EXPOSED means that wall face will fail under sustained pressure unless the player actively intervenes — either by spending repair materials during the raid or by repositioning to defend the breach.
Wall percentages carry between nights. A wall that ends a raid at 63% starts the next day at 63%. The scrap economy from devlog 01 — specifically the hull repair claim on the material budget — is the mechanism for restoring wall health. Skip the repair, accept the risk, spend the scrap on expansion instead. That is a real decision with consequences that arrive at dusk.
The Night HUD: Reading the Raid
Night combat has more active information than the day shift, and the HUD has to surface all of it without burying the player.
The current night layout:
- Top bar: Night number, SURVIVOR status, SCRAP collected, KILLS, DAWN IN countdown, repair hotkey, flare hotkey, focus keys, WALLS aggregate bar
- Right panel: Directional wall health (N/E/S/W percentages), raider mood indicators, RADAR minimap
- Bottom bar: Q FLARE charges, SHIFT DASH stamina, HP bar, WAVE progress (e.g., WAVE 0/2), NEXT WAVE timer
- Center overlay: DAWN IN countdown (large), NIGHT RAID announcement with raider count, HOLD UNTIL DAWN status
The player has three active tools during a raid: repair ([E], costs scrap), flare ([Q], reveals raiders and illuminates the field), and focus ([1-4], directs attention to a specific wall quadrant). Combined with movement and dash, that is the full night toolkit. Enough to respond meaningfully. Not enough to trivialize the raid.
The HOLD UNTIL DAWN indicator replaces the wave counter once all spawned raiders are active. At that point, the objective shifts from “clear the wave” to “survive until the clock hits zero.” That transition — from active defense to pure endurance — is one of the highest-pressure moments in the loop.
Dusk Scouts and the Transition Window
The transition from day to night is not instant. As the DUSK IN counter drops into single digits, dusk scouts appear in the field. The game surfaces a clear warning: “Dusk scouts spotted! Head back or fight.”
This creates a decision point that devlog 01’s day loop design anticipated but did not spell out. The player who is still in the field when scouts appear has to choose: abandon the current haul and sprint for the perimeter, or fight through the scouts and risk arriving late, damaged, and out of position for the first wave.
The scout encounter is not a separate game mode. It uses the same movement and dash mechanics. But the context is different — the player is outside the walls, possibly loaded with materials, and the DUSK IN clock is the enemy as much as the scouts are. Getting caught outside at nightfall with a full haul and low HP is a compound failure state that started with a day-shift route decision.
Insane Difficulty: The Honest Stress Test
The build ships with multiple difficulty tiers. Insane difficulty exists not as a marketing checkbox but as a design validation tool.
On Insane, the scrap economy is tighter, raids escalate faster, wall damage is higher, and the DAWN IN countdown is shorter. The same day-shift decisions that produce a comfortable buffer on Normal produce a razor margin on Insane. A player who under-invests in hull repair by one cycle — spending the material on a perimeter extension instead — loses a wall face on Night 2 instead of Night 5.
Insane difficulty exposed design assumptions that Normal difficulty obscured. The carry limit that felt generous on Normal becomes a genuine constraint when raid damage is higher and repair costs eat more of the budget. The route planning that felt optional on Normal — near wrecks are fine, why risk the far ones? — becomes mandatory when the scrap yield needs to be higher just to maintain wall integrity.
The AI QA harness ran full campaigns on every difficulty tier, including Insane. The defeat pathways — fortress collapse, player death, dawn failure — all resolved correctly. The game does not softlock on a loss. It reads the failure state, surfaces the cause, and resets cleanly. That sounds basic, but getting defeat resolution right is a prerequisite for a game where defeat is a core teaching mechanism.
What the AI Found
The current Wreckhold build has passed a comprehensive AI QA cycle. Here is what that means in practice.
The QA harness ran automated playthroughs across all difficulty tiers, testing both victory and defeat pathways. It verified that the day/night transition triggers correctly, that raids spawn and resolve as designed, that wall damage accumulates and repairs apply properly, that the DAWN IN countdown terminates the raid at zero, and that defeat states — including mid-raid fortress collapse on Insane — resolve without crashes, softlocks, or corrupted state.
The test suite covers the full session lifecycle: menu navigation, campaign start, day-shift scavenging, dusk transition, night raids, dawn resolution, and inter-day carry-over. Forty-two test scenarios passed. Zero failures. Twenty-one screenshots captured across the test matrix document the visual state at each checkpoint.
The QA pass also caught the night HUD label collision mentioned above — RAIDERS and DAWN IN overlapping in the top bar — which was fixed before the current build was locked. That is the value of automated QA: it finds the thing that a manual tester might not notice until the fourth or fifth night, when the label overlap finally matters because both values are changing fast.
The build is itch-ready in the technical sense: win64, linux-x86_64, and .love packages all exist and launch cleanly. The AI has played it. The machines say it works.
Where We Are
Wreckhold is at the PLAYTESTING milestone, waiting on a human play session.
That is an honest status. The AI QA harness can verify that the game runs, that systems interact correctly, that defeat states resolve, and that the night raid loop functions as designed. What it cannot verify is whether the pressure curve feels right to a human player. Whether the DAWN IN countdown creates the intended tension. Whether the scrap economy forces interesting decisions or just frustrating ones. Whether the first night raid teaches the player what went wrong or just punishes them.
Human playtesting is the final gate before the build goes public. The itch packages exist. The game launches. The systems work. The question is whether it is fun — and that is a question only a person can answer.
The day shift still works the way devlog 01 described: route, carry, time, triage. The night shift now works the way it was designed to: raids, walls, countdown, dawn. The loop is complete. The pressure is real. The next step is a human sitting down, hauling scrap, building walls, and finding out whether the fortress holds.
The wrecks are still out there. The sun is going down. The walls need you.
Wreckhold is in active development. Follow x00f.com/games/wreckhold/ for updates.
