How should I integrate Nodes into my design process? about svelto.ecs HOT 2 CLOSED

What I don't get (and that is probably a feature), is that

I can have a Implementor implementing components A,B,C, while at same time a Node map components B,C,D. How exactly svelto make sure an Entity have N components, and that all those components are used by some Node? (or viceversa, the Node say a component that is not implemented by anything)

from svelto.ecs.

The simplest way to see nodes vs components is this:

• Components must be designed as part of an entity. The components, starting from their names, are thought to compose an entity.
• Nodes instead are linked to the engines. Nodes are how engines see entitites.

In this way you totally decouple the design of your entities from the design of your engines.

You build an entity always through the BuildEntity function (see my last article). The BuildEntity needs the list of implementors. You can create implementors on the spot or pass them as monobehaviour, it doesn't matter.

As you realised, components are not objects in Svelto.ECS, they are just interfaces, so an object must implement them. These objects are the implementors.

About the last question, it doesn't matter for you, that's Svelto.ECS magic. If you don't implement some components needed for an Entity, Svelto.ECS will tell you with an exception in run-time.

P.S.: it's better if you use the blog for comments, I will get a notification there

from svelto.ecs.