You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm running the latest version of Path of Building and I've verified this by checking the changelog
Check for duplicates
I've checked for duplicate open and closed issues by using the search function of the issue tracker
Check for support
I've checked that the behaviour is supposed to be supported. If it isn't please open a feature request instead (Red text is a feature request).
What is the behaviour in-game?
A single Cast when Stunned support gem can support multiple spells independently. The active spells roll their trigger chance independently, and go on cooldown independently when they do trigger. Multiple spells may trigger from one stun.
What is the behaviour in Path of Building?
Cast when Stunned linked to multiple spells divides effective trigger rate (and in turn hit DPS) by the number of supported spells, as though one stun can only trigger one spell.
How to reproduce the issue
Add Cast when Stunned Support
Add spells that do not have their own cooldown, e.g. Ice Nova, Shock Nova, Frostbolt
Each additional spell lowers effective trigger rate of each individual spell.
Check version
Check for duplicates
Check for support
What is the behaviour in-game?
A single Cast when Stunned support gem can support multiple spells independently. The active spells roll their trigger chance independently, and go on cooldown independently when they do trigger. Multiple spells may trigger from one stun.
What is the behaviour in Path of Building?
Cast when Stunned linked to multiple spells divides effective trigger rate (and in turn hit DPS) by the number of supported spells, as though one stun can only trigger one spell.
How to reproduce the issue
Each additional spell lowers effective trigger rate of each individual spell.
Character build code
Screenshots
No response
The text was updated successfully, but these errors were encountered: