Bug : Movement counter bug fix #78
Merged
Conversation
This file contains 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
mouheb182
force-pushed
the
movement-bug-fix
branch
from
01d5bec to
6300156
Compare
mouheb182
force-pushed
the
movement-bug-fix
branch
from
6300156 to
339f331
Compare
SMoraisDev
approved these changes
Nov 27, 2024
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.
Issue : #74
To fix the issue, I separated the moveCounter increment logic from the recursive function. The increment now occurs only when setting new movement coordinates. This ensures the counter increments correctly each time the player enters a new coordinate, accurately reflecting the number of moves made.