Hello. I’m aware of topics of force move issues but I have new issues with it since s2 launch. Before s2 everything was 99% smooth with using force move binded on keyboard.
There is new issue with it that was not there before s2.
First I noticed it when it killed my HC rogue when fighting Avarice. In phase when Avarice spawns a lot of surrounding rings/pools my character when standing in it and using force to move key it somehow got stuck inside one of the pools.
I believe this particular new issue is only for melee characters that are the closest to the monsters, for me at least as a Flurry melee Rogue.
Its the same with a lot of other AOE ground effects and/or the animations after killing monsters (f.e. killing the bloated things with spiders inside).
When I am inside the area that said animation occurs (which is bound to the AOE dmg effect when they explode) my character gets stuck inside of it and using force to move make it wobble and circle around inside of it like there is invisible wall at the border of the AOE effect.
Its really bad because it occurs much more often then not. From my testing it looks like the using the force move again after “block” occurs sometimes it lets my character go away but only sometimes. Its forcing me to use dash instead force to move to get out of it.
Aside of that issues there is A LOT of issues with hitboxes for melee rogue that are since game launched. Character being on top of monster, being stuck right at it and also being unable to attack the monster as if it was obstructed in line of sight. From this situations also only dashing out of it helps to “unlock” character making it able to move or attack again. If I dont need to move/escape then i use HOLD POSITION shift to just use flurry and kill monster on top of me. But its really bad und surely doesnt work as intended.
Why character can’t attack and gets stuck by a monster’s hitbox when no line of sight obstructions and being right on top of a monster?
Those 2 MAJOR movement and being stuck issues in such a fast pace game is beyond something that can be dismissed especially on HC.
Can somebody test this as well as a melee?
THIS MUST BE FIXED.
===EDIT>>>
Ok, with further testing I get the assumption that the issue is not bound to the force move itself, but with the various AOE and death animations effects in the game. Before s2 it didnt exist. It seems that sometimes some AOE effects tend to do 2 things:
- Invisible barrier at the border of the AOE effect that is blocking force move “travel”
- Sometimes also it seems like the force move travel after being blocked by said invisible barrier starts to be pulled/pointed to the center of the AOE when mouse and travel direction is away (If it would “work” only based on invisible barrier then character should get just stuck on the border in direction of travel not bounce etc.).
So the force move itself works ok as it was before s2 BUT when interacting with AOE effects on the ground or sometimes some death animations without any AOE its getting blocked in this AOE area or on very top of monster(sticked to it) on some death animations without AOE.
Its not easy to replicate and test on single monsters with AoEs or specific death animations because of fast pace and many monsters at once but for me personaly it occurs very often all the time in combat. Out of combat force move works fine and is not blocked etc… I assume its connected strictly with melee character being inside the Aoe when it occurs.