Implement Slow Magnitude and Apex of Moment #606
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
igorwessel
commented
Jan 25, 2025
Comment on lines
+754
to
+756
| if enemyDB:HasMod("INC", nil, "TemporalChainsActionSpeed", nil) then | ||
| enemyDB:NewMod("Condition:Slowed", "FLAG", true, 'Skill:TemporalChainsPlayer') | ||
| end |
There was a problem hiding this comment.
I believe there is a better way to do this, I just couldn't find it.
igorwessel
commented
Jan 25, 2025
|
I did some tests and the current implementation is bad and wrong, I'll make turn again draft. It doesn't leave a space for us to use slow magnitude in movement speed modifiers. |
igorwessel
force-pushed
the
igorwessel/chronomancer-implement-slow-magnitude
branch
from
02050e4 to
c46d944
Compare
igorwessel
force-pushed
the
igorwessel/chronomancer-implement-slow-magnitude
branch
from
c46d944 to
c006522
Compare
|
It's finished, I must add support for gem with slow magnitude support in the next PR to finalize chrono. |
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.
Partially Fixes #180, still need Hourglass to finish Chronomancer implementation.
Description of the problem being solved:
Basically the slow in POE2 is very strong as a defensive layer if we are using curse, slow magnitude, and even the enchant that can come with slow magnitude.
So I have effectively implemented the rule that slows multiply together.
https://www.poe2wiki.net/wiki/Slow
I added enemy type conditions: rare/unique/magic for less slow effect.
Steps taken to verify a working solution:
Link to a build that showcases this PR:
Before screenshot:
After screenshot:
White Mob
Magic Mob
Rare Mob
Unique Mob