C:\GRIFFIN\PROJECTS\GAMES\TRUSS>

[@] MAP 
###C############
#...........$..#
#.&&..&&...&&..P
#......@.......#
#...*......&&..#
#..............#
######H#########
GAMES/TRUSS

Doors are hotkeys. Or click the screen and walk with the arrow keys.

TRUSS

A Godot city-builder prototype where a truss solver decides which buildings survive thirty years of storms, code changes and neglect.

Status
Simulation prototype
Stack
Game · Simulation · C#/.NET · Godot · Structural Engineering

At a glance

  • Outcome: TRUSS: Time-Resolved Urban Structural Simulator is a city-builder in which every beam, brace and footing is a real member solved under real loads. You are the mayor and building authority of a district through thirty years of storms, code changes and deferred maintenance.
  • Status: Pre-alpha prototype. Five scenarios run in the exported desktop build, from the single storefront of Open for Business to the thirty-year Long Campaign; itch.io demo first, then Steam, targeting 2027.
  • Role: Solo. Defined the product decisions, system boundaries, solver specification and contracts; reviewed AI-assisted implementation.
  • Stack & libraries: Godot 4.6.3, .NET 8, a C# solver and domain core, GDScript for interaction, and a Nix flake pinning the toolchain.

TRUSS is a city-builder, like RollerCoaster Tycoon crossed with Kerbal Space Program. Every beam, brace and footing in the district is a real structural part with real dimensions. The game calculates the loads on each one. When the ground shakes or the season’s storm arrives, each part either holds its load or fails. You play the mayor. You write the building code with a visual block-based editor, set the inspection budget and hire inspectors. Owners and contractors then build to your code with their own politics and goals. Everyone depends on the same cycles of weather and resource supply.

You can also play as an inspector. Walk into any building in first person and open the CAD editor to mark what you find, in new construction or old. Then see whether the contractors fix it. You can run a wind test to prove a fix without waiting for the storm. Contractors build with the same parts and the same structural calculations you use, and they have to stay on budget. When a frame comes down, you can trace the chain from the client’s brief to the contractor’s shortcut to the missing brace to the overloaded path the force took.

The structural math lives in its own C# core, separate from the game scripts that handle clicks and movement. Scenarios play as a campaign or in free play, each with its own environment and physical constants. Five scenarios run in the desktop build today, from the single storefront of Open for Business to the thirty-year Long Campaign. More scenarios, departments and city offices are planned.

SCREENSHOTS

The wind test on the as-built storefront frame, colored by stress at 35 m/s, the last step it held. The solver decides which members fail; the falling red members only replay that result.
The CAD view after the wind test. The Wind Test report panel reads: survived wind speed 35.0 m/s, collapse state COLLAPSED, first limit exceeded: utilization at 40.0 m/s (value 1.083), first failed member 60, removed members 60, 56, peak horizontal displacement 0.06602 m, peak utilization Infinity, collapsed True, no repair profile supplied. The blue frame has orange members along its top chord and two red members, with thin green lines for the displaced shape. The status bar reads: Wind test stress at 35.0 m/s, the last step the frame held. Max utilization 0.83, max drift 0.013 m. Orange > 0.75, red > 1.00.
The wind test report. The frame holds at 35 m/s and fails at 40 m/s, where member 60 reaches a utilization of 1.083. Members are colored by their utilization at the last step held.
First-person inspection view of the storefront. A blue finish panel is lifted above the opening, showing a red-marked empty bay between braced bays. The status panel reads: Evidence found: Empty gusset plates / unused holes. The brace connections carry bolt holes but no diagonals.
During inspection, lifting the storefront's finish panel shows the empty bay where the brace was removed, with its unused bolt holes.
Long Campaign legislate screen, season 1 of 6, storm in 38 days. The left panel lists five structural code rules and two authored code presets dated day 40 and day 120. The right panel shows an era timeline of six seasons, five years each, with the code generation moving from v1 to v3.
The Long Campaign runs thirty years as six seasons, and its era timeline moves the building code through three versions. Captured October 1, 2026, before the district view landed; the truss behind the panels is the first slice's.
The season 1 debrief on day 38, after a 230 m/s storm. The scorecard reads Safety: 22 and lists two buildings, owner-0001 and owner-0002, each surviving 230 m/s with 0 collapsed and 25 and 19 storm-time occupants. Below it, a collapse forensic report for parcel-0003 under longcampaign-building-code v1 lists a five-step causal chain, Provision, Design, Inspection, Condition and Outcome, ending: the structure collapsed after surviving to 95.0 m/s in the 230.0 m/s storm. The Rebuild tab on the right reads: No rebuild or scarcity outcomes are available.
After the storm, the scorecard lists the wind speed each building survived, and a forensic report traces one collapse from its governing code to the outcome. Captured October 1, 2026, before the district view landed.