Sethian (@theSethian) “GPT-5.6 Sol Ultra built a playable Geometry Dash-style game in one prompt. Promp” — TopicDigg

GPT-5.6 Sol Ultra built a playable Geometry Dash-style game in one prompt. Prompt Potato keeps raising the difficulty for 12 minutes: Geometry Dash, Doom, then Rocket League. At 00:18, the first build arrives with five difficulty levels, different movement forms, gravity changes, portals, music for each level, an icon kit, and a progress counter. It looks polished, but the hardest level has a real input problem. Jumps don't always register after landing, so he spends 700 attempts on it before enabling invincibility to see the ending. At 04:14, Sol builds the Doom-style game. The first enemy deletes the player in seconds because several rifle attacks stack into one burst. Sol finds the damage issue and repairs it. The next run has usable weapons, a keycard, multiple enemy types, and a full boss fight. Rocket League is the hardest test: > 1v1 and 3v3 modes > a garage with car colors and boost trails > goal replays > air rolls, aerials, flips, and demolitions > bots that can save shots and also park themselves on the wall At 08:59, one correction fixes the air roll camera and flips, adds free play, and gets the bots moving again. Their intelligence still needs work, but the aerial controls and even a tornado flick work. This is the kind of job that can justify Sol: a long build with several systems, visual judgment, debugging, and multiple rounds of repair. The expensive mistake is letting a demo like this choose the model for every other task. Sol costs five times as much as Luna: > Sol: $5 input / $30 output per million tokens > Terra: $2.50 input / $15 output > Luna: $1 input / $6 output The article gives each tier a specific job: > Luna for classification, extraction, tagging, and simple summaries > Terra for chat, RAG, drafting, code review, and standard agent steps > Sol for long builds and the cases where Terra fails your eval > Ultra only when parallel agents earn the extra token spend > retry on the next tier only after validation fails > log the model and token count on every call Sol earned its place on these game builds, and it doesn't need to classify the support ticket.