Arcane momentum says that every time you cast a spell, you gain stacks for arcane momentum, granting cast speed. Each cast should also refresh the duration of all current arcane momentum stacks.
Currently Arcane momentum does not refresh the duration of existing Arcane momentum stacks when gaining new stacks, which also makes the following Essence of Celerity passive’s 6 point bonus (10% movement speed at max stacks) useless as it’s practically impossible to sustain max stacks since by the time you cast spells enought to reach max stacks, your first stacks start to drop, thus you only manage to stay at max stacks for a split second, being unable to get any use out of that movement speed bonus.
Distant spark passive is supposed to grant up to 30% chance to cast Spark Nova when critically striking an enemy at least 4 meters away. I do not know how far 4 meters is in game, however no matter how far away I hit enemies from (and yes, critically striking), even if enemies are at the edge of the screen, I cannot get this passive to activate even once, thus I believe the passive is broken.
EDIT: I realised that tooltip says Arcane momentum’s max stacks are 5 (at 5 points invested) but it’s actually 40. The stacks go like this: 1-3-6-10-15-20-25-30-35-40 (basically 10 stacks) and the first 5 give cast speed while the remaining 5 stacks (20-40 arcane momentum) do nothing.
EDIT2: It seems that the passive was changed from 5 stacks to 10 stacks (but only being able to get the benefits from the first 5) and that the stack refresh was removed, and instead you can now “stock up” on stacks. Basically it had been nerfed on upkeep but it seems the change is not displayed correctly in the tooltip.
So Arcane Momentum is possibly not bugged but the tooltip just isn’t updated. Possibly the same with Distant spark?
I have tested it and it does indeed work as intended. BUT the stack icon is wildly bugged. Try doing the following test. Look at your movement speed (in my example 32%) then cast 5 skills and notice how it goes up 10% (42% for me) ignore your stacks on the buff, BUT don’t let it fall off by casting only 1 spell every few seconds. You will notice that it does keep your movement speed high (Same for cast speed and dmg). By the way you mentioned the stacks reaching 40, I reach like 75 with my cast speed. Hope that helps
That’s interesting, with my cast speed I could go just slightly above 40 but it caps at 40. Is there some other way to increase the max stacks then?
Anyways, the Distant spark is broken or suffers from the issue that the description hasn’t been updated and it does something completely different now.
Your cast speed dictates it(for reference, when fully buffed, I have around 148% cast speed). The more cast speed, the higher stacks you can reach. I did more upgrades and hit 85 last night after my original post. As you said, the stacks do “appear to behave” like they don’t refresh. The reason why it’s going up in that weird pattern (1-3-6-10-15-20-25-30-35-40) is that whoever coded it did it wrong. Instead of refreshing stacks, they’re adding the previous stacks, and they do fall off individually, as shown below:
first cast = 1 stack
second cast = 1 stack(already owned from the first cast) + 1 stack (from the addition of the poorly code) + 1 stack (from the new cast you just did)
Rinse and repeat.
They need to change the code to refresh stacks as intended and not add them indefinitely. It does seem to work mechanically properly. It’s just a bug in the display icon. I think its funny they got the display issue wrong when it should be the same algorithm as the mechanical part.
When I say mechanical, I’m referring to how it works, not the display portion.
Lastly, I haven’t tried the Distant spark. I’m almost on top of enemies so it’s useless for me.
I see, I can now reach 55 stacks although I feel like I haven’t even gained any cast speed but I could be wrong.
Also I found the problem with Distant spark. It does in fact work, however it casts it at the enemy location instead of you, and it also doesn’t seem to have any visual effects which makes it impossible to notice.
Looks like both of these bugs are just a problem with the passive description/tooltip
