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.
Description
This is my first PR so I do apologise if it isn't perfect...
This PR restructures battle partner data so they use their own array separate from
gTrainers
so a user isn't wasting trainer flags. Generating the party data is handled through a newCreateNPCPartyData
function which generates the party based on the party flags given to the array entry with a parameter handling both a partner and a trainer, With partners being able to set their trainer name and trainer id to the party for the summary screen. Partners use thetrainerPic
field in the data for the back pic whilst trainer still use it for the front pic.Here's the new array for partners with Steven's vanilla party data remade with it:
This PR also adds functionality for both trainers and partners for the rival and all a person needs to do is set the rival's name to
{RIVAL}
and the trainer name in-game will display the name set for the rival. By default, it's set toMAY
if male andBRENDAN
if female.Discord contact info