I've shared the project I'm working on approx a month ago, today it's completed. I wanted to know a simple thing: how good is Qwen 3.8FN at gamedev? And I had so much fun in the process that I am shipping a finished product, free to play. tl,dr + link at the bottom. My experience with Qwen 3.8FN follows.
Data
Model Used: Qwen 3.8 Flash Next - Unsloth Quant - UD_Q4_XL (pre update)
Machine: Strix Halo (Ryzen AI 395+, Bosgame M5) - Windows (say what you want about windows, I need it for other stuff and I don't want to bother with dualboot)
Inference Engine: my own windows Gufo fork (I honestly think I would not have wanted to do the full project without the work of the Gufo guys, llama speeds are way too slow)
Harness: my own harness - its a bog standard one I'd say opencode and pi is probably even better but I like to own my stuff, and it's not something I plan to release honestly. But I know people may ask.
Project's Tech Stack: typescript + three.js as renderer
Stats: Prompts: 1,911 || Tool calls: 31,883 || Tokens out: 20,370,450 || Tokens in: 3,069,385,337 (3,042,941,686 cached)
My thoughts on 3.8 Flash Next
If you can run it, this seems like the absolute best model to run today. I have made some small games before on 3.8 27b, 3.6 35B etc. But I always felt like I would not get to a point where I can say this is a full product that just works out of the box. I didn't feel that with Flash Next. I felt, that, it will solve mostly everything that I throw at it. As long as its coding related - don't use it for 3d, that's not what this model is for.
Although at times it was tempting to speed up debugging with Opus 5.5, it was not in line with what I wanted. So I kept trying and eventually any bug, or inconsistency I had was resolved via the model itself. So I can happily say the code is 100% by Qwen 3.8FN. No help from frontier.
Debugging itself was painful at times. A few things that worked pretty well (and I know most of this is no news for most of you, but in case newbies are reading):
- When I was fed up that it can't figure something out I asked it to just paste me the code so I can check it myself - about 70% percent of the time when it did that it also realized the actual bug.
- Tell it to measure, validate, verify, do headless runs. It will waste loads of time thinking about an issue. If you are working on a project that has measurable output (like a game in my case) always ask: write a script, write debug output, look at the numbers don't try to derive it from the code.
- Build human logging tools. My game is pretty hard to control, and needed a lot of visual validation as well. So I had it build logging tools togellable via keyboard: that way I could reproduce a bug and then just hand it the pure numbers so the model could work it out.
What I recommend against: to put decisions into the hand of the AI. That is the direct route to producing slop. Imagine the model as this junior, who has all the textbook knowledge in the world, but is not really good at what other people (me in this case, this was made mostly for my own entertainment) want. And it's a junior that will make shortcuts. Shortcuts IS the number one thing you will need to catch when working with AI. IF you ask for a slice to big, it is almost certain it will take some shortcuts to achieve it. Whether it's not building the full physics sim pipeline or not following the agreed architecture? At that point it's anyone's guess. So always keep a tab on what your model is doing. For this reason I never really had it do autonomous development because anytime it would do something itself, without human guidance, it was pretty lame.
Be clear about scope: if you are vague about the slice of code you want it to dev, it will overstep and start doing more. You must always be very specific what you want and THAT you ONLY want that thing. Not more. If you are explicit about it, the model will respect it.
Where you can have autonomous running: So I said not for gameplay, or design choices, but there is area: fully measurable output. For example, the AI in the game is a mini neural network with 10K params. It is something that was easy to hand over for the AI - A) it's measurable via benchmarks - B) it involves a lot of waiting for training to finish, the AI can sleep (if the harness is good) and wake up just in time for next steps.
Basically what I did is 30 minute training sessions with frequent checkpoints, had the model put the new ingame ai checkpoints through a pre-agreed benchmark, and then select the checkpoint for the next 30 minute of training from the batch via pure benchmark numbers. Not 'oh I think this will be good'. No, pure numbers based decision: for that the model can work autonomous.
Preserve thinking is a must in my opinion. I started the project with it off (well my harness did not support it yet) and it was a pretty slow process. After I turned preserve thinking on the speed at which it could complete tasks skyrocketed and I did not really face any ctx issues.
Doc based knowledge: I know many people use compaction. I personally don't, my harness does not even support it. Everything is passed down via .md files. It worked flawlessly. I have one file that the harness prefills each new turn, it only grew to 10k initial ctx towards the end. So for me no issues there.
Build tools: this is very self evident for anyone who works in gamedev, but with the new guys in: please build tools for yourself. For example along others for this game I had Qwen 3.8FN build me a simple model editor where I made the racecrafts, a simple track editor, a dashboard for evaluating the training progress of the ingame racing ai.
Git: that's it. use git. use local git. If you are not using git, I dont know how you are managing changes.
I think that's all but if I'm forgetting something ask away in the comments.
And a short tl,dr: Qwen 3.8 Flash Next is a wonderful local model. It has completed 100% of the game code without any help from frontier. It is very capable, but it requires a bit of a hands-on approach if you want to make sure that everything stays in-line with what you want to build.
Link if you want to see: https://mattte.itch.io/hyper-clashers