A playable ink-wash game made solo in 24 hours—and the comments are already arguing over the word 'solo'

toby posted a game video on X with a very short caption: Opus 5.5 is insanely powerful. According to him, he built a completely original, playable game solo in 24 hours. The tech stack he listed was long: Opus 5.5, Flux 3 Max, GPT Image, Tripo, Blender, and Three.js.

After the video went up, the comments split into a few camps. Some asked whether it looked a bit like Tomb Raider. toby replied that it was an original ink-wash-style game, with the protagonist running and jumping around ancient-style cliffs and temples, and that the style was quite different. Others focused on scene details, saying the pine tree by the cliff had a lot of character.

Another camp picked apart the word 'solo.' User 飞身踢抬杠 pushed back: listing Opus 5.5, Flux 3 Max, GPT Image, Tripo, Blender, and Three.js all at once—how is that solo? That's clearly bringing an AI team to a team fight. He added that getting it running in 24 hours is impressive, but a version that's actually playable long-term, without a pile of bugs and broken balance, would probably take several more 24-hour sessions of polish. As a demo, though, this level of completion is already very strong.

That pushback isn't harsh. There's a gap between a version that runs after 24 hours and a game that can be played long-term after 24 hours: level pacing, balancing, interaction feedback, sound effects, performance, and a whole lot of testing all sit in between. User ccod put it more bluntly: 'You can build a playable game from scratch in 24 hours; over here, I'm still reasoning with error messages after 24 hours.'

One more reply is worth reading. User VZA THE GREAT said that the key to making a playable game solo in 24 hours isn't how powerful the model is, but breaking art, code, and sound effects into small chunks that can run end-to-end in one pass. He had tried a similar workflow himself, and the places he got stuck were mostly because the requirements weren't clear; the model failing to write something was secondary. Make the game small and playable first, then gradually add content—that's the path that goes further.

That's also where this tweet's real value lies. Opus 5.5 won't automatically hand you a game design. What it lowers is the cost of trial and error, letting one person play multiple roles at once: programmer, artist, level designer, and sound designer. But the scope has to be set by a person, the workflow has to be broken down by a person, and when to stop has to be judged by a person.

A few unanswered questions are also scattered through the comments: What exactly is Flux 3 Max responsible for here? How were the character model and animations made to look natural? How long did the scene scripting take? Will it be open source? Some people ask; some wait.

It's a fact that it can run in 24 hours. After those 24 hours, the game has only just begun.

Original post: https://x.com/jdyu477723/status/2117815185545335031