Prevent the snake from going back on itself#3
Open
ali1234 wants to merge 1 commit into32blit:mainfrom
Open
Conversation
There are two ways that could happen: If you are going up and press left and down on the same frame, pressing left switches your movement to left, and then the check for vertical movement passes and you start going down in the same update. The other way is if two updates happen in one game tick. Fix both of these by remembering the last move. Switch the direction variable to an enum to make it easier to test the current and previous direction, and use a switch statement to calculate the actual changes to the position.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
There are two ways that could happen:
If you are going up and press left and down on the same frame, pressing
left switches your movement to left, and then the check for vertical
movement passes and you start going down in the same update.
The other way is if two updates happen in one game tick.
Fix both of these by remembering the last move. Switch the direction
variable to an enum to make it easier to test the current and previous
direction, and use a switch statement to calculate the actual changes
to the position.