Renamed PartyMemberController
to BattlePartyMemberController
#190
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.
Changes:
PartyMemberController
toBattlePartyMemberController
.Notes:
This might seem small, but this will clarify things between Exploration scenes and Battle Scenes, as each scene will need its own separate, but ultimately unique
PartyMemberControllers
. Potentially we may at some point findPartyMemberController
or a similar script making a re-appearance, but this time as a inherited base class.Please make sure to get #186 merged in first. There will be conflicts, and it'll be more straightforward for me to just fix them on this PR by accepting "theirs" and throwing "ours" in the trash, in git speak.
For More Info See:
closes #184