How to play :

WASD + J or arrow keys + J for movement and backspace to restart the level.

It's 4 am, EC, and as I write this, I can't stop but think about how much I was able to accomplish after spending 5 days using godot. Most of the days were spent trying things and seeing what and how things transition from my 3 years using the forever lovely Gamemaker Studio. I joined the jam late, 4 days late, and decided it was now or never to take action and learn some godot. The community helped me out tremendously, and put up with my barrage of questions. They were incredibly welcoming and very very friendly.

What went right :

I was able to breeze through the UI of the engine. It might seem like a lot at first, but trust me, once you get used to it, it is actually very easy to navigate. I was able to get the basics of my game in like 1 hour, and then after that I was working on mechanics, an enemy, and some destructible objects. Everything went very smooth there. I then made some art, and continued to work. Setting up the art assets was a bit tedious, but only because of my lack of experience with the engine. I then realized how much faster I was able to just throw assets into folders and have godot import them instantly. If something was changed, Godot would just take it, and do the dirty work for me.

What went wrong:

man, going into a new engine means you have to find the way you need to walk in order to apply previous knowledge from any engines you might come from. i faced a shit ton of problems towards the end. Signals I had not setup properly, or that just were giving me debugging error messages, but whatever that was referencing was still working.  I ran into the issue of the engine not recognizing my MP3 files and the game ended up havin no background music.

There's no HUD because I had not understood labels at the time I was juggling everything.