Victoria, Australia
I found this run and it is not yet on the leaderboard, perhaps it should be added?
The thing is though, no one as of yet is choosing to use autofire. Regardless of whether this thread results in anything being changed or not I am still not going to use autofire because it would not be comparable to the other runs. If you use autofire you can save 40-50 seconds from あお's WR from the Tama-chan (aka red cherry aka matryoshka) boss with basically no effort, and that also decreases the likelihood of losing runs to the boss because you have to dodge less attacks.
Given how good あお's WR is, in order to get a run that is close to matching it, said run has to be quite optimised. For a goal time closer and closer to あお's WR, the likelihood of getting the necessary timesaves decreases, and possible timesaves get smaller. But if we add in autofire, we can save 40-50 seconds for free while also making the run less difficult. This could then result in a new WR that plays worse than あお, only being the WR simply because the runner chose to use autofire.
I've already spoken about the autofire tag in a thread on IWBT Justice, in the case for that game I think an autofire option is okay, as the run is not particularly optimised, and the timesave from autofire is very minimal. But this game has the opposite attributes. The WR is very optimised and the timesave (and reduction in difficulty) from autofire is large.
As I stated in my initial post in this thread, historically, no one has done runs of this game with autofire. So if we take away the option, there would be no one affected, and we remove the possibility of having worry about this problem at all.
If we do remove the autofire option, and for some reason, someone REALLY wants to use autofire anyway, there could be a separate category. In the aforementioned Justice thread, Naloa argued that having the autofire tag avoids "having ... boards with one, maybe two, runners," and this was justified because "[many] games have iframes so any difference made [by autofire] would be minimal." I think for this game, that justification should not apply, and that a second category would be warranted. But I think that if any aspiring runner sees the leaderboard with autofire disallowed, they would just choose to run without autofire anyway; in all likelihood we would just never have any autofire runs and then every run will remain perfectly comparable.
Perhaps autofire should be disallowed in this game? With the exception of my own run, all prior runs have been from before autofire was added as an option for this game, and it was generally accepted that autofire was not allowed (as far as I am aware). If players are to start running this game and use autofire they would have an unfair advantage over all of the previous runners, as the previous runners would not have had the option. I don't think it would be reasonable to compare autofire and no-autofire runs in the way the leaderboard is currently set up to do so, given that the timesave from using autofire is not insignificant, and that it actually reduces the difficulty of the run as fewer boss attacks need to be avoided.
I started running this game recently and I thought it might be fun to run 100%. This category would differ from any% in a few ways; you would have to collect the secret items in the final stage, as well as play on Hard difficulty or higher. Doing both of these unlocks the extra stage after defeating the final boss.
Here is an example run:
Proposed rules: Time starts when entering difficulty warp. Time ends when entering the warp after the stickmen avoidance.
Could this get added as a category here?
Is autofire allowed? Historically, no one seems to have done runs of this game using it. kashio_39 now is, but it is not mentioned in the rules.
I noticed the autofire tag is actually present on a number of fangames that it is either not applicable to, such as I Wanna Be The My Heart Goes On, or similarly to Justice, not previously used on such as I Wanna Be The Crimson and I Wanna Be The Destination. Is the autofire tag being added for runs such as these a mistake, or is it assumed for all fangame runs that autofire is allowed unless stated otherwise?
By the way, I'm not advocating for disallowing autofire, merely seeking insight as to whether it being listed as a run filter is correct given that it is not mentioned in the game rules of multiple fangames that have it as an option.
Also, I intended to post a thread about this on the fangames category itself, but it doesn't seem to work for whatever reason.
1.0 is out and story mode is a thing now, so that would be a very good run to put here. Also it has gems in it, so a 100% category would work well too.
Why do you not agree with the ending?
As of now, the rules do not say anything about when the timer should start and when it should end for a MSQ run. This should definitely be added so run times can be consistently and accurately measured. I recommend the timer start being when the initial "Loading..." message disappears, as this is completely dependent on the runner's internet speed and is unfair to include in their time. I would also recommend the end time being when the player reaches the clear screen rather than just when they beat the final level of the challenge, as there is still some menu-ing to do after entering the warp.
