What actually happens when you press make
No cherry-picked screenshots, no marketing copy — just the actual sentence we typed into the homepage box, what BIT said back, and the game that came out. This is one build, unedited, exactly as it happened.
The prompt was one of our own homepage placeholder examples, typed verbatim:
a racing game where the cars are shopping carts
BIT read it, picked an engine (BIT Code 3D, the raw-code Babylon.js path — it decides this itself, no picker shown up front), and narrated back what it was about to build before writing a line of code:
"A shopping-cart Grand Prix — you're pushing a rickety supermarket cart flat-out around a curvy asphalt loop, weaving past three rival carts while the clock ticks down. Off the asphalt you bog down in the grass, so hug the racing line through the bends. Complete all the laps before time runs out to win; run the clock to zero and it's over. Once you tap to start, hold W to build speed, steer with A/D (or arrows), and mash Space for a boost burst down the straights — the first sweeping left-hander comes up fast, so ease off the throttle before you plow into the grass."
About four minutes later — BIT streams its reasoning and the code live, so you watch it happen rather than stare at a spinner — the build finished: Cart Grand Prix, a real racing game, 21 KB of generated game code, saved to the account as v1. Not a mockup. We drove it: WASD steering, a working HUD (lap counter, position, time, speed), three AI-driven rival carts actually racing around the same track, a checkered start/finish line, grass that visibly slows you down exactly like the narration promised. First try, no edits, no re-rolling the prompt.
That's the honest version of "press make": you get a real playable game, BIT tells you what it's building before it builds it, and what it says matches what you get. We're publishing this kind of walkthrough because screenshots alone don't prove that — the actual prompt and the actual narration do.
— the ARCADEBOX.AI team