This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
notes:comporg:spring2025:projects:mtb2 [2025/02/27 04:03] – [difficulty of computer player] amelvil2 | notes:comporg:spring2025:projects:mtb2 [2025/02/28 05:03] (current) – [score storage] bdildine | ||
---|---|---|---|
Line 6: | Line 6: | ||
For our purposes, we can check if the ball's x position has exceeded 640 or subceeded 0 | For our purposes, we can check if the ball's x position has exceeded 640 or subceeded 0 | ||
====score storage==== | ====score storage==== | ||
+ | You can store the score and other variables you may use such as x and y positions to locations in memory by defining it, for example: | ||
+ | < | ||
+ | %define LScore | ||
+ | </ | ||
+ | You can then load each score into a register before use so you can use the same score tracking function for both the right and left players scores by loading different scores before calling the function. | ||
====score display==== | ====score display==== | ||
Displaying the player' | Displaying the player' | ||
Line 66: | Line 70: | ||
First we need to get the difference in position between the paddle and the ball. | First we need to get the difference in position between the paddle and the ball. | ||
- | NOTE* we want the center of the paddle to hit the center of the ball, so we must make sure to compensate for the distance between the hotpots and centers of the paddle | + | *NOTE* we want the center of the paddle to hit the center of the ball, so we must make sure to compensate for the distance between the hotpots and centers of the paddle |
This will tell us the direction and magnitude the paddle should move, but we will want to cap the movement speed of the paddle so the bot isn't too good. | This will tell us the direction and magnitude the paddle should move, but we will want to cap the movement speed of the paddle so the bot isn't too good. |