tutorials/best_practices/node_alternatives

[giscus[bot]]

tutorials/best_practices/node_alternatives

Nodes are cheap to produce, but even they have their limits. A project may have tens of thousands of nodes all doing things. The more complex their behavior though, the larger the strain each one a...

https://docs.godotengine.org/en/stable/tutorials/best_practices/node_alternatives.html

[buanzo]

Use Nodes for visual and interaction purposes but check the performance as your node count grows. Replace data-centric nodes with Object or RefCounted where possible.. THen, Resources for data that benefits from serialization, like settings, configurations, or reusable assets, help with performance and keep the scene tree clean.

[badunius]

Never use Custom Resources for anything that isn't supposed to be shared between the instances. Unless you're going out of your way to make sure they are unique, they won't be. And wen they are, you're no longer benefiting from them being accessible from the editor.