Flicker Strike
Flicker Strike + Multristrike + Melee Splash + Added Fire Damage + Increased Melee Physical Damage = An absurd amount of DPS. I'm currently level 80 and the DPS I output with a 491 DPS 2hd axe is ridiculous. This is definitely a YOLO build and not an optional skill for hardcore because of the desync. Currently you cannot control the direction of where your character is going while using Flicker Strike. It would be nice if GGG can edit Flicker Strike. While using the skill, your character will flicker towards the direction of where your cursor is on the screen. It makes more sense to control what you want to attack rather than attacking random monsters. Nonetheless, flicker strike is incredibly fun with the proper support gems and spec.
IGN: Marissa_Is_Hella_Hot
My Domination Shop: http://www.pathofexile.com/forum/view-thread/713727/page/1/#p6181728 |
![]() |
Please make this skill not shake my screen and move it around like crazy, makes me want to vomit.
|
![]() |
1) Camera:
Currently the camera follows the character in a ridiculous way, making it near impossible to follow what's happening in the game. I'd suggest making the camera move to where your cursor is while the skill is in-use and back to your character as soon as you release the button or run out of frenzy charges to keep using the skill. For this to work well with the skill let's get to point 2. 2) Automatic target choice: If the mouse is over an enemy while the skill is being used, then said enemy should be chosen as the target instead of random enemies in range. If the mouse is not hovering above a specific enemy, then the nearest few enemies should be chosen as targets and - again - not totally random enemies in the skill range. Those two simple changes would greatly improve the gameplay experience with flicker strike. IGN: Pirteloli
|
![]() |
instead of nerving the auto-targeting part of multistrike, how about changing multistrike to "the last hit will hit the initial target, if possible". That way it would also be better to use for single target purposes
|
![]() |
I currently use flicker strike in some 5L armor:
Coupled with blood rage and I endlessly flicker around until all mobs are dead. One thing that would be nice is having a little more control over the movement. Perhaps limit flicker to a certain radius from where you click so it will only atk mobs in that radius rather than chain flicker you across the map and not actually kill much. This could mean that you stop flickering while an enemy is next to you but slightly outside said radius, but I think that would be a small price to pay for the control you would have. |
![]() |
I think im talking for all flicker strikers out there right now... Chris or somebody, please, try some flicker strike character on normal servers (not on your testing ones) and you will see how fatal the desync is with using this skill as primary one. Game would be much enjoyable without /oos -ing milion times per map (and it sometimes doesn't even help).
1st Hideout of the week: view-thread/1059888
Gears & Builds history: http://www.pathofexile.com/forum/view-thread/1062423 |
![]() |
Really enjoy this skill on my oro's build but.. 2 things I'd like to see addressed
1) De-sync when coupled with multistrike (not nearly as bad as cyclone with multistrike, but still pretty ridiculous in 2014) 2) I like the random teleporting around when NO monster is selected. However, I'd like to see a change where if I specifically select a mob, I ONLY flicker strike that mob until its dead. Currently I select a mob and end up clear across the map with 50 1/2 dead mobs because the game makes me keep jumping away. thanks |
![]() |
" That specifically is Multistrike's downside. |
![]() |
oh.. right. well lame
|
![]() |
GGG - Flicker has been out for a while and we havent seen much change for control or desync issues with this skill. Us long-time players are lobe gunning to look at theory crafting with odd skills such as flicker. Unfortunately the majority of us are on HC. and this is NOT hc viable.
Any plans with this gem in the near future? Thanks! |
![]() |