I made Roblox in a chat window

I asked Claude to make something 3D. That's it. That's how this started.

I'd been messing around with 2D stuff — a castle, some basic tools, an ERP thing for the business. All built the same way, just chatting. But I hadn't pushed into 3D yet. So I asked.

// what happened

First attempt — black screen. The iframe sandbox was killing the pointer lock API. We debugged it together. Second attempt — black screen again. Third attempt — something rendered, but the camera was in the sky looking down at tiny trees like a god who'd had a few too many.

The ground wasn't rendering. Turns out PlaneGeometry with a rotation transform is a classic Three.js gotcha — invisible from one side. Switched to a BoxGeometry lying flat. Ground appeared.

Then I said "make Roblox-like people walking around" and Claude just... did. Blocky characters with heads, torsos, arms, legs, walk animations, name tags floating above them, wander AI picking random targets.

Then I said "you can literally just make Roblox" and it built a character customiser, shirt colour picker, username input, fake live chat scrolling in the corner, coins to collect, coloured obby platforms. The whole thing.

// the realisation

None of this is saved as a file anywhere. It's not an artifact. It's not a download. It's just content in a chat message. The same way text renders in a conversation, this 3D game with walking NPCs just... renders. Inline.

I sat there for a second going what the fark.

Then I thought about week 100. If week 2 is this, what does week 100 look like? I don't know. That's the point.

// what this actually means

I run a sheet metal business. I'm not a developer. I learned enough to build my invoicing tools in HTML but I'm not writing Three.js from scratch.

What changed today isn't that I can make games. It's that the gap between "I want to build something" and "a thing exists" just collapsed. The bottleneck used to be skill. Now the bottleneck is imagination and persistence.

See you next week.