three genders in a wenchcoat

In practice the engine is flexible enough with the node and signal system that an ECS (or even just reusable components) as a paradigm is possible, but may not have the performance of one.

This seems to be one of the only written resources I could find, but some of the GDScript will likely be out of date for Godot 4.

https://www.gdquest.com/tutorial/godot/design-patterns/entity-component-system/

There is a more up to date video resource for Godot 4; I haven't gone into the further videos of this series but the first one made the concept click for me to attempt the rest myself.

https://www.youtube.com/watch?v=zUeLesdL7lE

Of course these are the lowest friction options to hit the ground running, there is also diving into the Godot Server Architecture (barely documented) to write systems outside of the base engine.

If you want Unity-like ECS stuff but without shitty devs, maybe check out Flax. https://github.com/FlaxEngine/FlaxEngine

It's not too difficult from what I messed around with. Has C# support but more importantly has really easy C++ support. Like, I didn't feel like I was fighting the engine to get C++ stuff working. It's also less distinctly corporatized than Unity, though it's not proper FOSS. So there's still licensing fees, but they're definitely not bad. And only kick in after $250,000 in revenue at this point.

I enjoy using Godot for my own projects, I find it very easy to iterate with. However, things like multiple inheritance may be more difficult to work with (unless you just have multiple sub-nodes with your various child classes operating on your main node or something), so if that's a requirement for you, do consider checking Flax.