But then shouldn't we simply delete the IGT column for the marathon speedrun mode for consistency with how marathon full game is sorted ? If it's possible though

Timers can only be enabled per-game, so a choice of whether to record IGT & RTA either has to be made over the entire game, or managed by verifiers (or a bot checking submissions, which is what we use for Hollow Knight).

If IGT were disabled, then this would remove the second time column from every category that uses IGT, and the RTA column would simply become Time. I don't see any reason to track RTA on SRM & segmented subcategories, so simply clarifying in rules which timing method to use would be enough.

Alternatively, a bot could force runs on non-SRM categories to only submit RTA & automatically fix runs that submit IGT, but this isn't foolproof and may still produce some confusion for new runners ("at submission time I see 2 times but I only have the time from Livesplit - what do I do?")

I think now is a good time to go over this, especially with SNB in SpeeDons (& being restreamed on GDQ), since as it is now this board is rather confusing to read for new runners.

Circling back on this, and hopefully clarifying a few things by summarizing my suggestions:

Marathon

Complete the game.

• Speedrun Mode: Complete all 5 chapters of Speedrun Mode in a single sitting. (Clarify timing IGT/RTA*)
• Full Game: Complete the game from a fresh save file.

Segmented

Complete all 5 chapters of Speedrun Mode as fast as possible. All chapters do not have to be completed in a single sitting.

Jumpless

Complete the game without pressing the jump button. Runs must show unbinding the jump button before the run starts.

• Segmented: Complete all 5 chapters of Speedrun Mode, may use multiple sittings.
• Full Game: Complete the full game in a single sitting.

Other

• *eg. Single-segment SRM runs need to clarify whether they use RTA or IGT, and if IGT, then we can remove RTA entirely, either through manually removing RTA/IGT on the appropriate boards (I do have a bot that can do this if wanted), or by removing IGT as an option and treating Time = IGT for these categories.
• Global controller/kbm label or subcategory variable. Controller% being a separate category entirely is unusual and splits a single category into 2. This gives every board a controller/kbm split - if this is undesirable a label still allows tracking & filtering every category while merging controller runs into the main board.
• ILs for SRM chapters! Needing to get a decent time in all 5 chapters to submit one is an unnecessary barrier; honestly I think having each IL should completely replace segmented, as it's a weird way to track players' IL times.

I also think "Real time" should be the main timing method by default for the Marathon Speedrun Mode category and not the IGT

Unfortunately "default timing mode" is still a per-game setting on SRC - there's a compromise to be made between 'do we want both times available? which should be default?' (does RTA matter when comparing speedrun mode runs?) made worse by the fact that only some categories have IGT, and so only some categories want that as the default.

Hi, I have a few suggestions that would bring this board more in line with what one would expect elsewhere on SRC:

• Make KB/Controller split a global subcategory variable - this gives a leaderboard split under every category. Controller% can then be merged into Marathon.
• Rename "Full Release->Speedrun Mode" to Segmented (and remove the redundant subcategory variable) to make it clearer from the name that it is not Marathon->Speedrun Mode.
• Add levels for each of the 5 speedrun mode chapters.
• Clarify timing rules - Marathon time starts on difficulty select and (as far as I can tell) when the final cutscene becomes visible, not "when credits roll" as in the Game Rules. Full game runs are submitted with milliseconds even though it is unclear where exactly the endpoint sits.

If migration is an issue I can offer scripts to automate the process if desired.

Scarab/Lumafly is used to install mods on the latest patch - MiniSavestates is not a mod but an assembly.

The most up-to-date instructions are in the HK-Resources Github repo - you replace [game files]/hollow_knight_Data/Managed/Assembly-CSharp.dll, then when you launch the game the text MiniSavestates Active should replace the Modding API text in the top left.

You cannot have Modding API enabled for runs, nor can it be installed alongside MiniSavestates.

The cross-platform autosplitter has been made available for submissions, see the latest news post.

You can upload a video to google drive & provide a link as long as that video remains publicly accessible through Speedrun.com after verification.

You can also publish videos as unlisted on Youtube, meaning a direct link will be visible but the video will not be findable on Youtube.

Yes, if you had a run rejected for a reason that is now legal, you may resubmit.

You need to use a colo-specific save file, as the wave autosplits rely on the Journal entries being uncompleted for the relevant enemies. You can download a working file here, you will need to use DebugMod or a save editor to add the abilities you need. Also note that this is a 1221 save where Flukenest costs 2 notches instead of 3, so if you use flukenest make sure you're not still overcharmed when you're not supposed to be.

It is not a speedrun of Hollow Knight, but a different game. This would be better suited on a board for that game if it exists, but would likely be too specific for such a board.

We already need to relegate a majority of odd or infrequently-run categories to a separate spreadsheet to avoid clutter (and verifier load); adding other unrelated games would only make it worse.

The autosplitter has a separate configuration (Edit Splits > Settings button); you can get splits from hksplitmaker which has autosplit triggers for all splits pre-made.

As a rule we will not add a new category before we get active interest in running it & at least 3 runs (though fewer is probably reasonable for HKMods) ready to submit; you can post runs in the Discord at #modded-categories so we can register interest.

Most resources are indeed currently available only on the discord, unfortunately, though some work is underway to remedy this. That said there aren't too many resources I am aware of for 107, but Hksplitmaker contains premade splits and route notes for the category.

Please ignore :)

If you mean Mound Skip (inventory dropping or otherwise maintaining control during the Vengeful Spirit pickup, and using that to leave the room before being teleported behind the gate), that is banned as it is invisible control.

You can read the full NMG ruleset here.

NKG appears in P5 regardless of whether you banish or kill NKG in the overworld. If you let Zote die then GPZ does not appear in P5 (he is the only boss that does this)

IL runs may omit the timestamp, but must still show the Title Screen. In short, if you were submitting ILs with a quitout to show title screen at the end or at the start, you can keep doing that.

The new ruling only affects full game runs, so that if a recording eg. has an unreadable version number at the start due to compression, or simply starts too late, a title screen from a later quitout can be used.

the chain

Stallball is NMG, but to my knowledge this just isn't worth due to the soul used (and needing to gather that soul, and the inconsistencies of stallballs...)

No version prior to 1.4.3.2/3 exists on consoles, so the only way to play 1221 (as well as the only way to have load times removed) is on PC.

Note there is a set of console boards for RTA 1432/3 runs, so you can have times compared fairly there.