You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This would allow for usage patterns where component names have a semantic hierarchy. For example, different enemy types in a game could be tagged with enemy:tank, enemy:bomber and enemy:infantry
It seems relatively straight forward to implement, with only very little performance cost.
Cons:
This might lead to patterns that are kind of considered antipatterns in the ECS world, since you may end up introducing a hierarchy into a system that is explicitly intended to avoid hierarchies.
In Typescript, archetypes are fully typed, and refactoring the typings to fully support this may prove very difficult.
The text was updated successfully, but these errors were encountered:
Summary:
Allowing archetype queries for
foo*
.Pros:
enemy:tank
,enemy:bomber
andenemy:infantry
Cons:
The text was updated successfully, but these errors were encountered: