Focus Swiftness Not Stacking At All
Focus is, IMO, has 3 big problems:
- Swiftness that doesn’t stack.
- Pull with a 1s internal CD, which make it very predictable and most of the times you fail.
- Bugged iWarden. Sometimes he dies trying to catch the enemy, cause is freaking slow at it due to the attacking CD. Sometimes, it even doesn’t attack a single kitten time…
i7 5775c @ 4.1GHz – 12GB RAM @ 2400MHz – RX 480 @ 1390/2140MHz
This is not a new thing, and the mechanic is well understood. Back in the betas, you could walk back and forth over the line to get infinite swiftness easily. To prevent that, they made the line not apply swiftness if you already have the buff.
It’s a band-aid fix, but here in GW2 band-aid fixes are permanent
This is not a new thing, and the mechanic is well understood. Back in the betas, you could walk back and forth over the line to get infinite swiftness easily. To prevent that, they made the line not apply swiftness if you already have the buff.
It’s a band-aid fix, but here in GW2 band-aid fixes are permanent
Your sigil gives you might on crit. But to ensure you don’t get too much might, you won’t get it at all if you already have might.
No. It can’t be. It’s just… wrong on so many levels.
Assign a unique ID to each temporal curtain. Make it an array and fill it with IDs of players who trigger it. Run an if-else statement to check whether to give swiftness (player not in array) or not (player already in array). Fixed!
Give the skill a cooldown of the same duration as the skill uptime with mechanics similar to sigils (tied to players). Half-fixed!
That said… Getting multiple stacks of swiftness through going back and forth makes perfect sense. It will be of limited usability to players because of its requirements; the swiftness duration cap is still there; the pulsing symbol of swiftness does it, so why naturally slow mesmers’ temporal curtain shouldn’t?
All they need to do is make it go back to 12 if you’re under 12 (modulo boon duration). No infinite stacking, you can only get max 12 seconds of swiftness going away from the curtain spot in any direction, and it’s still useful if you accidentally run over it with 1 sec left over from some other source.
^
Third viable solution.
^
Third viable solution.
One that everyone and there momma have stated ever since the initial nerf. I’m an amateur programmer and I could have fixed this easily so it boggles my mind why professionals haven’t done so already.
One that everyone and there momma have stated ever since the initial nerf. I’m an amateur programmer and I could have fixed this easily so it boggles my mind why professionals haven’t done so already.
I think the solution lies in the payment system of the game: things like Living Story is something very clear and appealing to new players who are looking for a new game to buy, while bugs become annoying once you master your profession only (which is, of course, once you’ve already bought the game and probably some extras). So naturally, priority goes to things which give more money.
(edited by Lishtenbird.2814)