From 3805de74f48135e18bf74288828cc9ab8bb776c2 Mon Sep 17 00:00:00 2001 From: Evan Hemsley Date: Tue, 21 Jul 2020 15:05:19 -0700 Subject: [PATCH] slight clarification --- content/pong/move_paddle/input_handling.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/pong/move_paddle/input_handling.md b/content/pong/move_paddle/input_handling.md index 4ae04ee..5ccafd7 100644 --- a/content/pong/move_paddle/input_handling.md +++ b/content/pong/move_paddle/input_handling.md @@ -36,7 +36,7 @@ namespace PongFE.Engines *record scratch* -Uh oh. **SendMessage** emits a message, as the name suggests, and we can use it to send out a MotionMessage. But it needs a reference to our paddle entity. +Uh oh. **SendMessage** emits a message, as the name suggests, and we can use it to send out a MotionMessage. But our new MotionMessage needs a reference to our paddle entity. At this point, you might be tempted to attach our paddle entity as a property on InputEngine. This would be a *terrible mistake*. We *absolutely never* want to have our game state directly attached to the state of an Engine.