Raise shield getting cancelled by move click needs to change.

I'm playing a shield warrior with a mouse, and I don't want to play WASD.

With WASD, you can raise shield and move in all four directions, with the shield raised.
With mouse click, the shield is lowered whenever you click, essentially nerfing the skill for mouse users.

Solution suggestion:
- Make mouse movements no longer undo raised shield. (mandatory)
- Make raise shields a "toggle" skill. Press skill once, shield is raised until you press it again or use another skill.

Better yet, make the skill a two-parter. One part to toggle on/off and one subskill to choose where to face.
The best way to implement this would be to that subskill a general shortcut you can assign in your input options like weapon swap etc.

That way, you can toggle your shield on, move around with your mouse, and press your custom shortcut to change the direction when needed.

Thank you for your time.

+1 game breaking if true

just use WASD lol, click to move is objectively inferior

"

gmillar#4054 wrote:

just use WASD lol, click to move is objectively inferior

There are many reasons to disagree tbh.
My main reason is accessability, 2 hands amputated, and my limitation is one arm on keyboard, can't do movement and spells at the same time.
Stopping movement to cast will lead to deaths.

Clicking to move is great, got >25k hours in PoE 1 with it just fine.

The issue is the usability gap of the Raise Shield skill here, and it can, and needs improvement.


Issue #1
When holding down the Raise Shield skill button, clicking to move drops the shield and you run instead.

My suggested solution
When holding down Raise Shield and clicking somewhere, it should walk with shield up same as WASD movement rather than run.


Issue #2
With WASD you have free movement in any direction while blocking. On the contrary, with M&KB you'll walk to the location yur cursor was at when you pressed Raise Shield.

My suggested solution (Suggsting solution here is hard, but I have 2)
1) When blocking, lock the rotation to the direction when blocking was first initiated.
2) Allow namelocking block direction.

And to be fair, there are many solutions with a smaller gap between WASD and M&KB