I apologize for deleting the module. It should be less deleted now.

????

Thanks, past me.
Not for allowing multiple strikes on TP, but for copying Mineseeker's queue system when Faulty Sink was originally implemented, which allowed for multiple strikes.

v2.33

v2.31
[FS] When assigning buttons for the spinning rule, it checks to see if the button selected is the button spinning. Somehow, I failed to realize how this could be bad for the counter-clockwise rule.
I think I even encountered this bug several times in testing but thought I was just imagining things. That's what I get for programming instead of sleeping.

What the [Skill Issue] is a coroutine???

v2.3 - The Reset Update
Address the following three exceptions:
[FS] The module breaks when attempting to rotate in Twitch Plays.
[S|FS] The module breaks when interacting with a button and then autosolving the module.
[S|FS] The module breaks when striking and then autosolving the module

[FS] - Remove the Skip function.
What's the skip function? It's the function that skips the rotation rule for Twitch Plays. All three options above used it so it needed to be removed.
[FS] - Add a Reset function.
What does the reset function do? It's the Skip function, but it's renamed. Sometimes just a change in purpose is enough to make the bugs go away.

Other changes
[S|FS] - Set the module's ID before logging the version of the module
[FS] - Fix a visual quirk in the texture rule while autosolving
[FS] - Slightly lower the rotation chances when rotating is enabled. This should keep it from activating after every press every time. (It'll still happen a lot though, if it's activated)
[S|FS] - Literally rewrite both modules from scratch. All of it was optional so sorry this update was delayed like two months. Changes will be detailed on GitHub.

v2.22TP
[FS] - Coroutines are the bane of my existence.

v2.22
[FS] - You see, any person who knows Unity would be able to tell you that running StartCoroutine on an IEnumerator would start it from the beginning.
Except, they wouldn't because that's not how it works.
Maybe now that I finally understand coroutines I can make sure the rotation rule works properly. Like, for example, making sure the timer is actually reset when holding the button.

[FS] - Make a note saying how many inputs were processed, rather than just saying inputs were dropped.