Bug Reference #: 1,540,855,364
Issue: Upon reaching 0 charges, Flame Dash will stop recharging. This is the 2nd time I have had this happen to me. I am unable to recreate bug on demand, seems to be completely random.
https://imgur.com/a/YiPgUFOLast edited by Septiv#2068 on Jun 15, 2022, 3:13:20 AM Last bumped on Jun 16, 2022, 4:21:43 AM
This thread has been automatically archived. Replies are disabled.
|
Posted bySeptiv#2068on Jun 15, 2022, 3:11:36 AM
|
|
I figured it out. Still a bug though, I believe.
I had Molten Shell linked to Flame Dash. I'm assuming that when MS and the last charge of FD are used at the same time, it bugs out and stops BOTH (I missed MS originally) from recharging. I'm not able to get the timing window right to test this, but I'm fairly certain this is what's happening.
|
Posted bySeptiv#2068on Jun 15, 2022, 3:25:54 AM
|
|
One possible Eater altar downside is "Player gains: reduced cooldown recovery rate per power charge".
A skill's cooldown time is set when it is used, rather than the remaining time changing whenever your cooldown recovery rate changes. If you use a skill with a cooldown (molten shell, flame dash), with this altar effect, with enough power charges that your cooldown recovery rate for the skill hits 0% (which usually takes more for flame dash due to its built in cooldown recovery rate), the cooldown on the skill will not recover.
|
Posted byJadian#0111on Jun 15, 2022, 3:54:08 AM
|
"
Jadian wrote:
One possible Eater altar downside is "Player gains: reduced cooldown recovery rate per power charge".
A skill's cooldown time is set when it is used, rather than the remaining time changing whenever your cooldown recovery rate changes. If you use a skill with a cooldown (molten shell, flame dash), with this altar effect, with enough power charges that your cooldown recovery rate for the skill hits 0% (which usually takes more for flame dash due to its built in cooldown recovery rate), the cooldown on the skill will not recover.
Interesting interaction. But not the case here - as after I unlinked MS and FD they returned to working as normal, in the same map that I experienced the issue.
|
Posted bySeptiv#2068on Jun 15, 2022, 3:58:09 AM
|
|
Unsocketing and resocketing the gem is actually the way to get around the infinite cooldown from the power charge downside. Assuming you dont do it with a bunch of a power charges.
|
Posted bygladiatorpie#3317on Jun 15, 2022, 4:01:20 AM
|
"
Septiv wrote:
"
Jadian wrote:
One possible Eater altar downside is "Player gains: reduced cooldown recovery rate per power charge".
A skill's cooldown time is set when it is used, rather than the remaining time changing whenever your cooldown recovery rate changes. If you use a skill with a cooldown (molten shell, flame dash), with this altar effect, with enough power charges that your cooldown recovery rate for the skill hits 0% (which usually takes more for flame dash due to its built in cooldown recovery rate), the cooldown on the skill will not recover.
Interesting interaction. But not the case here - as after I unlinked MS and FD they returned to working as normal, in the same map that I experienced the issue.
changing gem links forces a recheck, so still not a bug.
|
Posted bydorkdude2#1774on Jun 15, 2022, 12:30:10 PM
|
"
dorkdude2 wrote:
"
Septiv wrote:
"
Jadian wrote:
One possible Eater altar downside is "Player gains: reduced cooldown recovery rate per power charge".
A skill's cooldown time is set when it is used, rather than the remaining time changing whenever your cooldown recovery rate changes. If you use a skill with a cooldown (molten shell, flame dash), with this altar effect, with enough power charges that your cooldown recovery rate for the skill hits 0% (which usually takes more for flame dash due to its built in cooldown recovery rate), the cooldown on the skill will not recover.
Interesting interaction. But not the case here - as after I unlinked MS and FD they returned to working as normal, in the same map that I experienced the issue.
changing gem links forces a recheck, so still not a bug.
What? I unsocketed/resocketed the gem to force a recheck and the FD remained chargeless until moved it to a completely unlinked socket. This absolutely is a bug.
|
Posted bySeptiv#2068on Jun 16, 2022, 4:21:43 AM
|
