I think everybody just got busy and moved on with other stuff. Swap hopping isn't that bad from what I remember. Everything in the route should work just fine.

Yeah no need to reject runs of course, but I proposed a solution 9 months ago and no decision was made so I'm bringing it up again. The thing is it's not like 2.4 is entirely better anyway since it lags way more.

So what's going on with Maria on Emulator? I took down 3 PBs to make sure everything is fair, but now everybody is using ancient versions of Bizhawk to get an advantage. Either we start doing loadless timing or it's a free for all.

My run is old and bad, but it does have input display if that helps.

Well I think milliseconds need to stay in if we remove loads, but thousands could be dropped since capture imperfections make that measurement meaningless. Actually on the Timing Conventions guide it already says "Precise times use milliseconds rounded to the hundredths place." for all categories.

I think there are no breaking differences for Richter when playing on the JP psx version unless I'm forgetting something, so you should be fine using that for RAB.

If something isn't listed here or in the Extensions board as a category shouldn't stop you from running it or posting about it. It just means there are either no runs or not enough runs to justify creating more clutter. We already have more categories than most games. The categories are defined by the runners, not by what is listed here.

Splits are only for you, they don't matter at all for your submission. By default the autosplitter is tuned for Alucard categories and the Shaft split is not turned on.

You can use whatever controller or input device you want to as long as it adheres to the rules.

no

Added the Name Code annotation field to Alucard categories, with Normal being default. It shows up on the board page and can be filtered. Depending on community preference Glitchless can be split with dedicated rules.

It's undeniable that this is the next evolution of the category. It reminds me a lot of Aria without shop. It's also clear, and this isn't new information to anybody, that Luck Mode significantly changes how the game is played, so that should be indicated. I don't think this warrants category segregation, a filterable field works great. Glitchless is the only one that should be segregated because both routes deserve their category.

Not really relevant since nobody runs the category in non-replay mode. But yes that is also something that should probably be indicated on the run somehow. It just so happens that all runs are replay mode. I think Rom did some non-replay runs as a separate thing. If anything that point just means there needs to be more clarification to avoid it being confusing why we can skip cutscenes and purchase Duplicator. I don't understand what exactly they are waiting for. At the very least there should be a temporary place where all of these runs should exist.

The main problem with flat allowing any name code is that it would eliminate any way to see how the run was done apart from comments. Normally there is at least something to filter by.

I think the good options are:

• Variable like with the Maria categories, segregates
• Field that is displayed on a run indicating the name code that was used, allows filtering

Another option is to preserve current Any% NSC and change to Any% NSC No code, but that's ugly.

Unfortunately it seems like the time youtube provides with their api is not accurate, so I've had to add a framerate field in order to properly adjust milliseconds. This reduces ease of use but I'm hoping maintains the usability of the tool while being accurate. I didn't expect the api to spit out a fraction that is straight up incorrect.

The current time is taken directly from youtube's information for that frame, so it all depends on how the video is transcoded and timed by them specifically.

EDIT: It seems like the way they track time internally and provide it via API might have some inaccuracy. Will see if I can account for that.

Oh that is done on purpose, assuming that the segments would be spaced out by at least a frame.

Hope it is helpful, feel free to message me somewhere or submit an issue on github for problems, bugs or feature requests.

For a while we've used frame-accurate timing for top times in the SotN community. A while ago we also started removing loads for certain categories to combat performance differences.

I've made this tool to make the process of doing that faster and easier without the need to download anything. But unfortunately the process is not ideal and not precisely accurate.

You can find the tool here: Segmented Timer

And a short video instruction here: How to use the Segmented Timer tool

EDIT: I made an issue request to the youtube team and they responded that they will not adjust their API to increase accuracy of the reported current time. This means that the only way for the timing to be accurate is to request the runner to provide the exact framerate, since they both don't have a visible framerate in their API and even if they did it would be rounded. My desire was for this to replace the need for yt-dl and avidemux, but it seems like it won't happen.

I imagine either nearest or just removing the last digit.