Add Support for Enemy damaging ailments #6814
Merged
Conversation
This file contains 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
Regisle
force-pushed
the
EnemyDamagingAilments
branch
from
7dbcd2e to
cef7df5
Compare
LocalIdentity
approved these changes
Aug 14, 2024
LocalIdentity
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Built ontop of #6809, merge that one first
Only the last commit is unique at the moment
adds support for enemy damaging ailments, either if the enemy has a chance to apply them or above a certain critical strike threshold, this is just so that it doesnt always show the enemy as being able to ignite you
This also correctly scales with unaffected by/immune to, and also will not apply if the duration is 0, but applies regardless of chance if the chance is greater than 0