Uploaded June 2020 | Updated September 2026, 6 hours ago
Extremely finicky but it works
Krythom
|
Itemless Dupe/WW to Lurien
🔇 TAP TO UNMUTE
![Hollow Knight - Kings Pass IL in 39.19 [WR]](https://i.ytimg.com/vi/UVypkjKDq-I/mqdefault.jpg "Hollow Knight - Kings Pass IL in 39.19 [WR]
Amazing category")
![[TAS] Hollow Knight Any% NMMS in 12:49.10](https://i.ytimg.com/vi/YGu732UYgjs/mqdefault.jpg "[TAS] Hollow Knight Any% NMMS in 12:49.10
Some Info To Help Clear Things Up:
White Screens - You may notice at a couple points during the run that there isnt a fade to a white screen where there normally would be or that a white screen goes away abruptly rather than the normal fade animation. This is because when entering the dream nail sequence the TAS does a trick to spawn in the seer earlier which unfortunately has the side effect of causing the rest of the entire run to be a pure white screen. To make the TAS a little bit more interesting to view I took the liberty of removing the white screen so you can continue to see the gameplay however this does result in a couple strange looking transitions.
NMMS - NMMS stands for no main menu storage and is the ruleset followed by this TAS. All glitches are allowed with the one exception of a glitch called main menu storage which allows you to access the main menu while you shouldnt be able to. The routes for categories that allow main menu storage generally (with a couple exceptions) boil down to noclipping everywhere which I find boring so Ive stuck to my main category of NMMS for this TAS
Timing - Hollow Knight speedruns are timed using a custom load remover to make times comparable between different PCs as the in game timer is both highly unreliable and not well suited to our purposes, this TAS also uses this timing method meaning 12:49.10 will not match either RTA or the time displayed in game however this is still the official time for this TAS
Segments - This TAS was made in 5 separate pieces that were stuck together at the end as at the time of making this TAS Hollow Knight still experiences a fair amount of issues with des-syncing as a TAS gets longer. Splitting the run into segments both made it easier to go back and adjust earlier parts of the run as well as drastically cut down on these de-syncs. I did my best to hide the cuts between segments so they shouldnt be distracting however they may be noticeable if you look for them.")
