-
Notifications
You must be signed in to change notification settings - Fork 231
Update on input fixes #61
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
…; ple frame limiting;
added tests for pong and raycastmaze
Parameter verification for Pong and RaycastMaze
…d and updated tests
Changed pong collision to use pygame built-in
Test Update __init__.py
Update __init__.py
Thank you for your work on this. It looks great. I left a few comments. |
@@ -261,7 +263,7 @@ def step(self, dt): | |||
self.bad_creep.update(ndx, ndy, dt) | |||
self.good_creep.update(dt) | |||
|
|||
self.player.draw(self.screen) | |||
#self.player.draw(self.screen) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why is this commented out?
is_pad_hit = True | ||
|
||
#then we test the cpu, much cleaner! | ||
if pygame.sprite.collide_rect(self, cpuPlayer): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you verify that this does not slow down the step speed? I believe using this function was slower.
No description provided.