Hey, awesome job on your first game for this challenge !
At least, you've got a loop under 3 hours, my first entry a few years ago took more than the restricted deadline and wasn't that polished at all :' D.
Here are a few structural tips for your next runs:
- Practice with your engine until it's second nature.
It builds muscle memory, and you'll accumulate handy code snippets or base architectures you can deploy instantly (just don't overdo it, the goal isn't to pre-make the game, but to skip the boring setup phase).
- Planning time is free, use it! You have unlimited time before starting the clock to structure your ideas.
Don't wing it during those 3 hours. Map out your core gameplay loop, state machine, or main classes on paper first.
- Think about the "Juice" early...
A basic prototype with good camera tweens, responsive controls, a solid shader, and synchronized audio will always feel better than a complex game that feels static.
- ... so leave room for audio and VFX.
Plan them out during your brainstorming: When do they trigger? At what volume? Having a tiny impact sound or a subtle screenshake completely changes how the player perceives your game's polish.
- The 15-minute rule: Try to code your core mechanic in 2 hours, spend 45 minutes on audio/VFX/UI, and lock down the last 15 minutes strictly for building, testing, and uploading.
In short: practice, scope down, plan... and if it feels too complicated, simplify it immediately!
Oh, et passe le bonjour aux profs de l'HEAJ ; ) !