Devlog
What Claude Fable 5.1 built with a night and an empty project
I handed it a fresh UE 5.8 Third Person template, ECABridge's roughly 780 editor commands, and Forage pointed at my own Fab library. The idea — a museum hub whose portals are showcase levels for a category of the tool surface — was mine. Everything after that, it built, tested, and photographed on its own.
Five of nine planned levels got built by morning. Three of those five are rough — presentable, not polished — and this devlog says so plainly, chapter by chapter, in the order it actually happened: the wins next to the misses next to the fixes.
01
Sourcing the gallery
Before any building started, two establishing shots from the Museum Environment Kit confirmed the purchased asset pack actually read as a museum — the model's starting material, not anything it built itself.


02
Building the hub
The concept: a museum gallery where each doorway is a portal to a showcase level for one category of the tool surface. Getting there took a working single-portal prototype, a row of them down both walls, and two rounds of fixing that same row after it broke in two different ways.






03
Terrain & Weather
The environment level was the first one handed to a subagent working alone, and it's also the roughest of the five — dark, pit-shaped at first, and hit by a rendering bug serious enough to turn the whole level black.



04
Particles & Motion
Niagara turned out to have its own blind spot: none of the static screenshot commands tick the running world, so a plinth full of particles looks completely inert until you catch it live in Play-in-Editor.





05
Surface & Light
Eight node-authored materials laid out on a table for comparison, in a room that never got a front wall — and an exposure problem a late fix didn't fully undo.



06
Sound & Signal
The audio hall was supposed to read as a dark temple nave. It shipped instead as a sunlit corridor open at both ends — until the last capture of the night, when the open end finally got closed off.



07
The flythrough
A 12-second Movie Render Queue flythrough of the finished hub, closing out the night. The first render flew through the pyramid centerpiece; the second flew through the portals themselves. This is the third — Video QA'd before it shipped.


What I learned
The gotchas any new hire would hit — just faster, and overnight
- ✦Claude Code's own Unreal MCP connection failed to come up at boot and never reconnected for the rest of the run — everything after that went through ECABridge's own Python client instead, one call at a time.
- ✦None of the static screenshot commands tick the running world. Niagara particles, and anything else that's animating, only show up in a capture taken during Play-in-Editor.
- ✦A freshly created mesh renders on the default gray checkerboard material until something is actually assigned to it — an easy 'is this even broken' moment the first few times it happens.
- ✦Landscape materials that blend based on painted layer weights render solid black with nothing painted yet. Start with a plain material, paint the blend later.
- ✦A swept polygon mesh builds flat in one plane — the wrong roll value buries it face-down in the floor instead of standing it up. The fix was a single sign flip, once we knew to look for it.
- ✦Text3D handedness isn't consistent: a standalone actor and one parented under a Blueprint root can need opposite yaw values to read correctly. Mirrored, upside-down text showed up more than once before that clicked.
- ✦A manual post-process exposure edit can leave an entire level rendering solid black in every capture path — including the live editor viewport — until you close and reopen it. Auto-exposure bias only, from now on.
- ✦Subagents sharing one running editor have to work strictly one at a time, each pinned to its own level. Two open levels in the same editor at once is how you get spawns landing in the wrong place.
- ✦A failed 'create new level' call doesn't fail loudly — it silently leaves you inside whatever level was already open, and everything spawned next lands there too, unless you check first.
- ✦Forage can log into Epic without a person at the keyboard if the browser is already signed in: grab the redirect auth code and use it within about a minute, before it expires.
What's next
Four wings, still empty rooms with a return portal
Cinematics, gameplay, lighting, and characters are placeholders — bare rooms with nothing built in yet. The UMG splash screen, main menu, and popups that were supposed to wrap the whole hub are still owed too. Everything that shipped this round — environment, materials, audio — is due a polish pass before any of it is done-done. The flythrough sequence is already set up for a re-render once the rest catches up.