This repository has been archived by the owner on Nov 23, 2024. It is now read-only.
Refactor status checks and ability logic in VPR and BRD #209
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.
Refactored status checks in
VPR_Default.cs
by replacingStatusID.Reawakened
withStatusID.ReadyToReawaken
in multiple conditionals, affecting abilities likeUncoiledFuryPvE
andSerpentsIrePvE
.Expanded
InBurstStatus
logic inBRD_Default.cs
to include additional conditions based on player level and status effects such asBattleVoice
andRadiantFinale
, making the burst status check more comprehensive.Removed BRD Experemental pot usage.
Updated logic for using
RadiantFinalePvE
andBattleVoicePvE
inBRD_Default.cs
to include more detailed conditions considering cooldowns and player status effects.Modified the
GeneralGCD
method inBRD_Default.cs
to check for theBattleVoice
status instead ofRagingStrikes
when determining ifIronJawsPvE
should be used.