-
Notifications
You must be signed in to change notification settings - Fork 118
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for Break Enemy Armour Below 0 - "Imploding Impacts" Warbringer #759
Add support for Break Enemy Armour Below 0 - "Imploding Impacts" Warbringer #759
Conversation
enemyModList:NewMod("Condition:ArmourFullyBroken", "FLAG", true, "ArmourBreak", { type = "Condition", var = "Effective" }, { type = "ActorCondition", actor = "enemy", var = "CanArmourBreakBelowZero", neg = true }) | ||
enemyModList:NewMod("Condition:ArmourBrokenBelowZeroMax", "FLAG", true, "ArmourBreak", { type = "Condition", var = "Effective" }, { type = "ActorCondition", actor = "enemy", var = "CanArmourBreakBelowZero" }) | ||
enemyModList:NewMod("Armour", "OVERRIDE", 0, "ArmourBreak", { type = "Condition", var = "ArmourFullyBroken" }, { type = "GlobalEffect", effectType= "Debuff", effectName = "ArmourBreak" }) | ||
end }, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I previously tried adding a mod that directly affects Armour here already, but couldn't figure out how to access the enemyArmour Config value, which is not assigned until later. So it is now done in CalcOffence
instead. If anyone has a more elegant solution, I'd prefer to have this step done here instead. (I still think it's better in CalcOffence
than further down in the ConfigOptions
where enemy Armour is assigned though)
This was the code I tried:
enemyModList:NewMod("Armour", "OVERRIDE", -enemyModList:Sum("BASE", { source = "Config" }, "Armour"), "ArmourBreak", { type = "Condition", var = "ArmourBrokenBelowZeroMax" }, { type = "GlobalEffect", effectType= "Debuff", effectName = "ArmourBreak" })
I updated the damage bonus cap according to the info supplied by Viperesque. The rest of the assumptions were confirmed. |
Fixes # .
Description of the problem being solved:
Assumptions made for the calculations:
Maximum % 'anti-reduction' is 90%, as PDR is also capped at 90% (really not sure on this. otherwise theoretical maximum would approach 100% given 1 damage and infinite Armour)As per Viperesque from GGG, there is no cap on bonus damage from negative Armour, apart from the mathematical cap of 100%. [fixed]Limitations:
Steps taken to verify a working solution:
1.91.99(flat 10% PDR does not automatically mean maximum 1.9 effective DPS because the 90% cap is applied after the addition of 'anti-reduction' and PDR).Order no longer relevant because the cap is now 100%Link to a build that showcases this PR:
Test Build
Before screenshot:
None
After screenshot:
Imploding Impacts node effect

Breakdown Armour Broken Below Zero (max)

Breakdown Armour Broken Below Zero (partial)
