Skip to main content

On Sale: GamesAssetsToolsTabletopComics
Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines
(1 edit)

This was the third Godot Wild Jam in a row that Musket and I worked on together. I think we were able to divide up development work quite easily. I spent around 9-10 hours each day, so maybe that qualifies as crunching? I didn’t feel pressured–certainly I’ve felt more pressure in past jams, at least. You can read about the dev process we use if you want.

Of course, it depends on experience level, but for me the only 2 challenging bits of coding were how to align collision shapes with the various control nodes at runtime, and how to use an object pool for visual effects. Without vfx object pooling, I saw a lot of the fun explosions being missed and that was just unacceptable. I may have missed some other obvious fix, but that’s the nice thing about tight deadlines–you use the first thing you find that works and don’t worry about it too much. :D

UPDATE: thinking about it, 3 days is a better description–Friday afternoon/evening, Saturday, Sunday until the deadline.

Looking forward to reading more about your team's dev process and checking out Hamsterwell! :)

Game dev is a new hobby, for me, although I've been adjacent to it for some time. For aligning the collisions, are they instantiated dynamically and you're doing a calculation on the viewport size, or are they hard coded?

(1 edit) (+1)

I’ll write up the whole destructible UI approach in a day or two as a dev log.

UPDATE: Here’s a dev log with more detail – https://hatmix.itch.io/blasteroids/devlog/770116/how-i-made-destructible-ui-for-blasteroids