GodotShaderCollection VS godot-tactical-rpg

Github for shader - https://github.com/alfredbaudisch/GodotShaderCollection

I based the current logic on godot-tactical-rpg and am modifying heartbeast's tutorial on turn managers. From what I understand, act would be taking the argument for delta from something like _fixed_process(delta) or _process(delta), however in my case, I don't see how that would apply considering that battle basically acts as the turn and phase manager, and I'd rather not have _process() inside of battle.gd running when it's the enemy's turn as I don't see why we'd need to check those actions running every frame.

The setup is slightly different. The node the script is attached to is not the parent of ui_control, but a sibling node. I'm building my project with this engine: https://github.com/ramaureirac/godot-tactical-rpg. So the setup for a scene looks like this: https://i.imgur.com/pEl3eBu.png. The script from the OP is attached to the "Player" node, while ui_control refers to the "PlayerController" node. So the path to ui_control is given to "Player" by the "Level" node. This is also why I use the get_combat_act() function to locate the button nodes.