- Joined
- Jan 11, 2016
- Messages
- 4,183
- Reaction score
- 13,272
- Points
- 838
- Gender
- Male
Well... think about it this way. Mouse movements are inherently inaccurate... so the length of the stroke on a typical mouse button is of little concern in comparison to the length of the stroke on a keyboard key, since both of those actuations are 100% accurate. The mouse movement itself is inherently inaccurate because it depends on actuation from an inaccurate device, the arm/hand/wrist. Those movements are subject to variable speed, over correction, blah blah blah, all the weaknesses inherent in manual human movement when flexibility is not needed.You're right. I didn't mean to imply that it would be useless or anything, just that it seems unnecessary and not particular helpful for these hits. Although as suggested a keybind for next/no occlusion would be nice.
So lets say you write a script that shaves an average of 3 seconds off each hit... not an impossible number for these hits we are discussing now and honestly thats pretty low compared to the time savings some scripts create with other hits. You can complete up to 3800 hits a day. 3800 x 3 seconds = 11,400 seconds / 60 = 190 minutes of work time.
Along with those time savings you also know that each time you actuate a decision point the exact same actions are taken, so you can be more assured your input is not only fast but also predictably accurate.