Wreckhold Devlog 01 — Before Dusk: The Scrap Economy, the Perimeter, and the Night-Raid Loop
Every trip outside the walls is a wager.
That is the shortest possible description of Wreckhold’s core design loop, and the more we’ve built into the pressure-build survival system, the more that sentence holds up. Wreckhold is the ninth title in the Dark Factory slate — a salvage-fortress survival game about daylight scavenging, scrap triage, perimeter construction, and holding the line once the sun goes down.
This is the first devlog, and it covers the design backbone: the day/night architecture, the scrap economy, the perimeter logic, and what separates Wreckhold’s lane from every other game that uses the phrase “base building.”
The Pitch That Survives Contact
There is a tendency in survival game marketing to describe the loop too abstractly. You “gather resources.” You “build structures.” You “survive the night.” That language describes dozens of games without distinguishing any of them.
Wreckhold’s pitch is tighter: build a scrap fortress by day, survive the raid after dark.
Four words on each side of the comma. Day verb, night verb. The player can see the whole pressure loop in the tagline before they start playing. There is no mystery about whether this is a cozy automation game or a stress-pressure survival game. It is a stress-pressure survival game. The fortress is made of scrap because you do not have better materials. The raids are real because the night is hostile. Dawn is the only metric that matters.
That specificity is a market decision as much as a design decision. The word “Wreckhold” sounds like a place that holds — barely. The subtitle tells you why. The commercial read is not “base builder with a darker theme.” It is salvage-first survival, which is a distinct lane with a distinct player.
The Day Loop: Scavenging Is the Hard Part
Daylight is when the real decisions happen.
The game does not start with resources. It starts with wrecks — dead machines, collapsed structures, and abandoned equipment scattered across zones outside the fortress perimeter. Those wrecks contain materials. Materials are what the fortress is built from and what keeps it functional. You need to go out and get them.
The day loop is a route and carry problem. Every scavenging trip has three variables:
Route: Which wrecks do you hit? Near wrecks are safer but lower yield. Far wrecks have better material density but cost more time and create more exposure on the return leg. Routes that look efficient on the map often reveal complications in practice — a zone that requires crossing open ground, a wreck cluster that puts you far from the perimeter when the clock is running short.
Carry limit: You cannot bring back everything. Your carry capacity is hard-capped, which means every scavenging run requires a constant evaluation: keep picking, or turn around now with what you have? The pressure to go deeper — there is one more good wreck just past this sector — is constant. The discipline to turn around before the clock forces you is a learned skill.
Time: The day clock is the governing constraint on every decision. You know roughly how much time you have before dusk. You do not always know how long the next section of your route will take. Miscalculations are not hypothetical costs. They are actual emergencies — the player caught outside the perimeter when darkness falls has a perimeter problem and a survival problem at the same time.
The fantasy of the day shift is the clean haul: good route, full carry, home before the clock turns, scrap banked and ready for fortification. That happens sometimes. Most of the time, something is off — the yield was lower than expected, the route took longer, a wreck that looked accessible had complications. The day shift is a lesson in expectation management.
The Scrap Economy: One Budget, Six Claims
Scrap is not a single resource. It is a category that subdivides immediately into competing demands.
The materials you bring back from the day shift go into a shared pool. That pool gets claimed by six competing systems:
Hull repair: The fortress takes damage from raids. Wall sections, reinforcements, and structural elements need materials to patch. Letting damage accumulate across multiple nights is a losing strategy — the fortress that took three nights of moderate damage without repair is the fortress that collapses under a coordinated raid.
Power infrastructure: Generators, lighting, and active defense systems all require fuel cells or equivalent material inputs. A perimeter without power is a perimeter without sensors, active deterrents, or emergency response capability. Dark perimeters invite escalation.
Perimeter extension: Growth costs. Every new wall segment, every new reinforcement layer, every new defensive structure requires materials from the day shift. Expanding the perimeter increases what you can protect and increases what you have to defend. Net gain requires that the expansion was worth the material cost before the next raid tests it.
Supply cache: Emergency materials stored in reserve for post-raid response, critical repair windows, or mid-crisis construction needs. Running the economy at full spend every cycle means no buffer when the unexpected happens.
Scavenging equipment: Carry capacity upgrades, route tools, and equipment that makes future day shifts more efficient. These are investments that pay forward — spending materials now to bring back more materials later — but they compete directly with immediate defensive needs.
Personal equipment: Survival gear for the player character, since the day shift involves direct exposure to the same hostile conditions that the fortress protects against at night.
The economy is designed so you almost never have enough for everything at the correct priority. There is always a second claim on the same material. The decision tree is: which shortage hurts worst right now, and what are we accepting as a risk in exchange?
That is the correct design posture for a pressure game. Abundance removes triage. Scarcity creates it.
The Perimeter: Layout Is the Game
Night reveals what the day built.
The fortress perimeter is not decorative. Wall placement, coverage angles, chokepoint design, generator placement, and reinforcement layering all determine how a given raid resolves. Raiders do not hit a generic “fortress health” bar. They find weak points. They exploit gaps. They hit the angle you did not shore up, the section you planned to reinforce tomorrow, the generator you left exposed to prioritize hull materials.
The perimeter design philosophy has two rules:
Honest walls: A wall section that looks covered must actually be covered. Placing a wall and assuming the adjacent structure provides backup coverage is a mistake. The raid will find the assumption and exploit it. Wreckhold’s defense system tracks coverage angles specifically to prevent the player from rationalizing gaps that are not actually filled.
Chokepoint thinking: The fortress does not have to be impenetrable. It has to be defensible. That is a different design problem. A straight wall is hard to defend. A wall with controlled entry points, coverage angles, and depth creates positions where the player can respond to a breach before it compounds. Chokepoints concentrate the threat into a manageable zone. Open perimeters distribute the threat until it is everywhere at once.
The layout decisions made during the first few day shifts compound. A fortress built with chokepoint thinking early is easier to expand and easier to reinforce. A fortress built reactively — wall wherever the last raid hit — becomes a maze of patches that does not actually hold together.
Dawn is the report card. A night you survive is feedback about what works. A raid breach is specific information about what does not. The fortress improves through iteration or it fails through neglect.
The Night Loop: The Audit
Night is not a separate game mode. It is the consequence of everything the day shift decided.
The raid structure escalates across the campaign. Early raids are pressure without complexity — a test of whether the perimeter is minimally functional and whether the player knows how to respond to a breach. Later raids introduce coordination, multiple breach attempts, and tactical variety that requires an active response rather than a passive one.
The player is not a passive observer during a raid. Active defense — repositioning, patching, prioritizing response — is part of the night loop. A player who built a good perimeter but cannot respond effectively to a breach still fails. A player who responds effectively to breaches in a structurally weak perimeter delays the failure but cannot prevent it indefinitely. Both elements matter.
The worst outcome is not losing a raid. The worst outcome is losing a raid without learning why. Wreckhold’s raid resolution is designed to be readable — the breach point, the raid path, the structural failure — so that the player can identify the correct day-shift response. Post-raid clarity is part of the game’s teaching function.
Dawn resets the loop. Materials depleted. Perimeter in its post-raid state. Day clock starting again. The player assesses what held, what failed, and what the next day shift needs to prioritize.
That is the loop. It is tight, it is readable, and it escalates through investment in the player’s decision-making rather than arbitrary difficulty scaling.
Where We Are
Wreckhold is in BUILDING status. The lane is locked — name, tagline, premise, and systems spine are defined. The day/night architecture, the scrap economy, the perimeter design logic, and the raid structure are all established at the design level.
The active build is implementing the day loop first: movement, carry limits, wreck interaction, and the basic resource flow. Getting the day-shift feel right is the prerequisite for everything else. If the scavenging decisions are genuinely interesting — if every trip outside the walls involves real choices about route, carry, and timing — the rest of the game has a foundation worth building on.
Perimeter construction is the second build priority. Wall placement, coverage angles, and the first pass at raid testing need to work in concert before we can tune the economy.
The build is early. The design is solid. The franchise has a commercial lane that is distinct, readable, and pressure-first.
The wrecks are out there. The sun is up. Start hauling.
Wreckhold is in active development. Follow x00f.com/games/wreckhold/ for updates.
