Raging Storm: Love has a critical bug where the first die sometimes does not hit regardless of the roll. This is due to asynchronous processing masking a programme mistake that is impossible for players to deal with (I'm not familiar with asynchronous processing in Unity, sorry if I'm wrong). So I made a patch to fix this bug, but the current rules don't allow it to be used. I put here in case you still want to use it, or in case future rule changes allow it. https://drive.google.com/drive/folders/1dXw3bsgfqBwS7zKDIBZR4sz5u0aV65of?usp=sharing
To install, see the Autosplitter Readme. https://drive.google.com/drive/folders/1EgNIGJ12yFoYuw3LeH02SdmodW0E4iWF?usp=sharing
"Raging Storm: Love" is used in most of all WR and have high utility: mass attack, 5 cost, no emotional level restriction so that the bug which the first die doesn't hit is serious problem.
That's why, I'm going to allow to use the bug fix patch and revise the present rule disallowing any external tools. I expect new runners achieve best records.
Thank you for improving circumstances, Argo.
"That's This, and This is That" category rule is modified. The change is as follow.
Before, Timer stop : Show "the title logo" after the last invitation
After, Timer stop : Show "the talk text between an arbiter and librarians" after the last invitation
March 21, 2022