Automatic observer and system registration #18
Labels
A-Control-Flow
Control flow systems like behavior trees
C-Feature
A new feature, making something new possible
Milestone
Its very difficult to remember to register each action for a given scene, and its also hard to know which default ones are registered by the
LifecyclePlugin
We should add typeids to a hashset on register, and check that set on add with lifecycle hook. If its missing id like this to panic by default, with options for warning or ignore. I cant think of a use-case where its a desired configuration.
The text was updated successfully, but these errors were encountered: