It took me too long trying to figure out which state was incorrect until I notice it was only happening in the score setting, that the old save had no scores, and both the states in the score ui and play was the same. My silly mine kept blocking out the save_ part of the state. Issue about old stuff

player (or the general view) to detect valid water spots to keep track of and manage the water objects. It would be a pooling system, but also extra work so I may use fish nodes unless it is needed. The endless map the only thing I worry about since that could be a lot of nodes being added/removed.

projects, the signature of the events would likely be the same compare to the state. Inherence would solve that if merging, but I may not have a base version of since it is redundant. Really they are easy to make so there no need to transfer them and if they are transferred, then they can be edited.

Though with both Godot project I need to decide if events and states should stay separate or I should merge them since they are related (events trigger a change in the state or notify a change in state) and I do not have to deal with GMs. I mean another reason to split them would be in other

connecting them, and then testing to make sure I cover all the logic so I can delete the old stuff. Also I need to try to get use to the file organization since it split bases, plugins, and framework like stuff from the implementation of them, but not everything been following that rule.

assets and something I would not talk or share here while the other is the old one I still need to clean up and then add content. I want to clean it up, but I get overwhelmed by all the old stuff I need to remove that could break some ancient logic. Mostly it is moving things to abstract objects,

'The one who feast upon the remains of the old ones. Who live between the cracks reality to stay hidden from HIM, to ever oppose fate declared by THEM'. -one of the hags describing their deity or something.

(Also this is more about foss games made by a solo devs who are not collecting any money from their labor, but I feel it would apply to free games that do not make a profit. The game is for them or their targeted players, not necessary for some random with high standards).

add more gameplay stuff to it this month. It a mix of me not knowing what to give as a gift and me being in the mood to mess with html and js again.

and independent feature while the other one contain the actual game (dependent?) content organized loosely base on how the runtime scene tree looked. Some files seems like they do not follow this rule, but I would need to clean up things to be sure.

the code relocated. A lot of the others was being update or just need a ref change from the autoload to a shared resource. Meow but there still a lot of clean up. So much files of old attempts of organizing the logic flow. Also I split the directory up into two major branches. One for bases

depends on the global scope too much and gave a little too much power to resources in some cases. I wanted to use groups to tell the gui to queue up a message, but the part that was call it was a resource because it contain ref to a node to manage. Luckly i think this is the only one that need