Team 04 - Implementation of Module 4: Game State Manger Module#72
Open
VirochaanRG wants to merge 3 commits into
Open
Team 04 - Implementation of Module 4: Game State Manger Module#72VirochaanRG wants to merge 3 commits into
VirochaanRG wants to merge 3 commits into
Conversation
VirochaanRG
changed the title
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
1 participant
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.
This is a rudimentary implementation of the Game State Manager module as defined by the Module Guide and MIS. I tried to implement all the functions as defined and applied the logic in the way that it was stated in the MIS. I had a bit of trouble understanding all the rules and usecases so I tried to implement the logic the best I could but there are definitely situations and move_types that might not be implemented. The GameStateData currently just consists of a board layout in the form of a dict but this can be expanded along with the MoveData as necessary to account for more fields.