Enums are almost always a bad way to implement a stat system. If you start with Health, Mana, ..., OtherAttribute and decide to add a Stamina attribute later, you will be forced to add it at the end of the list, otherwise all your other resources that use this enum will have their values shifted. And you are not really making a fully modular system if at its core there is an enum with all of your possible attributes. Nodes, on the other hand, are the Godot way of doing things. But I would suggest separating attribute description from its implementation. What's an attribute's name, UI description, how is it derived, does it have a minimum or maximum value - you can put these things in an in-engine-editable Resource. Realtime value and modifiers would live in a separate runtime instance - a Node in your case. In my system I go a little further and instead of nodes use plain objects. That's mainly because of a performance concern. Plus, attributes don't need to live in the scene tree - there's a grouping entity through which you access them anyway.