Blog Article
Fable 5.2 vs Opus 5.5 with Ultracode on Extra High: Which One Built the Better Game?
I gave Fable 5.2 and Opus 5.5 the same single prompt with Ultracode on extra high effort and played both paintball games side by side. Fable won on gameplay feel
I put Fable 5.2 head-to-head with Opus 5.5 in an Ultracode showdown on extra high effort. One build, one prompt, no back and forth.
The short answer: Fable 5.2 built the game that feels better to play. Opus 5.5 built the one I liked looking at a little more. And given how expensive Fable 5.2 is, I would still lean Opus 5.5.
Let me show you how I got there.
The test: one prompt, two models
I used my favorite prompt from recent tests: a first-person shooter paintball video game that feels very realistic.
The setup was simple:
- The Claude desktop app
- Two separate projects, both starting from an empty folder: "Fable Showdown" and "Opus Showdown"
- Ultracode enabled on extra high for both
- The same exact prompt sent to each model
I added one line to the prompt before sending it:
> Please only work out of this directory. Do not go look at other directories in the parent directory that this one lives in. No cross-contamination between results.
If you run your own side-by-side tests, copy that line. Two models working in neighboring folders can peek at each other's work, and then you're not comparing anything.
I started Fable first, so it had a small head start. I wasn't focused on time for this one, so I didn't mind.
20 minutes of thinking with nothing written
The first surprise came early. Both models sat in a thinking state for about 20 minutes with nothing written.
I wondered if something was going on with Anthropic's servers. I'm not sure, and I never confirmed it. Then Fable started building, and Opus followed suit about 1 minute later.
So if you kick off an Ultracode run on extra high and it looks stuck, give it time. Mine looked exactly like that before any code showed up.
Opus finished first, but not by much
I was expecting this test to take quite a few hours. It didn't.
I interrupted my time lapse at 1 hour, 17 minutes, 45 seconds [02:02]. Fable 5.2 was still working, and to me it looked like it was mainly still focused on the engine. Opus 5.5 was already done.
I didn't preview the Opus build early. I wanted to wait and play them side by side.
Then Fable wrapped up about 8 minutes after Opus. I was shocked this didn't take multiple hours. Maybe I could have been more thorough with my prompt, but both models delivered a playable game within 10 minutes of each other.
Playing the Opus 5.5 build
First impression: the bunkers looked interesting. I went into settings, turned on invert mouse, and played a match.
What I found:
- It was a slow start
- The physics felt off to me
- The sprint wasn't fast enough
- The paintball gun didn't switch hands when I leaned left
There was one visual effect I thought was very cool, and overall the game feels very realistic. The look was there. The feel wasn't quite there.
Playing the Fable 5.2 build
I checked the controls, set invert look in settings, and hit play match [04:39].
My reaction was immediate: I like the feel of this gameplay better.
A texture caught my eye right away. Then I found a fast forward option that I never asked for. That's awesome, right? A small extra the model decided to add on its own.
The realistic detail both models missed
Now, if you've ever played paintball, you know this one. When you're shooting left or right out of a bunker, the gun repositions to that side of your body.
Neither model did it on this run.
What makes that interesting is my earlier every-effort-level test. In that one, both of these models nailed that detail on the higher reasoning levels. I chose extra high here, so my assumption was that they'd nail it again. Both of them failed on that minor little realistic detail.
Keep in mind, my prompt could have been far more detailed. I kept it simple on purpose. I wanted to test from the perspective of a semi-beginner. We're not game developers. We don't know how these gaming engines are built or how to build them ourselves. We trust the models to do it for us.
So the takeaway for me is this: a higher effort setting doesn't guarantee the small stuff. If a detail matters to you, write it into the prompt.
The verdict: Fable for feel, Opus for looks
Here's how I scored it:
- Gameplay: Fable 5.2. It feels more fluid, natural, and realistic, for sure.
- Visuals: Opus 5.5. I liked some of the visuals a little better, and I liked the color palette it chose.
I wasn't focused on the outside world in either game. If I wanted to, I could tell both models to place us on the Las Vegas strip and see how they do. That's room for improvement on the next prompt.
What it cost, and why I still lean Opus 5.5
After the run, my usage read 67% of all models and 87% of Fable. If my math is correct, this test took 4 to 5% of my weekly Fable allowance.
That's the deciding factor for me. Both models finished within 10 minutes of each other, and the results were close enough that each one won a category. Given how expensive Fable 5.2 is, I would still lean Opus 5.5, with some minor tweaks to my prompt and a bit of back and forth.
My decision framework from this test:
- If gameplay feel on the first shot matters most, Fable 5.2 had the edge
- If you're watching your usage and you're willing to iterate, Opus 5.5 gets you close for less
One prompt means one prompt
Let me be clear about how I run these. These were one-shots.
I'm not going to sugarcoat the results, go back and forth five to 10 times, and then tell you it was one prompt. That's not what I do around here. What you see in the video is what one prompt produced from each model.
That also means your results may look different with a more detailed prompt. Mine was simple by design.
Your turn
Which one do you think won this Ultracode showdown on extra high? Watch both builds in action and tell me in the comments.
And if there's a specific type of showdown you want me to record, drop a comment with exactly what you're interested in. I'll add it to my queue.
Watch the full test here: https://www.youtube.com/watch?v=NnlVDQbydG8
Watch the full walkthrough on YouTube.
Watch on YouTube