clarify some terms
continuous-integration/drone/push Build is passing
Details
continuous-integration/drone/push Build is passing
Details
parent
c0c369aee7
commit
f6a81d6db1
|
@ -38,7 +38,7 @@ We already have MotionMessages. Let's keep those, but redirect them slightly. We
|
|||
|
||||
Let's have the MotionEngine consolidate all the MotionMessages per-component, and send out an UpdatePositionMessage with that final delta after a sweep check.
|
||||
|
||||
Finally, a CollisionDispatchEngine figures out what two kinds of objects collided and emits a Message in response. We can then implement various collision resolution Engines that read each of those kinds of Messages. For example, a ScoreEngine would track **CanScore** Actors and **CanBeUsedToScore** Receivers, and perform behavior based on attached **Responses**, like an **IncreaseScoreResponseComponent**.
|
||||
Finally, a CollisionEngine figures out what two kinds of objects collided and emits a Message in response. We can then implement various collision resolution Engines that read each of those kinds of Messages. For example, a ScoreEngine would receive **ScoreMessages**, and perform behavior based on attached **Responses**, like an **IncreaseScoreResponseComponent**.
|
||||
|
||||
We can visualize the flow of data like so:
|
||||
|
||||
|
|
Loading…
Reference in New Issue