I'm so used to this type of content being passion projects by junior or amateur developers. The spaghetti piles up but. y'know, that's part of the charm. Surprised to see such meticulous planning and design. I'd offer to help but I'm in the OOP camp, not the functional one. Good luck and where can I buy you a coffee?
Viewing post in Alpha Devlog 2: A Workflow Example, Creating the Guild comments
The spaghetti is why it's nice to think big when designing content. Amateur or not, you'll do whatever necessary to avoid spaghetti if you have to import 100 equipment items.
After the import, a large part is still OOP. The buildings and buildingeffects are objects inheriting from Godot Resource, just like all the UI elements inherit from Godot Control Nodes. Godot as a whole is object oriented with some compositional stuff. The whole "script" part of buildingeffects/moves/items is functional though. In the end I subscribe to WWP (Whatever Works Programming).
Good luck and where can I buy you a coffee?
Thanks! Unfortunately Itch demonitized me, and I'm having some trouble getting Subscribestar running, so for now you can't buy me anything.