slight clarification
	
		
			
	
		
	
	
		
			
				
	
				continuous-integration/drone/push Build is passing
				
					Details
				
			
		
	
				
					
				
			
				
	
				continuous-integration/drone/push Build is passing
				
					Details
				
			
		
	
							parent
							
								
									537becd65e
								
							
						
					
					
						commit
						3805de74f4
					
				| 
						 | 
					@ -36,7 +36,7 @@ namespace PongFE.Engines
 | 
				
			||||||
 | 
					
 | 
				
			||||||
*record scratch*
 | 
					*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.
 | 
					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.
 | 
				
			||||||
 | 
					
 | 
				
			||||||
| 
						 | 
					
 | 
				
			||||||
		Loading…
	
		Reference in New Issue