This looks good, gonna try it out right now!

I later found out that this track is not in the public domain, despite being a million years old.

I'm guessing that's part of the reason for this calming banana bulshit.

[2/2]

Retro City Rampage DX

(5/x) I fell that I will need to use pre-determined brick placement in the final product, or at least come up with various pre-determined brick sets.

I might also offer the choice between "scripted" and "random" levels.

That's all I have to say for now. Have a good day!

(4/x) how to adjust the target score and performance evaluation rules as the player reaches higher levels in the game.

Another point I'd like to bring up is the way the levels are populated with bricks. At the moment, the numbers and operands on the bricks are chosen at random but

(3/x) When the player finishes a round (or a "try") their performance is evaluated based not on how much they scored but on how close their score is to the target score.

Finding a way to evaluate the performance in a way that feel fair was a bit of an issue and I will need some more time to gauge

(2/x) and this helped a lot but it's still not perfect.

Getting the ball to bounce off the paddles with various angles and making that feel intuitive was also a bit of an issue, I might need to re-do the whole thing and find a different way to calculate at what angle it should bounce.

(1/x) I have encountered numerous challenges with that game so far.

One of the biggest problems I had to deal (still do) with is the physics.

The ball sometimes goes through the bricks and sometimes it goes through the walls.

I played around with cooldowns and "await get_tree().process_frame"

That was the first of my projects that I migrated, let's just say I still have a few things to learn about git. The process was smoother and cleaner with my other projects.