This would probably be better informed on the Discord server for quick solution, being as it's not a particularly big issue, but I'm a bit retiring to chat on Discord, so I suppose it's acceptable to notify this as a forum post once

The Gate B: Ending 2 subcategory, as we all know, has a necessary individual timer stop condition in the category rules and a well-considered time addition of 1:22.120 in case of autosplitter use (which almost everyone uses), which was also decreed subsequently, aaand…

It wasn't too long ago that I appeared in this community, at most merely only about a month ago: I don't know actually what kind of intra-collective disputes, disagreements and other such things might have happened in the last few years behind the scenes… but the fact is that CookiesUnite is missing this very time addition in her Set Seed Inbounds 7:13 speedrun: it should be timed 8:35 including the addition, but instead the run is verified straightly with this LiveSplit timer value, which it shouldn't be, obviouslyI believe that this is just some unintentional confusion for sure, since she also has at least a few other runs in Intended% and Random Seed on Gate B ED 2 in different time periods, in which everything is timed fine

Besides CookiesUnite, there are also incorrect times for answols and Danimed in Gate B ED 2 runs. It's strange enough, however, that throughout all these years no one has noticed these cases so far… Well, be that as it may… I'd just want to draw the mods' attention to this so that someone free of them can retime the runs to restore integrity of the board

I don't want to give the impression of a nerd (although I'm afraid I already have anyway with my enormous texts inevitably), but It's important enough in my opinion to make such a big deal about it: it leads to an unreliability of the whole board (due to the shift of all record positions) and having a world record that isn't actual – when comparing equal time moments, the real one still belongs to DTY, which he rightfully earned two years ago, and no one has been able to beat his time so far

I hope that the numbers will be corrected in the near future, and I will be able to sleep peacefully… without thinking about that someone has 1:22.120, and someone does not, and this creates tremendous injustice in records times. I would love to run this warhead-disabling code-remembering route once again after Intended%