Problem
AutoInvasionFinger uses hard-coded values to determine how long a key is held down and how long to wait before opening a menu. On slower systems, the invasion loop may have to run slower to account for this.
Example
If the script is ran on a slower system, menus may take a couple ms longer to render after a keypress is made which can result in a future keypress to select an invasion finger to be missed, resulting in the invasion loop being broken.
Solution
Implement a config to allow users to change the timing on the invasion loop so that the script is catered to their system.
Problem
AutoInvasionFinger uses hard-coded values to determine how long a key is held down and how long to wait before opening a menu. On slower systems, the invasion loop may have to run slower to account for this.
Example
If the script is ran on a slower system, menus may take a couple ms longer to render after a keypress is made which can result in a future keypress to select an invasion finger to be missed, resulting in the invasion loop being broken.
Solution
Implement a config to allow users to change the timing on the invasion loop so that the script is catered to their system.