ReadyM.SDK.Client.Entities
Structs
Every entity carrying all 4 shapes, without an archetype that names them.
EntityQuery<T1, T2, T3, T4, T5, T6>
Every entity carrying all 6 shapes, without an archetype that names them.
EntityQuery<T1, T2, T3, T4, T5>
Every entity carrying all 5 shapes, without an archetype that names them.
Every entity carrying all 3 shapes, without an archetype that names them.
Every entity carrying all 2 shapes, without an archetype that names them.
Every entity of a shape. How it is walked is decided for you: a shape whose components are all known at compile time is walked by chunk, and anything else by identity. The choice is made by overload resolution, so this type has no GetEnumerator of its own and a foreach binds one of the extensions instead. A netstandard2.0 client has no chunk path at all, so every query there walks identities.
Every entity a scope holds that carries all 4 shapes. Walked by identity: a scope's entities are scattered through the archetypes they belong to, so there are no chunks to hand back.
ScopedQuery<T1, T2, T3, T4, T5, T6>
Every entity a scope holds that carries all 6 shapes. Walked by identity: a scope's entities are scattered through the archetypes they belong to, so there are no chunks to hand back.
ScopedQuery<T1, T2, T3, T4, T5>
Every entity a scope holds that carries all 5 shapes. Walked by identity: a scope's entities are scattered through the archetypes they belong to, so there are no chunks to hand back.
Every entity a scope holds that carries all 3 shapes. Walked by identity: a scope's entities are scattered through the archetypes they belong to, so there are no chunks to hand back.
Every entity a scope holds that carries all 2 shapes. Walked by identity: a scope's entities are scattered through the archetypes they belong to, so there are no chunks to hand back.
Every entity a scope holds that carries the shape. Walked by identity: a scope's entities are scattered through the archetypes they belong to, so there are no chunks to hand back.
Interfaces
The entities this client can see: query, look up, create and delete them.