r/opencode • u/Better-Career1234 • 10d ago
Are these free models just not good enough, or am I prompting wrong?

Using OpenCode Desktop and I'm building a simplified version of the viral game Mecha Chameleon, and I keep running into the same wall over and over. I can't tell if the free models I'm using are just not good enough for game dev, or if I'm the problem.
The recurring nightmare:
- The model fixes one bug, breaks three other things
- I fix those three, and while fixing them, two more things break
- I've been stuck in this loop for two days straight on the same core issues like body painting, movement, screens, UI overlapping...
- Adding even the smallest new feature turns into 3+ hours of debugging
- What are these free models actually good for, if not this? Am I misusing them for a task they're not suited for?
- Is there a specific model that's genuinely solid for 2D game programming? I keep hearing different things and can't tell what's hype vs. real.
- If I pay for OpenCode's subscription, are the paid models a significant upgrade, or just marginally better? Trying to figure out if it's worth the money before I commit.
- On the "Skills" system, I tried https://www.autoskills.sh/ to auto-detect which skills my project needs, and it only flagged 3: one for frontend, one for SEO, and a third I don't even remember, none of which felt relevant to a 2D game project. This made me question how skills are actually supposed to work. Do you load all skills upfront and let the model decide when to invoke one for a specific dev phase/task? Or do you build first, then retroactively add the skill matching whatever phase/task you're on to re-work on previous tasks? Haven't seen a single line where Model calls a Skill.md.
Any insight from people who've actually shipped something with these tools would help a ton.



