Character Stops Attacking/Moving when using skills bound to LMB under certain circumstances
Character Stops Attacking/Moving when using skills bound to LMB while holding 'Shift Key' and hovering over items and other interactables.
For example, I have Falling Thunder bound to my LMB, it works normally all the time, preserving the ability to walk up to items, and other interactables like chests, npcs, etc, this stops when I press the 'shift key' to attack in place, this allows my skill to fire in place, IF and ONLY if my cursor is NOT hovering any previously mentioned interactables, IF there's an interactable under cursor(generally highlighted when hovered), MY CHARACTER COMPLETELY STOPS all actions, it doesn't attack, it doesn't move either, this is disastrous in combat situations and especially high tier maps where items drop like crazy, whenever I 'accidentally' hover over an item in middle of combat(which is generally at least 40% of screen space, can get up to 90%, even with strict filters), this prohibits me from using my skill completely, making the game simply more difficult, the combat annoying. This is incredibly bad to play with, and forces you to not use the most common button in PC(LMB). This wasn't the case in PoE1. And this only happens with LMB. INPUT Method: Mouse and Keyboard Last edited by Climet#7103 on Mar 22, 2025, 2:10:49 PM Last bumped on May 17, 2025, 1:35:59 AM
|
![]() |
Here are some things you could try
1. Add a Key pick up in Options > Game (Might work) 2. Change ur LMB to RMB 3. Press Z (Default Key) to hide loot. Dont forget to turn back on. 4. change keybind to Control + LMB (Might have to bind it to a different skill slot because you wont be able to change the default bound skill 1. Just a few things that might work for you. |
![]() |
I agree that this is a problem in POE2 that didn't exist in POE1. It appears when using the "Attack in Place" key with Mouse & Keyboard input, but does not appear when using WASD without the key. It appears to be a bug.
|| Edit: I double checked and as expected, it will also happen in WASD input mode if you force the use of the "Attack in Place" key. Using Attack in Place still prevents casting skills when hovering (highlighting) an interactable object, while also preventing you from moving toward the object (as expected). || With Mouse input mode, if you were not using Attack in Place your character would walk to the hovered object to interact when clicking. When using Attack in Place, your character cannot reach the interactable but still defers to that interaction over casting the skill assigned to the Left Mouse Button. This does not occur in POE1 when setting Attack in Place for a skill on LMB. I avoid getting caught on items by using a pickup key (set to my highlight key), but the problem is still evident on interactables like containers, checkpoints, NPCs, and waypoints. It is somewhat funny that I can't use my skill to break open a container unless my cursor is first nowhere near the container. Last edited by Pehr#3739 on Mar 22, 2025, 9:07:28 PM
| |
" I know these work, but LMB is the only key which doesn't, and therefore this post. |
![]() |
My best advice is to hide loot with Z during stressful fights or breaches that spam a lot of loot. When the moment passes clean up the mess on your screen LOL. I have died on my monk so many times from these pauses leading to a freeze or stun that would never have happened otherwise.
|
![]() |
Thanks for your report, I'll pass this on.
| |
![]() | |
" Thanks, we (probably) won. |
![]() |
bump - After 0.2.0h, this problem is even more common for WASD, now, too.
I hope that this is still in line to be looked at, since it is a still a problem in Patch 0.2.0h. It actually appears to occur more commonly now with WASD mode as well. A change has been made which now causes characters using WASD controls to run toward interactable objects when clicking the left mouse button (even canisters and urns) if they do not have "Always attack without moving" set for a skill bound to LMB and are not using the "Attack in Place" key bind. This makes the issue described by this thread just as common for WASD as it was for the Mouse & Keyboard input mode. We previously didn't need to use Attack in place for WASD because we had full control over our character's movement. With this new change, this is no longer the case. I presume that this change was made to facilitate interacting with objects without having to move to them manually, but it is a detriment to combat. Was this change related to 0.2.0H Hotfix 2? I didn't see this mentioned, otherwise, scanning through the recent patch notes. Having your skills just not cast because your mouse cursor is near an urn or other interactable is problematic. There are frequently clusters of such objects (e.g. bottles in Ogham Manor or canisters in Black Chambers), creating unexpected dead zones for skills when using a mouse. This was all the more unexpected when it wasn't as great an issue for WASD mode in the past, but suddenly started frequently appearing again. |