Document Battle Castle App setup functions #941
Conversation
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.
Continuing off of #923, this PR focuses mainly on the functions in each app that handle setting up the graphics and a few other initializations. A lot of this is boilerplate that is very similar to the Battle Hall app (#911), not getting into the app's core logic yet.
The biggest item of note here I think is the naming of the two apps as
BattleCastleSelfAppandBattleCastleOpponentApp. I chose these names based off the list items that open each of them when in between rounds: "SELF" and "OPPONENT". The first allows the player to view and modify their own lineup, the latter to view and modify the upcoming opponent.