🤑 Indie game store🙌 Free games😂 Fun games😨 Horror games
👷 Game development🎨 Assets📚 Comics
🎉 Sales🎁 Bundles
A jam entry

Procedural InvadersView game page »

3d Space Invaders with procedurally generated enemies.
Submitted by michalbe with 1 day, 3 hours before the deadline

Play game

Visit Procedural Invaders's game page

Results

CriteriaRankScore*Raw Score
Theme interpretation#323.6673.667
Graphics#673.2503.250
Innovation#732.7502.750
Overall#1142.5832.583
Gameplay#1352.0832.083
Audio#1611.2501.250

Ranked from 12 ratings. Score is adjusted from raw score by the median number of ratings per game in the jam.

GitHub repository
https://github.com/michalbe/procedural-invaders

Leave a comment

Log in with your itch.io account to leave a comment.

Comments

Submitted

This has some real performance issues, but otherwise very cool idea. Enemy destruction effect look awesome.

Submitted

Nicely done.

There's actually a sort of beautiful irony to the game slowing down as you clear enemies, since it's the exact opposite of the original game which sped up as enemies got removed from the screen because it didn't have to draw as much stuff.

I vote for procedural Galaga next!

Submitted

Performance issues aside, I really like this. Love the effect when an enemy is destroyed. Procedural generation keeps it visually interesting. If you keep working on this, it'd be interesting to have enemy behavior depend on the generated pieces (timing and flight path for example) to keep the gameplay from being repetitive as well.

Submitted

Almost crashed my computer as the debris piled up, you seriously need to fix this if you want anyone to give you a good score. I suspect each dead alien piece is an object, so the more you blow up, the more objects it has to model, which eventually kills the computer. Besides this, you have the kernel of an alright game.

Submitted(+1)

On the browser version it gets unplayable when there are too many enemy pieces in the ground.

Maybe you can have a decay period so that they disappear.

Developer

Hey, thanks for the comment. This is probably caused by some memory leaks in the physics engine (I use GoblinJS here), because I actually am removing parts of destroyed ships from the physic calculations after 3 seconds (they're still being rendered, but this isn't a problem here).