Reset invasion loop if attempting to connect to host fails #2
Description
Problem
A common occurrence while attempting to invade involves one of the invasion fingers acting as if a successful attempt at invading is made, which results in nothing happening. When using the same finger, the user is prompted to cancel the invasion. If this connectivity issue occurs while using AutoInvasionFInger, the invasion loop will be broken which results in keystrokes being sent to incorrect items and menus.
Example
While the invasion loop is running, the bloody finger is used to attempt an invasion. The bloody finger "thinks" it found an invasion but the host or client may have some connectivity issues, resulting in nothing happening.
Solutions
Add a keybind that resets the invasion loop and corrects the issue to the invasion finger that is having issues connecting.
Other Notes
*If this issue occurs when using the script, stop the invasion loop and cancel the invasion for the respective finger. The invasion loop can then be restarted.
*This issue may not be fixed as a "good enough" solution already exists (see first bullet of Other Notes section).