Game Jamming, Vibe Coding

Can be frustrating AF if you like to don't understand why the ai keeps wasting your API credits like pouring gasoline on a fire as it loops into fixing one things and breaking another, fixing that and breaking another, fixing that and breaking the original and something else, loop for as long as your patience and pocketbook can stomach.

J/k

I learned a lot from this experience. There's no way my game will be done and ready to submit to the game jam unless it really did get the deadline extended. But doesn't matter either. Gonna finish this game. I'm having too much fun learning how to make it.

Windsurf and Cursor and Roo Code kinda broke the v1 that manus made for me. Mind you i had a decent hand in that since my lack of expertise created half the problems when asking them to fix problems i didn't understand the cause of and mispoke rampantly.

So I took what I learned from round one, and crafted a new prompt with a project requirements built into the prompt, and gave that to manus to make a v2. That version exceeded context limits before completing everything, I learned to not ask it to test the game and view it in the browser as that wastes a lot of context. If i repeat this again with manus i know how to improve the prompt thanks to that.

But it did pretty good, built a decent scaffold, and now with a little help from Claude 3.7/Cursor Agent I have a semi-working v2 with a functional deckbuilder you can access from the new Wizard's Study room/screen you go to between duels.

The Deckbuilder:

The Wizard's Study:

I plan to add more art later on. The aim now is functional game. Then we can make it polished and shiny.