imdivesmaintank
New Member
- Joined
- Oct 30, 2013
- Messages
- 342
- Reaction score
- 0
LMB is move only.
my skills look like:
1: move only
2: default attack
3: primary melee skill
Beta 2619 Bugs
- Thread starter imdivesmaintank
- Start date
my skills look like:
1: move only
2: default attack
3: primary melee skill
imdivesmaintank
New Member
- Joined
- Oct 30, 2013
- Messages
- 342
- Reaction score
- 0
wow idk how I missed that. I've fixed it and am running Library right now to see if that was the cause (seems likely).
out of curiosity, will that be restriction be dropped in the future? i like having move only on LMB and have always had it that way.
edit: yeah that was why it wasn't resetting library. sorry about that. it's fine now that i moved the move action off LMB.
Last edited:
There's no restriction in place, but there will starting with the next version. I've tried to enforce various client settings in the past, but I end up getting tons of complaints about the bot not working with wrong setups. However, I'll gladly trade that from now on to avoid an issue like this again.
The reason why the bot can't use Move when it's on LMB, is for reasons similar to what you and tozededao experienced here. The client doesn't "Move only" on LMB, because LMB is also the client's hard coded button for "Interaction". There's no assignable "Interaction only" skill, but it does exist.
Only when Move is not bound to LMB, do things work as expected, so there's nothing we can do to change that. I wanted to drop the reliance on Move only, but it's impossible for the bot. The client's object hitbox testing is too unpredictable, and trying to code around not clicking on things that get randomly highlighted is simply not worth the enormous amount of time it'd take (I've tried many times already).
The reason why the bot can't use Move when it's on LMB, is for reasons similar to what you and tozededao experienced here. The client doesn't "Move only" on LMB, because LMB is also the client's hard coded button for "Interaction". There's no assignable "Interaction only" skill, but it does exist.
Only when Move is not bound to LMB, do things work as expected, so there's nothing we can do to change that. I wanted to drop the reliance on Move only, but it's impossible for the bot. The client's object hitbox testing is too unpredictable, and trying to code around not clicking on things that get randomly highlighted is simply not worth the enormous amount of time it'd take (I've tried many times already).