Love seeing the discussion! My personal thoughts are that Glitchless and Any % are separate categories, which is normal in most speedrunning communities. Any % can also be multiple categories if we wanted to separate out certain glitches. Using FF6 as an example again, there are categories for Any % (All glitches), Any % Sketch (All glitches except one really powerful one) and Any % No Sketch (All glitches except two powerful ones). Not an expert on FF6 runs, just saying it's not uncommon to separate out. If further glitches are found other than OoB, the categories can always be updated again - no reason to worry about hypothetical glitches right now.

That being said, if people are correct that this glitch is hardware related and not repeatable by most runners, then we should decide as a community whether it's a valid run / route. My personal opinion is that if it's not repeatable, we shouldn't allow it, as then we have a category basically for just one person. That will take some work on our ends, as runners, to determine whether we can replicate it and, if we can, what it takes to do so.

So for now, I think it is appropriate to keep the categories separate, until we figure out if it's replicable and/or there are other glitches.

I haven't been able to replicate the OoB either. On his Twitch, he included an input overlay, but I haven't gotten it to work yet. My guess is that he's on an older patch, as I know the earlier releases had some wall / OoB issues that were later patched. Would love for Mountebank to explain his process though.

As for separating the categories, I think it makes perfect sense how much OoB impacts the route. There's no reason not to separate and it lets runners play their preferred route, etc.

Saw the new run, congrats on finding the new techs! Two questions:

1. How are the OoB done?

2. For mods, now that there are skips that heavily impact routing, should we separate any% and glitchless into two separate categories? This is pretty standard for RPG runs, for example https://www.speedrun.com/ff6

Cool, thanks for the explanation!

Thanks for verifying! Couple notes:

1. Since there are now categories for every difficulty, we should remove Any% as it is no longer relevant and transfer the one run to its difficulty category.

2. Was the Genesis console category deleted? What happened to its WR? We should find a way to restore it if so.

Sure is, got very very lucky on that and it saved this run even though the rest of the run is a bit sloppy. I've done over 80 runs on this game so far and only hit the gnat twice haha. You can see the full stream (while Twitch still keeps the VOD) with several attempts here and the gnat is at around 39 minutes. I also had a 12:07 on this stream gnat free at around 28 minutes.

Thank you! I'll add ms to the leaderboard and frame count all the runs so we can both be 5:01 :)

My run on GDQ Hotfix can be found here. I had a very rough 28 / 29, but otherwise a decent enough run and it was a ton of fun.

It's just Queuety, but I'm afraid I don't really stream anymore. If people are interested after GDQ, I'd be happy to start streaming again though.

I just did my first run on PC to set everything up and it turns out PC is a lot faster than console. I also added a timer overlay just for Handtuch18 :) even though we don't require it. I'll try not to verify my own runs unless MaykHibiki no longer wants to do it (I appreciate you!).

Yes, I'd be happy to be added as a moderator - I'm currently running this game almost every day and will be submitting more runs. I'll actually be demonstrating this game for GDQ on Twitch on Sept 25th, so I expect we'll have more runners soon.

A timer on screen is not required - it is not required in the game rules or by speedrun.com. The rules state: "The time of the run is the time in the video from starting condition to ending condition. It is not the time shown on the timer program, which is started and ended with human error." The rules also state: "Do not require a timer on a video unless there is a good reason to do so. A good reason might be a game that uses an auto-splitter to track time without loads." An onscreen timer is also not practical when streaming on a console and places an undue burden on any console players.

I'm down, I think I'm the only currently active runner. I appreciate you verifying my runs (and so fast!), but I'm happy to take on some of the work too.