Here the reasoning of run belongings to category will be published. Often it makes no sense to compete between different versions with same mechanics and route. Hovewer, some changes may remain unnoticeable but crucial at a time.
Examples:
- Tutorial Any% category haven't changed between 0.7.0 and 0.8.1, but from 0.8.2b the pannel been modified. Such runs cannot be treated as same category and placed at 0.8.1 version.
- WPWT Any% remains the same throughout 0.8.0-0.8.2b, hovewer, important superjump glitch mechanic has changed. Therefore, runs can no longer be compared and treated the same way.
In this forum each post will target specific reason of placing runs where they belonging to.Rules inside each category will receive the link to belonging post to ensure lack of ambiguity. Important! The forum is experimental and can be suggested to alter here. Forum will receive more functionality in the future as well.
One post here = one something edited. Simple as that!
Thanks for your understanding and contributions to the community! :D
Changed: Important info! forum
Reasons: | changelog appearence | clarification updates has been required |
Changed: Time precision
Reasons: To avoid collisions of sub-second difference, runs will be verified with 10 ms precision from now on. No collisions have been appeared yet, though all death% runs will be re-verified due to precision importance. It's a flaw that should've been fixed long ago. From now on every run will receive confirmation including milliseconds. For example WPWT Any% — 6:12:660
Changed: Mailbox prohibition now pointed out in KerfurO% rules
Reasons: As any% suggests, it is unclear that "any methods except cheating" excludes such an feature for run usage. Hovewer it's implemented for story mode, mailbox works as exploit that will tie all story mode runs to wise inventory management and off-screen preparations, which should not be the competitive case
Changed: Ensured ladder spam boost is not considered as a glitch
Reasons: It is unclear whether or not ladder spam boost is considered as a glitch. Since upper half of all ladders can be spammed to climb faster, it seems like not a bug at all. Applies to all versions where such a feature occurs as for now. Allowed in Glitchless% runs
Changed: Mid-air exiting of ragdoll state is not considered as a glitch
Reasons: It is unclear whether or not mid-air exiting of ragdoll state is a glitch or purposely implemented. By pressing spacebar after ragdolling you can speed up the "waking up" process right mid air sometimes. Works on pretty consistent manner and can be mastered so will not be considered as bug/glitch on all versions it remains stable. Allowed in Glitchless% runs
Changed: Death% time precision added for all runs
Reasons: The fastest category should have the most precise time to compare runs in it. May require 1 ms precision in the future
Changed: Added 0.8.2b version
Reasons: Came out a month ago, has debug tp difference with 0.8.2, hence game-changing enough to be considered as segregated version. VotV dev provided no info on mechanics further. For now on, only Any% story mode runs will be impacted by that. Has no visible impact on Glitclless% and runs may be placed at 0.8.2 as well.
Changed: Runs with no timer at the recording video will not be accepted. Timer can be started not at a time run started and ended, but within 2 seconds range.
Reasons: Timer allows to tell easily whether video is not speeded up or timer just overlayed on speeded up video. Easier for mod to tell if timer is correct and game mechanics working at normal speed with it (incredibly hard to unnoticably spoof). 2 seconds range is enough to stop timer manually and still have run covered with it.
Changed: Rules regardless hook were clarified
Reasons: Hook is the most broken item in the game right now in terms of speedrunning. It can boost you and can be used to fly on props. Some mechanics of it are glitchy and shouldn't be present in glitchless category. Only basic mechanics should remain there.
Changed: "You should NEVER cover point, saturation and stamina amounts by overlays or recording stuff" - added to general rules.
Reasons: Points are not easy to calculate manually. To avoid points modifications on run with external tools, they should be visible to the mods.
Changed: Added rule to the tutorial speedruns: "WARNING, show the game settings panel before the run! It's the only way to distinguish 0.8.2 versions between them despite having minor key differences!"
Reasons: other categories are showcasing differences in details mods can notice easily, but it's not the case for the tutorial ones sometimes