From f6a81d6db118430ab7e6aa5e364171a6ecb2c455 Mon Sep 17 00:00:00 2001 From: Evan Hemsley Date: Tue, 21 Jul 2020 15:20:25 -0700 Subject: [PATCH] clarify some terms --- content/pong/ball/bouncing/design.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/pong/ball/bouncing/design.md b/content/pong/ball/bouncing/design.md index 3c50118..3036560 100644 --- a/content/pong/ball/bouncing/design.md +++ b/content/pong/ball/bouncing/design.md @@ -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: