Hit by Your Own Lorry
Saturday, and a lift that went up one floor too far
Saturday was the day off, so the gym came first and then the whole of the rest of it went on the game. It turned into one of those days where nothing finished and four things moved. Most of the work was the kind that happens while James is somewhere else: the agent, Claude Code Opus 5.5, ran a queue of staged jobs against the editor in slots.
The hotel went first, because it had changed its mind overnight.
On Friday night James had been asked how the top floor of the hotel should be reached. There was a lift to the fourth floor and no stairs, and the proposal on the table was to extend the east turret spiral all the way up. He said yes, preferring the spiral. The agent staged it just after midnight: a section in the runbook, a Blender kit, layout checks, a gate that counted 18 checks. None of it opened the editor, because nothing had a slot yet.
At two minutes past six on Saturday evening James looked at it again and asked a different question: can we just make the lift go there? The answer was that the lift already went there. The fourth floor became lift-only, which is what it had been in the first place.
Undoing it took about twenty minutes and cost nothing in the game. The two spiral scripts were set to refuse to run unless an environment variable was switched on, the offline check for the stair stopped gating, the runbook sections were moved under a heading that says SHELVED, and the handover got a new line on top and a "dropped, kept for history" prefix on the old one. Every file touched had a backup beside it and a copy on the second drive. The gate dropped to 15 checks, and passed.
The agent's work on the spiral was not wasted in the way that sounds. The proposal that sat next to it was the useful bit, and it was about something else.
Four lift links and nobody on the stairs
The thing James had actually noticed on Friday was that hotel residents never take the stairs. They are on four floors, there is a grand staircase, and everybody queues for the lift.
The agent read it out of the live source before it wrote a word. Each of the four lift floors has a smart link, a hand-placed bridge that tells the pathfinder two bits of navmesh are connected. Each one is about 4.4 metres long in path cost. The grand stair between two floors is about 15 metres of walking. The pathfinder takes the cheaper route every time, so the stairs lose, and they only get used when the lift links are switched off, which happens when the lift is jammed.
The first idea in a case like this is to make the resident choose the stairs at the start of the trip. The agent ruled that out in the proposal. The lift never learns about a trip until the body is already standing at the lift doors on a path that was built through them, so there is no "start" to decide at. To make somebody walk the stairs you need a path that avoids the lift for that person while everybody else still uses it. The recommended way is a navigation area for the lift links with the same cost as before, so nobody's route changes, plus a filter that excludes that area, chosen per move.
It is a proposal and not a build, and it says so. There is a second catch underneath it. The grand stair's own navigation has not been tested since the lift links went in, and the navmesh has been rebuilt three times since. Any rule that sends people up the stairs starts with a probe that walks them. That is the next thing, not this.

The lorry that knocks its own crew down
The bin round got its sixth slot in the afternoon: a full round from sign-on to the payslip, run in the editor on the Low setting, on the real town, with the autopilot driving. It finished. Twenty minutes of real time, 1,315 of 1,316 waypoints, six bins tipped, two empties returned, eight body items taken to the incinerator, and a payslip of £43.40 that started from nothing.
Before that, the check was the slow part. Re-dumping the five Blueprints the round depends on takes about 27 minutes, and for all of it the editor says "not responding" and is working on one core. The agent waited it out. The dump leaves all five dirty, and saving after it would write a read-only read back over the live files. The editor was closed without saving, which is the right ending.
The round itself finished and the part that matters did not behave. Five times the player was knocked down, and three of those added four hours to the game clock, because a knockdown at that severity costs a rest. The clock went from 06:09 to 10:09, from 10:25 to 14:25 and from 14:30 to 18:30 on a shift that lasted twenty real minutes.
None of the five happened while riding. The slot before had fixed that, and every riding sample in this run read no collision and no knock. All five were on foot, just after getting out beside the cab or when the autopilot teleported the player to the back of the lorry. The vehicle that did the knocking, by the log, was the bin lorry itself. It was stopped or creeping at the time.
So the lorry that carries the crew has a box in front and behind it that knocks anything that gets in the way, and the player walked into it because the job told them to. A real player stepping off the nearside would meet the same box. The fix is to exempt that lorry from knocking a player while the round is running, or to ignore its creep speeds. The agent wrote down both and picked neither. A lift also ran longer than 20 seconds once, at the very moment of the first knock, which supports the earlier guess that a knockdown in mid-cycle stalls it.
Every stall in the run read as blocked, and some of those were horns, which is what blocked looks like to a road with other people on it.
A beard that would not take, and a skin that could not be read
The grooming thread had a day of its own. Residents grow hair and stubble over days in the game, and the plan is for it to show: a hair trim amount and a stubble mask driven by how long since the barber. The data half was already in. The material half had been blocked since mid-afternoon.
The block was the shape of the materials. Both the hair and the skin master are built on Material Attributes, so there is no loose Opacity pin or Base Color pin to connect to, and the root of the skin is a Named Reroute that points somewhere else. The agent's first script walked the attributes chain looking for the node that sets the pin, and that worked for the hair, which was spliced at 19:31 with all eight connections made and no compile errors.
On the skin the walk failed. The reroute's declaration, the piece that says where it points, is protected in 5.8 Python and cannot be read. The material also has no Set node of its own to splice at. The fix the agent wrote was to copy a Set Material Attributes node from the finished hair material into the skin one, disconnect every pin on it, and wrap the root with it. That runs on 5.8 because duplicating an expression re-parents it across materials. It had to be a copy because Python cannot add pins to a new Set node: the inputs resize only when the graph is open in the editor.
The skin run at eight minutes to eight made thirteen connections, recompiled with no errors and saved, with a backup taken first.
The data pass in the town also ran: one resident went from a hair length of 12 days out of 14 to nothing, and back to 14 days of hair and 7 days of stubble, which the system read as due for the barber. The before and after stills were not taken. James had asked at that moment to move on, and the pawn was still at the intro spot with nobody framed. Skin stubble cannot show until the next slot has run.
Route 7, and a rota with holes in it
The bus thread was all spreadsheets, and none of it is in the editor yet. Route 7 is the airport. The rota solver says the airport route needs six more drivers than the town has spare, and the roster has exactly one unemployed resident who passes the checks for it. The other five are new residents, written to the same pattern as the earlier drivers, with addresses on streets that exist.
The numbers the agent was most careful about were the driverless hours. Under the current hand-out, which gives a driver to the lowest-numbered bus first and holds them for the whole duty, the airport buses go without a driver for 67 bus-hours a week. A service-aware hand-out, staged as a gap build, takes the whole town from 145 driverless bus-hours to 96, and the airport route from 67 to 38. It has not been run, and the model rests on a flag, whether a bus is in service, that was hand-built and has not been watched at runtime.
There was a smaller thing on the same list. One resident falls through the world after spawning, at a height of minus 40,000. The cause is a work block that resolves to the skate park, whose entry point has no navmesh and no floor collision, so he spawned where the sim put him and dropped. The fix is staged as a rescue for bodies that spawn off the navmesh, and another for ones that fall below the kill height.
The scoreboard, as of Saturday night
The roadkill build went green at the same time, which is the first half of getting animals killed on roads sold to the butcher. Four of its queue items are ready and are the next thing to run.
A day with a gym session in it, one lift question, a lorry, a material and a rota. GTA VI will have departments for each. Here it was a queue, a Saturday, and a handover that got a new line on top.
The fault
Hotel residents never use the stairs in Unreal Engine 5.8 because lift links always win the pathfinder
Four smart links for the lift are about 4.4 m each in path cost, against about 15 m of walking for a flight of grand stair, so the pathfinder chooses the lift every time. Stairs are used only when the links are switched off.
- Wrong guess: choose the stairs when the trip starts. The lift only learns of a trip when the body is already at its doors.
- Cost: one overnight proposal, one spiral kit that was then shelved.
The fix
The agreed fix for residents ignoring stairs, as proposed
Give the lift links their own navigation area at the same cost so nobody's route changes, and exclude that area with a per-move filter. Prove the grand stair's navigation with a probe first, because it has not been tested since the links went in. Staged, not built.
The fault
The player is knocked down by the vehicle they are working with in a bin round
Five knockdowns in one full round, all on foot, the knocking vehicle the bin lorry itself. Three added four hours to the game clock each. Riding knocks were zero.
- Cause: the autopilot's teleport or a step off the nearside lands the player inside the lorry's own knock box while it creeps.
- Not yet fixed: exempt the lorry for a player on the round, or ignore its creep speeds.
The fault
Python cannot read a Named Reroute declaration in a Material Attributes graph in Unreal Engine 5.8
NamedRerouteUsage has a protected Declaration, so a script that walks the graph to the node that sets Base Color stops at the root. Python also cannot add pins to a new Set Material Attributes node.
The fix
Splicing a material when the root is a Named Reroute
Duplicate a Set Material Attributes node that already has the pin from another material, disconnect all its pins, and wrap the root with it and a Break node. Duplicating an expression re-parents it across materials. Back up first.
The kit
What was used
- A queue of staged runbooks, run in slots by the agent through the editor's Python and a computer-use loop.
- Offline gates that passed before anything opened the editor: 15 of 15 for the hotel, plus rota recounts for every hour of the week.
- A backup folder beside every file touched and a copy on a second drive.
Plain English
| Term | What it means |
|---|---|
| navmesh | An invisible map of walkable ground that characters use to work out routes. No navmesh, no walking. |
| nav link | A hand-placed bridge that tells the pathfinder two patches of navmesh are joined, for gaps it cannot see across on its own - a narrow doorway, a jump, a ladder. Both ends snap to the nearest walkable floor, which is right until the nearest floor is the one below. |
| PIE | "Play In Editor" - pressing play inside the editor to test the game without building it first. Fast, and it behaves subtly differently from the real build. |
| tick | Code that runs every single frame. Cheap once, ruinous sixty times a second across a thousand actors. |
| gap build | One numbered, self-contained batch of C++ changes to the town's code, prepared and checked offline, then compiled into the game in a single build that backs itself up and undoes itself if it fails. |
Things we still need to fix tomorrow:
- Run the stair navigation probe on the grand stair before any rule sends people up it.
- Stop the bin lorry knocking a player who is on the round, then rerun slot 6.
- Skin stubble: run the next grooming slot, then take the before and after stills.
- Route 7: James decides the five new residents and the service-aware hand-out.
- Roadkill: the four ready queue items are next.