Pending GS_Interaction v2 implementation.
Image showing the Reactor component, as seen in the Entity Inspector.
Pulse Reactor Overview
Functionality
All Reactor
Receives a pulse event and starts processing.
If incoming entity is a “pulse” tag.
Based on “canBe X“ evaluation, each valid type then checks for granular pulse tags:
- Impulse
- Hit
- Burned
- etc.
Unique Reactors
Perhaps we make custom clusters of Pulse processing based on common types:
- Unit
- Item
- Dynamic Object
- Field
These would still use canBe X booleans to enable and disable specific pulses, but would allow for less logic in any given Reactor.
Single Reactors
Would be a performance consideration. With Pulsors also being independent components, it may lead to quite a lot of components. But is an option.