Guys, be very careful when adding runic ward to your items. I just deleted a 2 very expensive items. It is not just a "free upgrade" it will remove your defences to add ward. My armor dropped with 600es to under 200es.
Don't make the same mistake I did.
Hey guys,
With such a large update coming to POE 2, I really am hoping that GGG can fix point-and-click. As an old man, WASD hurts my hands, the buttons are in uncomfortable places, and I have been using point-and-click for way too long. In POE 2, point-and-click is fundamentally broken. It does not work the same way as POE 1, most likely due to the changes to the movement systems and being able to move and attack at the same time. That being said, it should not be broken to this extent, and it definitely should be fixed. I feel GGG has not really played with point-and-click in POE 2 for a long time (they have mentioned this before), because if they had, it is immediately obvious that it is broken and does not work.
Some issues with point-and-click:
-Channeling abilities — You cannot channel and move. If you move, you break the channel and cast. You can test this as a new character by trying to use Bonestorm while moving with WASD vs point-and-click.
-Name locking — In POE 1, if you target an enemy with an ability, it will "name lock" to that monster. This means for as long as the button is held down, the ability will ALWAYS aim at the target no matter where your mouse is. This is also the case in POE 2, though there is 1 HUGE difference that makes this not work: movement commands. In POE 1, once you are name locked, you are able to move while your skill is still targeting the enemy. In POE 2, when you move, it overwrites the attack/skill command, releasing the attack/skill (which is what happens with the channeling problem), and therefore when you stop giving a movement command, the attack/skill is now pointed at your cursor.
These issues make point-and-click unplayable at worst and extremely awkward at best.
I believe the issue is that when using point-and-click, a movement command cannot be used while another command is being held. You can see this in action by attacking, then moving. When you do this, you cancel your attack and start to move to the location. This is what is resetting the name lock, as after you let go of the movement command, a "NEW" attack command is placed.
You can see this clearly by holding the attack command, then moving to a distant location. If you press once and let go of the movement command, you will continue to attack and move at the same time as if using WASD. However, if you hold the movement command, you will completely stop attacking until you release the movement command.
This boils down to 1 thing, in my opinion: the movement command is overwriting the attack/skill command and cannot be issued while the other is being held down. This "SHOULD" be an easy fix by allowing a movement command to be used alongside other commands, though I won't pretend I know the code behind it, so it might be a bigger task. Either way, it is 100% important and should be fixed. As it is now, point-and-click feels very bad to play, and WASD hurts my old hands!
Apologies for the wall of text. Hope it was clear.