pixel_push_football_godot VS turbofat

I found that same thread! I read through about 10-20 different similar threads hoping to find guidance, because creating and managing a bunch of one-shot timers is sort of tedious. I ended up writing a TimerGroup script where I can still create one-shot timers, but have the option to clean them up with timer_group.clear() if something unusual happens. And instead of calling await or yield I just hook up listeners.

There are many well-designed and clever uses of get_parent() and get_node() other than your naive approach of arbitrarily navigating the scene tree to create brittle code. Here's a script I wrote so that its parent button can be activated with more than one shortcut key (e.g opening a menu with either the 'back' or 'menu' button). I'm curious how you'd handle this scenario in a way that produces concise reusable code?

It's also open source if you'd like to pry into the source code or play it yourself. It's made in Godot 3.5.1 but I'd love to upgrade it to Godot 4 to play with all the new toys -- particularly CanvasGroups which will be a monumental improvement for my 2D rendering!

Here's my current code, it is provided a list of fonts and will apply the largest font which can fit all of the text. However, calculating "will this font fit" of course cares about the difference between a font taking up 12 pixels of space and 15 pixels of space, so I need that "+3" constant. Maybe there is a better solution!

sfx-deconflicter.gd

Overall I thought updating all of my code would take forever but I ended up doing it in a little over an hour. There's a little less visual clutter in my scenes now, since I don't need as many nodes. Here is the full change log if you really want to dig into the weeds! Thanks for reading.

When my game loads, it runs this ResourceCache script

https://www.youtube.com/watch?v=K9FBpJ2Ypb4 here's the tutorial I followed, I made a custom mask which resembles the blocks from my game.

However, if this is a game you're planning on to work on for a few months, publish on itch.io or Steam, or make money from -- then I recommend recording the licenses for all assets in your game, and keeping them in one place. For example, I have a big asset-license.txt file which tells me, for example:

The game is open source, and the source code is available here if you want to poke around. The offending scene is Overworld.tscn, specifically the viewports near the top of the scene.