From b3b79e56a8232ba58827a7bc3ea430acc560d556 Mon Sep 17 00:00:00 2001 From: tildejustin Date: Fri, 13 Feb 2026 19:45:56 -0500 Subject: [PATCH 01/26] version-bound statistics advancing, #220 --- rules.typ | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/rules.typ b/rules.typ index 830baa9..35c72f8 100644 --- a/rules.typ +++ b/rules.typ @@ -302,7 +302,7 @@ A.5.4) Unless otherwise specified, pauses do not contribute towards in-game time - A.5.4.f) The advancements menu opening - A.5.4.g) The confirmation screen upon clicking [Intentional Game Design] - A.5.4.h) The "Twitch Broadcasting Unavailable" Menu -- A.5.4.i) Clarification: Pressing the Statistics menu causes the game to temporarily advance. This time will be added towards the final time. +- A.5.4.i) Clarification: Opening the Statistics or Achievements / Advancements menu may cause the game to temporarily advance in versions between 1.7.2 and 1.21.5. This time will be added towards the final time. A.5.5) Loading times (the Loading Terrain screen and Joining World screen) do not contribute towards in-game time.\ A.5.6) If lag occurs in the run which causes your game to freeze fully, this time will not contribute towards in-game time.\ A.5.7) If lag occurs, which causes a portion of the game to revert back to a previous state, this time will not contribute towards in-game time. From 084681e947100ed1359cbf819700740597980344 Mon Sep 17 00:00:00 2001 From: tildejustin Date: Fri, 13 Feb 2026 19:47:24 -0500 Subject: [PATCH 02/26] fix broken glitch example links, #144 and #219 --- rules.typ | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/rules.typ b/rules.typ index 35c72f8..a50c4e8 100644 --- a/rules.typ +++ b/rules.typ @@ -618,7 +618,7 @@ D.1.1) Only these glitches may be used during glitchless runs. - D.1.1.ai) Entering and breaking a boat simultaneously (#formatLink("https://youtu.be/RtDjfQqZB0Y")[Example]) - D.1.1.aj) Entering and breaking a nether portal simultaneously (#formatLink("https://youtu.be/FKT3cwU432k")[Example]) - D.1.1.ak) Retrieving a fishing hook from >32 blocks away (#formatLink("https://youtu.be/L6KSxYhZUvc")[Example]) -- D.1.1.al) Retrieving a fishing hook when the attached entity is in a different location (#formatLink("https://clips.twitch.tv/MiniatureTangibleChickpeaGivePLZ-fBmyL_Srx70ZnA8w")[Example]) +- D.1.1.al) Retrieving a fishing hook when the attached entity is in a different location (#formatLink("https://youtu.be/ODhRxsN6bCA&t=642s")[Example]) - D.1.1.am) Fast Looting (#formatLink("https://youtu.be/uZC_XE1t5yQ")[Example]) - D.1.1.an) Altered Fast Looting (#formatLink("https://youtu.be/L2VS3nWOc_U")[Example]) - D.1.1.ao) Force fast perch leaves by hiding (#formatLink("https://youtu.be/xNQtFdCGoxM?t=81")[Example]) @@ -669,8 +669,8 @@ D.1.2) Any other glitches not included in D.1.1 must not be used during glitchle - D.1.2.ab) Saving blocks by lag abuse (#formatLink("https://youtu.be/qhvBNctnJCk")[Example]) - D.1.2.ac) Shared hitbox abuse (#formatLink("https://youtu.be/aPtvSnMLmnI")[Example], #formatLink("https://youtu.be/X6F-eq1-QLE")[Example \#2], #formatLink("https://youtu.be/JRYuWzPLQeY")[Example \#3]) - D.1.2.ad) Teleporting via a pearl with nether portal (#formatLink("https://youtu.be/g5knWZnrmbM")[Example]) -- D.1.2.ae) Boat desync (#formatLink("https://bugs.mojang.com/browse/MC/issues/MC-205477")[MC-205477], #formatLink("https://youtu.be/MUuVgMxUfcA")[Example], #formatLink("https://femboy.beauty/7Z8iu")[Example \#2]) - D.1.2.af) Using a nether portal without the portal animation (#formatLink("https://youtu.be/IUf07boL9Ac&t=60")[Example]) +- D.1.2.ae) Boat desync (#formatLink("https://bugs.mojang.com/browse/MC/issues/MC-205477")[MC-205477], #formatLink("https://youtu.be/MUuVgMxUfcA")[Example], #formatLink("https://youtu.be/k0-6v85TprA")[Example \#2]) D.1.3) Save and quit must not be used during a run. - D.1.3.a) Exception: If you accidentally use Save and Quit within a run, it may still be verified (at the discretion of verifiers) if it is accidental, attempts are made to rejoin the initial world relatively quickly, and if it provides no additional benefit to the run. - D.1.3.b) Exception: Runners may Save and Quit within a run intentionally if and only if there is a relevant bug (at the discretion of verifiers) which can be resolved by saving and quitting (e.g. pie chart bug, ghost blocks, resetting fog, restarting autosave timer to avoid leads breaking). No additional benefit may be gained. From c4961def991b310b7c9c1437b4bbecc17b6afa39 Mon Sep 17 00:00:00 2001 From: tildejustin Date: Fri, 13 Feb 2026 19:53:31 -0500 Subject: [PATCH 03/26] clarify that coop runs are timed using rta, #218 --- rules.typ | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/rules.typ b/rules.typ index a50c4e8..944077f 100644 --- a/rules.typ +++ b/rules.typ @@ -271,7 +271,7 @@ This excludes but is not limited to: == A.5: Timing Rules #entangled[Entangled Rule(s):]\ #entangled[A.5 is referenced by: ] #entangledRule("E.2.2")\ -#entangled[A.5 is nullified by: ] #entangledRules(("11.1.2", "CE16.1.4"))\ +#entangled[A.5 is nullified by: ] #entangledRules(("F.2.4", "11.1.2", "CE16.1.4"))\ A.5.1) Runs begin timing on either world load, referring to when the player is placed into the world, or on first input. - A.5.1.a) Clarification: The timing method that is applied is defined by the category, and not chosen by the player. - A.5.1.b) Guidance: Random seed categories, longer categories, and categories which benefit from waiting additional time are likely (though not always) timed by world load, whereas set seed categories and shorter categories are likely (though not always) timed by first input. @@ -745,6 +745,7 @@ F.2.2) Runs done on external servers, or runs on LAN which choose to do #entangled[Entangled Rule(s):]\ #entangled[F.2.2 is referenced by: ] #entangledRule("F.1.3.b")\ F.2.3) On external servers, if /time set 0 is not done, then time starts when the server loads the world and server logs must be submitted. +F.2.4) The category is timed by RTA, nullifying #entangledRule("A.5"). == F.3: Video Rules F.3.1) Every player should record their perspective, and all of these perspectives should be submitted with the run. From 2147aa6067c7f45ada571cc67ee7c859de1f58d4 Mon Sep 17 00:00:00 2001 From: tildejustin Date: Fri, 13 Feb 2026 19:54:55 -0500 Subject: [PATCH 04/26] allow unbreakable fishing line / lead with dimension change, #2 and thread --- rules.typ | 1 + 1 file changed, 1 insertion(+) diff --git a/rules.typ b/rules.typ index 944077f..ee9b828 100644 --- a/rules.typ +++ b/rules.typ @@ -637,6 +637,7 @@ D.1.1) Only these glitches may be used during glitchless runs. - D.1.1.ba) Feeding a parrot a cookie to obtain Over-Overkill advancement (#formatLink("https://bugs.mojang.com/browse/MC/issues/MC-269656")[MC-269656]) - D.1.1.bb) Trapping wither (#formatLink("https://youtu.be/PCkzhtBl_xY&t=91")[Example], #formatLink("https://youtu.be/O-QgTljCgZw&t=153")[Example \#2]) - D.1.1.bc) Compass glitch (#formatLink("https://youtu.be/fQi1dOHEYLg")[Example]) +- D.1.1.bd) Unbreakable Fishing Line / Lead with Dimension Change (#formatLink("https://youtu.be/uxLNbGshih0")[Example], #formatLink("https://youtu.be/wh_tW3lVbuY")[Example \#2]) D.1.2) Any other glitches not included in D.1.1 must not be used during glitchless runs. - Examples of glitches that are not allowed include but are not limited to: - D.1.2.a) Duplication and zero-stack glitches (#formatLink("https://youtu.be/PYFMGuicVWA&t=102")[Example]) From 95e3401bbdbdcf82e9f83a8447d9d77793b9353c Mon Sep 17 00:00:00 2001 From: tildejustin Date: Fri, 13 Feb 2026 19:57:33 -0500 Subject: [PATCH 05/26] explicitly allow modified elytra shape of official capes if using those capes, #106 and #204 --- rules.typ | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/rules.typ b/rules.typ index ee9b828..f2b151a 100644 --- a/rules.typ +++ b/rules.typ @@ -164,7 +164,7 @@ A.1.4) The options.txt file must not be altered to circumvent the bounds to the - A.1.4.d) Exception: tutorialStep may be altered. A.1.5) The game's code and files must not be altered to produce any unfair advantage or significant deviation in gameplay. - A.1.5.a) Clarification: Changing capes and skins (including high resolution/dimension capes) in the launcher assets cache is allowed. Skins must not be transparent. Elytra shape must not be changed. - - A.1.5.a.i) Exception: The “Cobalt” elytra texture may be used. + - A.1.5.a.i) Guidance: Several officially released capes change the shape of the elytra. These custom elytra textures/shapes may be used if and only if their respective capes are also used. - A.1.6) The name of hardware components, such as the CPU, must not be altered. == A.2: Videos From ac644be596f0c2762f0c9b4604f3f48263d8cc2b Mon Sep 17 00:00:00 2001 From: tildejustin Date: Fri, 13 Feb 2026 19:58:56 -0500 Subject: [PATCH 06/26] better name for the nether portal desync, #143 take 2 --- rules.typ | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/rules.typ b/rules.typ index f2b151a..e894049 100644 --- a/rules.typ +++ b/rules.typ @@ -670,8 +670,8 @@ D.1.2) Any other glitches not included in D.1.1 must not be used during glitchle - D.1.2.ab) Saving blocks by lag abuse (#formatLink("https://youtu.be/qhvBNctnJCk")[Example]) - D.1.2.ac) Shared hitbox abuse (#formatLink("https://youtu.be/aPtvSnMLmnI")[Example], #formatLink("https://youtu.be/X6F-eq1-QLE")[Example \#2], #formatLink("https://youtu.be/JRYuWzPLQeY")[Example \#3]) - D.1.2.ad) Teleporting via a pearl with nether portal (#formatLink("https://youtu.be/g5knWZnrmbM")[Example]) -- D.1.2.af) Using a nether portal without the portal animation (#formatLink("https://youtu.be/IUf07boL9Ac&t=60")[Example]) - D.1.2.ae) Boat desync (#formatLink("https://bugs.mojang.com/browse/MC/issues/MC-205477")[MC-205477], #formatLink("https://youtu.be/MUuVgMxUfcA")[Example], #formatLink("https://youtu.be/k0-6v85TprA")[Example \#2]) +- D.1.2.af) Using server-client position desync to wait in a portal without the portal animation (#formatLink("https://youtu.be/IUf07boL9Ac&t=60")[Example]) D.1.3) Save and quit must not be used during a run. - D.1.3.a) Exception: If you accidentally use Save and Quit within a run, it may still be verified (at the discretion of verifiers) if it is accidental, attempts are made to rejoin the initial world relatively quickly, and if it provides no additional benefit to the run. - D.1.3.b) Exception: Runners may Save and Quit within a run intentionally if and only if there is a relevant bug (at the discretion of verifiers) which can be resolved by saving and quitting (e.g. pie chart bug, ghost blocks, resetting fog, restarting autosave timer to avoid leads breaking). No additional benefit may be gained. From 37a7ec38b94da59dea2262e180fadf8140f42725 Mon Sep 17 00:00:00 2001 From: tildejustin Date: Fri, 13 Feb 2026 20:08:19 -0500 Subject: [PATCH 07/26] generalized segmenting rules, #129 --- rules.typ | 37 +++++++++++++++++++------------------ 1 file changed, 19 insertions(+), 18 deletions(-) diff --git a/rules.typ b/rules.typ index e894049..553c409 100644 --- a/rules.typ +++ b/rules.typ @@ -172,7 +172,7 @@ A.2.1) All runs must be submitted with a video of the run.\ A.2.2) The video of the run must be continuous; it cannot be segmented or not display the run for a duration of time. - A.2.2.a) If your video is discontinuous due to an error with your hardware or video recording software, the run may still be verified (at the discretion of verifiers). In this situation, you should open a thread. #entangled[Entangled Rule(s):]\ -#entangled[A.2.2 is nullified by: ] #entangledRule("4.1.2")\ +#entangled[A.2.2 is nullified by: ] #entangledRule("A.5.19")\ A.2.3) Your video must be permanently available. - This excludes but is not limited to: - A.2.3.a) Twitch VODs and clips @@ -310,7 +310,6 @@ A.5.7) If lag occurs, which causes a portion of the game to revert back to a pre A.5.8) If lag occurs in the run, where some actions are impossible to perform while other actions are, the time may or may not contribute towards in-game time (at the discretion of verifiers), depending on if other fundamental processes are still occurring or if the action that cannot be performed is crucial to the run.\ A.5.9) If lag slows down the entire run, as is often present within the first few seconds of loading a world in older versions, the extra time will contribute towards in-game time if the run is manually retimed. - A.5.9.a) Clarification: If this lag occurs and SpeedrunIGT is used, the extra time spent will be accounted for and subtracted from the in-game time. -A.5.10) If a run is segmented, then time spent between the segments of the run will not contribute to in-game time or the real time of the run.\ A.5.11) If a run meets the criteria for a top-level retime, pauses contribute to in-game time except for the following circumstances: - A.5.11.a) Pauses that occur directly after or close to after (at the discretion of verifiers) a significant amount of chunks of a dimension are loaded for the first time and do not contribute towards in-game time. - A.5.11.b) Pauses that change settings and are less than 5 seconds do not contribute to in-game time. If this is done abusively (at the discretion of verifiers), these pauses will contribute towards in-game time. @@ -345,6 +344,19 @@ A.5.18) If a run ends by obtaining item(s), timing ends once the first "CE13.1.1.a", "CE18.1.1.a", ))\ +A.5.19) Segmenting, pausing the speedrun for a time by quitting the world and ending the recording, is allowed in a few categories. Segmenting suspends both #entangledRule("A.2.2") and #entangledRule("D.1.3") if and only if the following requirements are met: +- A.5.19.a) You must have the included video(s) show you exiting the world each time you do so. +- A.5.19.b) You must have the included video(s) show you re-entering the world each time you do so. +- A.5.19.c) In between segments of the current run, you must not play anything other than the current run on the instance that the current run is on. +- #entangled[Entangled Rule(s):]\ +- #entangled[A.5.19.c is referenced by: ] #entangledRule("6.1.1.a")\ +- A.5.19.d) You must submit log files. +- #entangled[Entangled Rule(s):]\ +- #entangled[A.5.19.d is referenced by: ] #entangledRule("6.1.1.b")\ +- A.5.19.e) Clarification: For glitchless runs, the segmentation must not provide any additional benefit to the run. +- A.5.19.f) Time spent between the segments of the run will not contribute to in-game time or the real time of the run. +#entangled[Entangled Rule(s):]\ +#entangled[A.5.19 is referenced by: ] #entangledRules("4.1.2", "CE19.3.4")\ == A.6: General Submission Rules A.6.1) The run's speedrun.com submission description must include the seed of the world. @@ -677,7 +689,7 @@ D.1.3) Save and quit must not be used during a run. - D.1.3.b) Exception: Runners may Save and Quit within a run intentionally if and only if there is a relevant bug (at the discretion of verifiers) which can be resolved by saving and quitting (e.g. pie chart bug, ghost blocks, resetting fog, restarting autosave timer to avoid leads breaking). No additional benefit may be gained. - D.1.3.c) If a Save and Quit is deemed as permissible and the run qualifies for a top-level retime, any time spent outside of the world will be included in the in-game time, but any time spent waiting for loads will not be included in the in-game time. #entangled[Entangled Rule(s):]\ -#entangled[D.1.3 is subject to an amendment by: ] #entangledRule("4.1.4")\ +#entangled[D.1.3 is subject to an amendment by: ] #entangledRule("A.5.19")\ #entangled[D.1.3 is referenced by: ] #entangledRules(("E.3.1", "E.4.1.a"))\ D.1.4) The game must not be closed and reopened during a run. - D.1.4.a) Exception: If the game closes, whether by crashing or otherwise, it may still be verified (at the discretion of verifiers) if it is accidental, attempts are made to rejoin the initial world relatively quickly, and if it minimally affects the run. @@ -885,20 +897,9 @@ H.1.2) In set seed runs, intentional prerotation (spawning into the world rotate #entangled[4.1 is referenced by: ] #entangledRules(("3.1.1", "6.1.1"))\ 4.1.1) The run is considered complete once every advancement has been achieved. - 4.1.1.a) Timing ends once the chat notification for the last advancement is shown. -4.1.2) <4.1.2> A runner may segment their run, thereby excepting both #entangledRule("A.2.2") and #entangledRule("D.1.3"), if and only if the following pretences are met: -- 4.1.2.a) You must have the included video(s) show you exiting the world each time you do so. -- 4.1.2.b) You must have the included video(s) show you re-entering the world each time you do so. -- 4.1.2.c) <4.1.2.c> In between segments of the current run, you must not play anything other than the current run on the instance that the current run is on. -- #entangled[Entangled Rule(s):]\ -- #entangled[4.1.2.c is referenced by: ] #entangledRule("6.1.1.a")\ -- 4.1.2.d) <4.1.2.d> You must submit log files. -- #entangled[Entangled Rule(s):]\ -- #entangled[4.1.2.d is referenced by: ] #entangledRule("6.1.1.b")\ -- 4.1.2.e) Clarification: For glitchless runs, the segmentation must not provide any additional benefit to the run. -#entangled[Entangled Rule(s):]\ -#entangled[4.1.2 is referenced by: ] #entangledRule("CE19.3.4")\ 4.1.3) All runs must submit world files.\ 4.1.4) <4.1.4> All runs begin on world load. +4.1.2) <4.1.2> A runner may segment their run if and only if they follow the rules regarding segmentation as outlined by #entangledRule("A.5.19") and its corresponding sub-rules. == 4.2: SS/SSG/RS/RSG, 1.12 4.2.1) The list of all advancements necessary to obtain are: Minecraft, Stone Age, Getting an Upgrade, Acquire Hardware, Suit Up, Hot Stuff, Isn't It Iron Pick, Not Today, Thank You, Ice Bucket Challenge, Diamonds!, We Need to Go Deeper, Cover Me With Diamonds, Enchanter, Zombie Doctor, Eye Spy, The End?, Husbandry, The Parrots and the Bats, Best Friends Forever, A Seedy Place, Two by Two, A Balanced Diet, Serious Dedication, Adventure, Monster Hunter, What a Deal!, Sweet Dreams, Take Aim, Monsters Hunted, Postmortal, Hired Help, Adventuring Time, Sniper Duel, Nether, Return to Sender, Subspace Bubble, A Terrible Fortress, Uneasy Alliance, Spooky Scary Skeleton, Into Fire, Withering Heights, Local Brewery, Bring Home the Beacon, A Furious Cocktail, Beaconator, How Did We Get Here?, The End, Free the End, The Next Generation, Remote Getaway, The End... Again..., You Need a Mint, The City at the End of the Game, Sky's the Limit, and Great View From Up Here. @@ -961,8 +962,8 @@ H.1.2) In set seed runs, intentional prerotation (spawning into the world rotate == 6.1: All Advancements Co-op Objective and Clarifications 6.1.1) <6.1.1> The objective, exceptions, and clarifications of All Advancements Co-op are identical to those of All Advancements (see section #entangledRule("4.1")). -- 6.1.1.a) <6.1.1.a> If the run is segmented, rather than not playing on the instance between segments (#entangledRule("4.1.2.c")), the server folder must not be played between segments. -- 6.1.1.b) <6.1.1.b> If the run is segmented, you must submit server logs instead of instance logs (#entangledRule("4.1.2.d")). +- 6.1.1.a) <6.1.1.a> If the run is segmented, rather than not playing on the instance between segments (#entangledRule("A.5.19.c")), the server folder must not be played between segments. +- 6.1.1.b) <6.1.1.b> If the run is segmented, you must submit server logs instead of instance logs (#entangledRule("A.5.19.d")). 6.1.2) Clarification: Each advancement must be achieved by at least one person, but no individual person needs every advancement.\ 6.1.3) <6.1.3> The list of all advancements is the same as for All Advancements (see #entangledRule("4.6.1") and #entangledRule("4.7.1")).\ 6.1.4) Clarification: There are no specific subcategory rules; thus, runs should only follow their respective rulesets (universal, random seed, glitchless, co-op). @@ -1315,7 +1316,7 @@ CE19.3.3) In addition to the external tools allowed by #entangledRule("A.11"), t - CE19.3.3.a) #formatLink("https://github.com/TheTalkingMime/AllPortals")[All Portals [TheTalkingMime]] - CE19.3.3.b) #formatLink("https://github.com/shnenanigans/APgui")[APgui [shnenanigans]] - CE19.3.3.c) #formatLink("https://www.desmos.com/calculator/la7ezpyutu")[Desmos Stronghold Rings] -CE19.3.4) A runner may segment their run if and only if they follow the rules regarding segmentation as outlined by #entangledRule("4.1.2") and its corresponding sub-rules. +CE19.3.4) A runner may segment their run if and only if they follow the rules regarding segmentation as outlined by #entangledRule("A.5.19") and its corresponding sub-rules. == CE19.4: All Portals Purist CE19.4.1) Purist runs must be played on random seed glitchless.\ From c7115bd447d83705fae2e9fa4b85da4a0520aae3 Mon Sep 17 00:00:00 2001 From: tildejustin Date: Fri, 13 Feb 2026 20:16:34 -0500 Subject: [PATCH 08/26] lowered standard of proof and implemented top level files requirement for aa, various other aa and half% refactoring, #190 and from discussion --- rules.typ | 26 ++++++++++++++------------ 1 file changed, 14 insertions(+), 12 deletions(-) diff --git a/rules.typ b/rules.typ index 553c409..aaa78de 100644 --- a/rules.typ +++ b/rules.typ @@ -897,9 +897,16 @@ H.1.2) In set seed runs, intentional prerotation (spawning into the world rotate #entangled[4.1 is referenced by: ] #entangledRules(("3.1.1", "6.1.1"))\ 4.1.1) The run is considered complete once every advancement has been achieved. - 4.1.1.a) Timing ends once the chat notification for the last advancement is shown. -4.1.3) All runs must submit world files.\ -4.1.4) <4.1.4> All runs begin on world load. 4.1.2) <4.1.2> A runner may segment their run if and only if they follow the rules regarding segmentation as outlined by #entangledRule("A.5.19") and its corresponding sub-rules. +4.1.3) <4.1.3> Runs must demonstrate all advancements have been obtained. +- This constitutes at least one of the following: +- 4.1.2.a) The advancement file from the world is submitted. +- 4.1.2.b) World files are submitted. +- 4.1.2.c) An advancement tracker is displayed the count of advancements have been completed. +- 4.1.2.d) SpeedRunIGT is set to the right category and autostops. +#entangled[Entangled Rule(s):]\ +#entangled[4.1.3 is referenced by: ] #entangledRule("CE24.1.2")\ +4.1.4) All runs begin on world load. == 4.2: SS/SSG/RS/RSG, 1.12 4.2.1) The list of all advancements necessary to obtain are: Minecraft, Stone Age, Getting an Upgrade, Acquire Hardware, Suit Up, Hot Stuff, Isn't It Iron Pick, Not Today, Thank You, Ice Bucket Challenge, Diamonds!, We Need to Go Deeper, Cover Me With Diamonds, Enchanter, Zombie Doctor, Eye Spy, The End?, Husbandry, The Parrots and the Bats, Best Friends Forever, A Seedy Place, Two by Two, A Balanced Diet, Serious Dedication, Adventure, Monster Hunter, What a Deal!, Sweet Dreams, Take Aim, Monsters Hunted, Postmortal, Hired Help, Adventuring Time, Sniper Duel, Nether, Return to Sender, Subspace Bubble, A Terrible Fortress, Uneasy Alliance, Spooky Scary Skeleton, Into Fire, Withering Heights, Local Brewery, Bring Home the Beacon, A Furious Cocktail, Beaconator, How Did We Get Here?, The End, Free the End, The Next Generation, Remote Getaway, The End... Again..., You Need a Mint, The City at the End of the Game, Sky's the Limit, and Great View From Up Here. @@ -916,12 +923,11 @@ H.1.2) In set seed runs, intentional prerotation (spawning into the world rotate == 4.6: SS/SSG/RS/RSG, 1.16 4.6.1) <4.6.1> The list of all advancements necessary to obtain are: Minecraft, Stone Age, Getting an Upgrade, Acquire Hardware, Suit Up, Hot Stuff, Isn't It Iron Pick, Not Today, Thank You, Ice Bucket Challenge, Diamonds!, We Need to Go Deeper, Cover Me With Diamonds, Enchanter, Zombie Doctor, Eye Spy, The End?, Husbandry, The Parrots and the Bats, Best Friends Forever, A Seedy Place, Two by Two, A Balanced Diet, Serious Dedication, Adventure, Monster Hunter, What a Deal!, Sweet Dreams, Take Aim, Monsters Hunted, Postmortal, Hired Help, Adventuring Time, Sniper Duel, Nether, Return to Sender, Subspace Bubble, A Terrible Fortress, Uneasy Alliance, Spooky Scary Skeleton, Into Fire, Withering Heights, Local Brewery, Bring Home the Beacon, A Furious Cocktail, Beaconator, How Did We Get Here?, The End, Free the End, The Next Generation, Remote Getaway, The End... Again..., You Need a Mint, The City at the End of the Game, Sky's the Limit, Great View From Up Here, Fishy Business, Tactical Fishing, A Throwaway Joke, Very Very Frightening, Ol' Betsy, Who's the Pillager Now?, Two Birds One Arrow, Arbalistic, A Complete Catalogue, Voluntary Exile, Hero of the Village, Sticky Situation, Bee Our Guest, Total Beelocation, Those Were the Days, Hidden in the Depths, Who Is Cutting Onions?, Oh Shiny, This Boat Has Legs, War Pigs, Country Lode Take Me Home, Cover Me in Debris, Not Quite “Nine” Lives, Hot Tourist Destinations, and Bullseye. #entangled[Entangled Rule(s):]\ -#entangled[4.6.1 is referenced by: ] #entangledRules(("6.1.3", "CE24.1.1"))\ +#entangled[4.6.1 is referenced by: ] #entangledRule("CE24.1.1")\ +4.6.2: RSG runs under 3:00:00 must submit world files and logs. == 4.7: SS/SSG/RS/RSG, 1.17 -4.7.1) <4.7.1> The list of all advancements necessary to obtain are: Minecraft, Stone Age, Getting an Upgrade, Acquire Hardware, Suit Up, Hot Stuff, Isn't It Iron Pick, Not Today, Thank You, Ice Bucket Challenge, Diamonds!, We Need to Go Deeper, Cover Me With Diamonds, Enchanter, Zombie Doctor, Eye Spy, The End?, Husbandry, The Parrots and the Bats, Best Friends Forever, A Seedy Place, Two by Two, A Balanced Diet, Serious Dedication, Adventure, Monster Hunter, What a Deal!, Sweet Dreams, Take Aim, Monsters Hunted, Postmortal, Hired Help, Adventuring Time, Sniper Duel, Nether, Return to Sender, Subspace Bubble, A Terrible Fortress, Uneasy Alliance, Spooky Scary Skeleton, Into Fire, Withering Heights, Local Brewery, Bring Home the Beacon, A Furious Cocktail, Beaconator, How Did We Get Here?, The End, Free the End, The Next Generation, Remote Getaway, The End... Again..., You Need a Mint, The City at the End of the Game, Sky's the Limit, Great View From Up Here, Fishy Business, Tactical Fishing, A Throwaway Joke, Very Very Frightening, Ol' Betsy, Who's the Pillager Now?, Two Birds One Arrow, Arbalistic, A Complete Catalogue, Voluntary Exile, Hero of the Village, Sticky Situation, Bee Our Guest, Total Beelocation, Those Were the Days, Hidden in the Depths, Who Is Cutting Onions?, Oh Shiny, This Boat Has Legs, War Pigs, Country Lode Take Me Home, Cover Me in Debris, Not Quite “Nine” Lives, Hot Tourist Destinations, Bullseye, Whatever Floats Your Goat, Wax On, Wax Off, The Cutest Predator, The Healing Power of Friendship, Glow and Behold!, Light as a Rabbit, Surge Protector, Is It a Bird?, Is It a Balloon?, and Is It a Plane?\ -#entangled[Entangled Rule(s):]\ -#entangled[4.7.1 is referenced by: ] #entangledRule("6.1.3")\ +4.7.1) The list of all advancements necessary to obtain are: Minecraft, Stone Age, Getting an Upgrade, Acquire Hardware, Suit Up, Hot Stuff, Isn't It Iron Pick, Not Today, Thank You, Ice Bucket Challenge, Diamonds!, We Need to Go Deeper, Cover Me With Diamonds, Enchanter, Zombie Doctor, Eye Spy, The End?, Husbandry, The Parrots and the Bats, Best Friends Forever, A Seedy Place, Two by Two, A Balanced Diet, Serious Dedication, Adventure, Monster Hunter, What a Deal!, Sweet Dreams, Take Aim, Monsters Hunted, Postmortal, Hired Help, Adventuring Time, Sniper Duel, Nether, Return to Sender, Subspace Bubble, A Terrible Fortress, Uneasy Alliance, Spooky Scary Skeleton, Into Fire, Withering Heights, Local Brewery, Bring Home the Beacon, A Furious Cocktail, Beaconator, How Did We Get Here?, The End, Free the End, The Next Generation, Remote Getaway, The End... Again..., You Need a Mint, The City at the End of the Game, Sky's the Limit, Great View From Up Here, Fishy Business, Tactical Fishing, A Throwaway Joke, Very Very Frightening, Ol' Betsy, Who's the Pillager Now?, Two Birds One Arrow, Arbalistic, A Complete Catalogue, Voluntary Exile, Hero of the Village, Sticky Situation, Bee Our Guest, Total Beelocation, Those Were the Days, Hidden in the Depths, Who Is Cutting Onions?, Oh Shiny, This Boat Has Legs, War Pigs, Country Lode Take Me Home, Cover Me in Debris, Not Quite “Nine” Lives, Hot Tourist Destinations, Bullseye, Whatever Floats Your Goat, Wax On, Wax Off, The Cutest Predator, The Healing Power of Friendship, Glow and Behold!, Light as a Rabbit, Surge Protector, Is It a Bird?, Is It a Balloon?, and Is It a Plane?\ == 4.8: SS/SSG/RS/RSG, 1.18 4.8.1) The list of all advancements necessary to obtain are: Minecraft, Stone Age, Getting an Upgrade, Acquire Hardware, Suit Up, Hot Stuff, Isn't It Iron Pick, Not Today, Thank You, Ice Bucket Challenge, Diamonds!, We Need to Go Deeper, Cover Me With Diamonds, Enchanter, Zombie Doctor, Eye Spy, The End?, Husbandry, The Parrots and the Bats, Best Friends Forever, A Seedy Place, Two by Two, A Balanced Diet, Serious Dedication, Adventure, Monster Hunter, What a Deal!, Sweet Dreams, Take Aim, Monsters Hunted, Postmortal, Hired Help, Adventuring Time, Sniper Duel, Nether, Return to Sender, Subspace Bubble, A Terrible Fortress, Uneasy Alliance, Spooky Scary Skeleton, Into Fire, Withering Heights, Local Brewery, Bring Home the Beacon, A Furious Cocktail, Beaconator, How Did We Get Here?, The End, Free the End, The Next Generation, Remote Getaway, The End... Again..., You Need a Mint, The City at the End of the Game, Sky's the Limit, Great View From Up Here, Fishy Business, Tactical Fishing, A Throwaway Joke, Very Very Frightening, Ol' Betsy, Who's the Pillager Now?, Two Birds One Arrow, Arbalistic, A Complete Catalogue, Voluntary Exile, Hero of the Village, Sticky Situation, Bee Our Guest, Total Beelocation, Those Were the Days, Hidden in the Depths, Who Is Cutting Onions?, Oh Shiny, This Boat Has Legs, War Pigs, Country Lode Take Me Home, Cover Me in Debris, Not Quite “Nine” Lives, Hot Tourist Destinations, Bullseye, Whatever Floats Your Goat, Wax On, Wax Off, The Cutest Predator, The Healing Power of Friendship, Glow and Behold!, Light as a Rabbit, Surge Protector, Is It a Bird?, Is It a Balloon?, Is It a Plane?, Caves and Cliffs, Feels like home, Star Trader, and Sound of Music. @@ -965,7 +971,7 @@ H.1.2) In set seed runs, intentional prerotation (spawning into the world rotate - 6.1.1.a) <6.1.1.a> If the run is segmented, rather than not playing on the instance between segments (#entangledRule("A.5.19.c")), the server folder must not be played between segments. - 6.1.1.b) <6.1.1.b> If the run is segmented, you must submit server logs instead of instance logs (#entangledRule("A.5.19.d")). 6.1.2) Clarification: Each advancement must be achieved by at least one person, but no individual person needs every advancement.\ -6.1.3) <6.1.3> The list of all advancements is the same as for All Advancements (see #entangledRule("4.6.1") and #entangledRule("4.7.1")).\ +6.1.3) The list of all advancements is the same as for All Advancements.\ 6.1.4) Clarification: There are no specific subcategory rules; thus, runs should only follow their respective rulesets (universal, random seed, glitchless, co-op). = 7: Any% Glitchless (Demo) @@ -1379,11 +1385,7 @@ CE23.1.3) All runs begin upon first input. == CE24.1: Half% Objective and Clarifications CE24.1.1) The run is considered complete once exactly 40 advancements, as listed in #entangledRule("4.6.1"), have been obtained. - CE24.1.1.a) Timing ends once the chat notification for the last advancement is shown. -CE24.1.2) Runs must show that 40 advancements have been obtained. -- This constitutes at least one of the following: -- CE24.1.2.a) Scrolling through the advancements list until 40 advancements have been displayed as completed. -- CE24.1.2.b) World files are submitted. -- CE24.1.2.c) An advancement tracker is displayed that shows 40 advancements have been completed. +CE24.1.2) Runs must demonstrate that 40 advancements have been obtained in accordance with #entangledRule("4.1.3"). CE24.1.3) Clarification: There are no specific subcategory rules; thus, runs should only follow their respective rulesets (universal, set seed/random seed, glitchless/glitched).\ CE24.1.4) All random seed categories begin upon world load, whereas all set seed categories begin upon first input. From 4d835e5827acef3dc782ab5708ee8f69e2cffb30 Mon Sep 17 00:00:00 2001 From: tildejustin Date: Fri, 13 Feb 2026 20:19:19 -0500 Subject: [PATCH 09/26] ninbot api blanket restrictions, #188 --- rules.typ | 1 + 1 file changed, 1 insertion(+) diff --git a/rules.typ b/rules.typ index aaa78de..f4a3519 100644 --- a/rules.typ +++ b/rules.typ @@ -529,6 +529,7 @@ A.11.6) The following constitute the whitelist of other legal sheets: - A.11.6.g) #formatLink("https://docs.google.com/spreadsheets/d/1tTXczjzo4VCOxV2dpkj-SE5cELA9A2NyreRiQj6Bu8I/edit?gid=1217206013#gid=1217206013")[Nether Portal Orientation Divine Sheet] A.11.7) The following constitute the whitelist of legal tools: - A.11.7.a) #formatLink("https://github.com/Ninjabrain1/Ninjabrain-Bot")[NinjabrainBot] [Ninjabrain1] (up to v1.5.1) + - A.11.7.a.i) The NinjabrainBot API may be legally used by other tools for display of provided data, without any additional calculations or modifications that may provide any interpretation of the data which is not otherwise possible with an unmodified copy of NinjabrainBot. - A.11.7.b) #formatLink("https://github.com/pjagada/strongholdnotcalculator")[StrongholdNotCalculator] [pjagada] (up to v2.0) - A.11.7.c) #formatLink("https://github.com/FourGoesFast/PerfectTravelBot")[PerfectTravelBot] [FourGoesFast] (up to v1.0.0) - A.11.7.e) #formatLink("https://github.com/KingContaria/ContariaCalc/releases")[ContariaCalc] [KingContaria] (up to v1.1.7.1) From ec54e3ad3b009f0c39c0f73ebb1c77199627e6f7 Mon Sep 17 00:00:00 2001 From: tildejustin Date: Fri, 13 Feb 2026 20:19:51 -0500 Subject: [PATCH 10/26] allow wood and stripped wood in all logs, #209 --- rules.typ | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/rules.typ b/rules.typ index f4a3519..0589176 100644 --- a/rules.typ +++ b/rules.typ @@ -1156,9 +1156,9 @@ CE8.3.1) The run is considered complete once a wood sword, stone sword, iron swo = CE9: All Wood Logs == CE9.1: All Wood Logs Objective and Clarifications -CE9.1.1) The run is considered complete once all logs have been simultaneously obtained. +CE9.1.1) The run is considered complete once logs for all tree types have been simultaneously obtained. - CE9.1.1.a) Timing ends once the last log is obtained. (see #entangledRule("A.5.18"))\ -- CE9.1.1.b) Clarification: Stripped logs qualify as logs, but do not need to be simultaneously obtained. +- CE9.1.1.b) Clarification: Logs, stripped logs, wood, and stripped wood all qualify as log variants, but do not need to be simultaneously obtained. CE9.1.2) All random seed categories begin upon world load, whereas all set seed categories begin upon first input.\ #entangled[Entangled Rule(s):]\ #entangled[CE9.1.2 is nullified by: ] #entangledRules(("CE9.2.2", "CE9.3.2"))\ From 1f107df645c1de1d914a40e01bd3c30bdc186aa8 Mon Sep 17 00:00:00 2001 From: tildejustin Date: Fri, 13 Feb 2026 20:20:24 -0500 Subject: [PATCH 11/26] allow /publish (added in newer versions), #210 --- rules.typ | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/rules.typ b/rules.typ index 0589176..89db2f0 100644 --- a/rules.typ +++ b/rules.typ @@ -218,7 +218,7 @@ A.3.3) You must not open to LAN during the run.\ A.3.4) Your world must not be corrupted significantly (at the discretion of verifiers).\ A.3.5) You must not use console commands during the run.\ #entangled[Entangled Rule(s):]\ -#entangled[A.3.5 is nullified by: ] #entangledRules(("F.1.3.a", "F.1.3.b", "CE20.1.2"))\ +#entangled[A.3.5 is nullified by: ] #entangledRules(("F.1.3.a", "F.1.3.b", "F.1.3.c", "CE20.1.2"))\ A.3.6) If you play one instance of Minecraft and then switch to playing another, the initial instance's run is no longer verifiable. If this is done accidentally, and attempts are made to quickly exit the other instance and rejoin the initial instance, your run may still be verified (at the discretion of verifiers). - A.3.6.a) Clarification: While one instance of Minecraft is played, you may pause or close other instances. A.3.7) Non-default shaders, including Super Secret Settings, must not be used.\ @@ -736,6 +736,7 @@ F.1.3) No cheats or actions which could not be accomplished without cheats must - F.1.3.a) Exception: /difficulty may be used, nullifying #entangledRule("A.3.5") (note that in accordance with #entangledRule("A.3.11"), the difficulty must not be set to peaceful, even if toggling between difficulties) - F.1.3.b) Exception: /time set 0 may be used as described in #entangledRule("F.2.2"), nullifying #entangledRule("A.3.5"). F.1.4) Players with cheats enabled must not use F3+I.\ +- F.1.3.c) Exception: /publish may be used, nullifying #entangledRule("A.3.5"). F.1.5) The entirety of a co-op run must occur on either an dedicated server or with Open to LAN. - F.1.5.a) Exception: The very start (at the discretion of verifiers) of a run may be played on singleplayer. F.1.6) If more than 16 players are running, choose 16 players while submitting, input the names of 15 of the players, and then list “+others” for the 16th slot. Include the name of all other players not listed in the description of the speedrun.com submission.\ From edda3b8be0cd10b9e598e953dc572fe48a926478 Mon Sep 17 00:00:00 2001 From: tildejustin Date: Fri, 13 Feb 2026 20:21:21 -0500 Subject: [PATCH 12/26] mention elder guardian curse removal as a blanketly allowed a11y change, #211 --- rules.typ | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/rules.typ b/rules.typ index 89db2f0..fbaa045 100644 --- a/rules.typ +++ b/rules.typ @@ -238,11 +238,12 @@ A.3.11) Peaceful difficulty must not be used within the run.\ == A.4: Resource Packs A.4.1) The vanilla resource pack, programmer art (1.14+), and High Contrast (1.19.4+) packs may be used.\ -A.4.2) Resource packs that are whitelisted for accessibility purposes (including but not limited to sensory issues or colourblindness) may be used. +A.4.2) Resource packs and resource changes that are whitelisted for accessibility purposes (including but not limited to sensory issues or colourblindness) may be used. - This constitutes: - A.4.2.a) #formatLink("https://github.com/dysphorLia/SensoryFriendlyResourcePack")[dysphorLia's Sensory Friendly Resource Pack] - A.4.2.b) #formatLink("https://github.com/shnenanigans/quieter-mc-sounds")[shenanigans' Quieter Sounds Resource Pack] -- A.4.2.c) If you need an accommodation that is not covered by the packs listed above, please open a thread. You may be whitelisted to play with a resource pack which is otherwise not allowed. +- A.4.2.c) If you need an accommodation that is not covered by the cases listed here, please open a thread. You may be whitelisted to play with a resource pack which is otherwise not allowed. +- A.4.2.d) Removing the Elder Guardian curse sound. A.4.3) Non-accessibility resource packs may be used if and only if they only modify the following resources under the following circumstances and do so in a way wherein a competitive advantage is not attained. - The textures that can be modified constitute: - A.4.3.a) Using the 1.14+ netherrack texture on older versions/in programmer art From daff15ecf5b29755f97e7b3526414577cfc59944 Mon Sep 17 00:00:00 2001 From: tildejustin Date: Fri, 13 Feb 2026 20:22:16 -0500 Subject: [PATCH 13/26] clarify that gui background includes dirt background for purposes of allowed gui resource packs --- rules.typ | 1 + 1 file changed, 1 insertion(+) diff --git a/rules.typ b/rules.typ index fbaa045..1e9f4c8 100644 --- a/rules.typ +++ b/rules.typ @@ -252,6 +252,7 @@ A.4.3) Non-accessibility resource packs may be used if and only if they only mod - A.4.3.d) Changing the Ender Dragon's death sound and sound volume - A.4.3.e) Changing the bossbar text - A.4.3.f) Changing the colour scheme of the GUI background to a non-transparent solid colour or colour gradient +- A.4.3.f.i) Clarification: The GUI background includes the options background texture, commonly known as the dirt background. - A.4.3.g) Changing the chest and trapped chest textures to their Christmas variants - A.4.3.h) Changing the default Player skin or cape texture. - A.4.3.i) Clarification: You must not modify the textures of the health bar, hunger bar, or XP bar whatsoever. From 282a246513203aac859fa06d5212049372ae93cb Mon Sep 17 00:00:00 2001 From: tildejustin Date: Fri, 13 Feb 2026 20:22:27 -0500 Subject: [PATCH 14/26] a.7.8.a typo --- rules.typ | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/rules.typ b/rules.typ index 1e9f4c8..54b6ae3 100644 --- a/rules.typ +++ b/rules.typ @@ -401,7 +401,7 @@ A.7.6) Logs refer to the .log/.gz file in the .minecraft/logs folder. Th #entangled[A.7.6 is referenced by: ] #entangledRule("A.3.1.b")\ A.7.7) Evidence of past attempts refers to videos of previously completed runs, nearly completed runs, practice sessions, or session videos. These should be in the same category of the run.\ A.7.8) 5 previous world files does not include the world files of the submitted run: this will generally mean you submit 6 world files in total. These should be from the same instance. -- A.7.8.a) If SeedQueue is used and 5 previous world files must be sent, all world files generated after the run must also be submitted. +- A.7.8.a) If SeedQueue is used and 5 previous world files must be sent, all world files generated after the run must also be submitted. A.7.9) Gameplay audio may be submitted either through the main submission video or a linked separate video. The entire run's audio should be included.\ A.7.10) In the rare circumstance that a run must go through immediate moderator notifications, please open a thread and ping moderators by submitting a message with \@LeaderboardMod, with your Minecraft instances still open and while still recording.\ - A.7.10.a) Please do not ping Leaderboard Mods unless this is absolutely necessary for additional proof, as defined in Section 1.2.4. From 30a7e3d9ba033e16c9b44613826b7f7d2cbbe728 Mon Sep 17 00:00:00 2001 From: tildejustin Date: Fri, 13 Feb 2026 20:22:46 -0500 Subject: [PATCH 15/26] a.11.9.a include other cases that ninbot uses --- rules.typ | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/rules.typ b/rules.typ index 54b6ae3..5fb2b3d 100644 --- a/rules.typ +++ b/rules.typ @@ -544,7 +544,7 @@ A.11.8) You must not use any other reference sheets/external tools besi #entangled[Entangled Rule(s):]\ #entangled[A.11.8 is nullified by: ] #entangledRule("CE20.3.3")\ A.11.9) If you would like to use a tool/reference sheet that is not listed above, please open a thread. It may be allowed at the discretion of moderators. Please note: -- A.11.9.a) The tool must only use position, angle, and dimension from the F3 menu. +- A.11.9.a) The tool must only use position, angle, dimension, and client block and blockstate data from the F3 menu. - A.11.9.a.i) Clarification: This excludes biome and temperature. - A.11.9.b) If it is a code-based tool, its source code must be on a publicly accessible repository (e.g. GitHub). #entangled[Entangled Rule(s):]\ From ae81c96a5663f189dfb827e49d886480e46c6792 Mon Sep 17 00:00:00 2001 From: tildejustin Date: Fri, 13 Feb 2026 20:23:17 -0500 Subject: [PATCH 16/26] fix typo in and change wording a bit for allowed glitches note --- rules.typ | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/rules.typ b/rules.typ index 5fb2b3d..79bcd3f 100644 --- a/rules.typ +++ b/rules.typ @@ -594,7 +594,7 @@ C.2.1) Exception to #entangledRule("A.3.10") and #entangledRule("A.10.5" = D: Glitchless Ruleset == D.1: Glitchless Runs -#formatNote[D.1.note) Glitches are only allowed in glitchless on a case-by-case basis. What differentiates a glitch from a technique is nebulous, but is generally defined by if it can be done unintentionally. In terms of legalising a glitch, it is generally done by the mod team's discretion of how severely they stray from the “spirit of the game” as seen by the general Minecraft community, whether they make the speedruns more or less fun to play, and how easy it is to perform accidentally. In general, one should err on the side of caution in terms of if something is a glitch or a technique; it is highly encouraged to open a thread and ask if a technique quantifies as a glitch, and if not, if it will be allowed in glitchless runs.]\ +#formatNote[D.1.note) Glitches are only allowed in glitchless on a case-by-case basis. What differentiates a glitch from a technique is nebulous, but is generally defined by if it can be done unintentionally. In terms of legalising a glitch, it is generally done by the mod team's discretion of how severely they stray from the “spirit of the game” as seen by the general Minecraft community, whether they make the speedruns more or less fun to play, and how easy it is to perform accidentally. In general, one should err on the side of caution in terms of if something is a glitch or a technique; it is highly encouraged to open a thread and ask if a technique qualifies as a glitch and if it will be allowed in glitchless runs.]\ \ D.1.1) Only these glitches may be used during glitchless runs. - This constitutes: From 9f1856169ebb8194e6060aaf13facf2a11b0faa5 Mon Sep 17 00:00:00 2001 From: tildejustin Date: Fri, 13 Feb 2026 20:24:29 -0500 Subject: [PATCH 17/26] ban abusing double-ticking the player when being pushed out of a block, #122 --- rules.typ | 2 ++ 1 file changed, 2 insertions(+) diff --git a/rules.typ b/rules.typ index 79bcd3f..c15f6ed 100644 --- a/rules.typ +++ b/rules.typ @@ -687,6 +687,8 @@ D.1.2) Any other glitches not included in D.1.1 must not be used during glitchle - D.1.2.ad) Teleporting via a pearl with nether portal (#formatLink("https://youtu.be/g5knWZnrmbM")[Example]) - D.1.2.ae) Boat desync (#formatLink("https://bugs.mojang.com/browse/MC/issues/MC-205477")[MC-205477], #formatLink("https://youtu.be/MUuVgMxUfcA")[Example], #formatLink("https://youtu.be/k0-6v85TprA")[Example \#2]) - D.1.2.af) Using server-client position desync to wait in a portal without the portal animation (#formatLink("https://youtu.be/IUf07boL9Ac&t=60")[Example]) +- D.1.2.ag) Clipping into a block to tick the server player faster than normal (#formatLink("https://youtu.be/b4hS_LdSRbg")[Example]) + - D.1.2.ag.i) Clarification: When possible, enforcement of the ban on this glitch when applied to nether portals will consist of retiming. D.1.3) Save and quit must not be used during a run. - D.1.3.a) Exception: If you accidentally use Save and Quit within a run, it may still be verified (at the discretion of verifiers) if it is accidental, attempts are made to rejoin the initial world relatively quickly, and if it provides no additional benefit to the run. - D.1.3.b) Exception: Runners may Save and Quit within a run intentionally if and only if there is a relevant bug (at the discretion of verifiers) which can be resolved by saving and quitting (e.g. pie chart bug, ghost blocks, resetting fog, restarting autosave timer to avoid leads breaking). No additional benefit may be gained. From 8d5bd98491274bc20698def9f0c0c02713609c3d Mon Sep 17 00:00:00 2001 From: tildejustin Date: Fri, 13 Feb 2026 20:26:15 -0500 Subject: [PATCH 18/26] allow credits warp, #216 --- rules.typ | 1 + 1 file changed, 1 insertion(+) diff --git a/rules.typ b/rules.typ index c15f6ed..610d76f 100644 --- a/rules.typ +++ b/rules.typ @@ -689,6 +689,7 @@ D.1.2) Any other glitches not included in D.1.1 must not be used during glitchle - D.1.2.af) Using server-client position desync to wait in a portal without the portal animation (#formatLink("https://youtu.be/IUf07boL9Ac&t=60")[Example]) - D.1.2.ag) Clipping into a block to tick the server player faster than normal (#formatLink("https://youtu.be/b4hS_LdSRbg")[Example]) - D.1.2.ag.i) Clarification: When possible, enforcement of the ban on this glitch when applied to nether portals will consist of retiming. +- D.1.2.ah) Credits warp (#formatLink("https://youtu.be/Luwkl36rbTw")[Example]) D.1.3) Save and quit must not be used during a run. - D.1.3.a) Exception: If you accidentally use Save and Quit within a run, it may still be verified (at the discretion of verifiers) if it is accidental, attempts are made to rejoin the initial world relatively quickly, and if it provides no additional benefit to the run. - D.1.3.b) Exception: Runners may Save and Quit within a run intentionally if and only if there is a relevant bug (at the discretion of verifiers) which can be resolved by saving and quitting (e.g. pie chart bug, ghost blocks, resetting fog, restarting autosave timer to avoid leads breaking). No additional benefit may be gained. From efbe3392bdd51af07da9eff988a082edcfca4cba Mon Sep 17 00:00:00 2001 From: tildejustin Date: Fri, 13 Feb 2026 20:27:21 -0500 Subject: [PATCH 19/26] define cross-world glitches, ban in internal and say they are case-by-case --- rules.typ | 15 +++++++++++++-- 1 file changed, 13 insertions(+), 2 deletions(-) diff --git a/rules.typ b/rules.typ index 610d76f..73c0862 100644 --- a/rules.typ +++ b/rules.typ @@ -660,7 +660,9 @@ D.1.2) Any other glitches not included in D.1.1 must not be used during glitchle - D.1.2.c) X-Ray; minor unintentional x-rays may be verified, but intentional (or important but unintentional) x-rays (at the discretion of verifiers) must not be used (such as in this #formatLink("https://youtu.be/oImgrxw-v6I&t=688")[example]). - D.1.2.d) Shearing sheep during their dying animation (#formatLink("https://bugs.mojang.com/browse/MC-76416")[MC-76416]) - D.1.2.e) Nothing MLG (#formatLink("https://youtu.be/flt0V9QdfIQ")[Example]) -- D.1.2.h) Slime spectating (#formatLink("https://t.co/UErxU74UW1")[Example]) +- D.1.2.h) Slime spectating (#formatLink("https://t.co/UErxU74UW1")[Example]) +- #entangled[Entangled Rule(s):] +- #entangled[D.1.2.h is referenced by: ] #entangledRule("E.1.6.a") - D.1.2.i) Ghost block jump (#formatLink("https://youtu.be/A57pDR-mEuI")[Example]) - D.1.2.j) Offhand clutch (#formatLink("https://youtu.be/CHsV1iG2HbY")[Example]) - D.1.2.k) Dragon skip (#formatLink("https://youtu.be/MLwXclfyc8o")[Example]) @@ -690,6 +692,8 @@ D.1.2) Any other glitches not included in D.1.1 must not be used during glitchle - D.1.2.ag) Clipping into a block to tick the server player faster than normal (#formatLink("https://youtu.be/b4hS_LdSRbg")[Example]) - D.1.2.ag.i) Clarification: When possible, enforcement of the ban on this glitch when applied to nether portals will consist of retiming. - D.1.2.ah) Credits warp (#formatLink("https://youtu.be/Luwkl36rbTw")[Example]) +- #entangled[Entangled Rule(s):] +- #entangled[D.1.2.ah is referenced by: ] #entangledRule("E.1.6.b") D.1.3) Save and quit must not be used during a run. - D.1.3.a) Exception: If you accidentally use Save and Quit within a run, it may still be verified (at the discretion of verifiers) if it is accidental, attempts are made to rejoin the initial world relatively quickly, and if it provides no additional benefit to the run. - D.1.3.b) Exception: Runners may Save and Quit within a run intentionally if and only if there is a relevant bug (at the discretion of verifiers) which can be resolved by saving and quitting (e.g. pie chart bug, ghost blocks, resetting fog, restarting autosave timer to avoid leads breaking). No additional benefit may be gained. @@ -713,7 +717,13 @@ E.1.3) If you use Task Manager or another program which forcefully closes the ga E.1.4) External Arbitrary Code Execution (ACE) must not be used. - E.1.4.a) Example: Log4j exploit E.1.5) Glitched runs must be played entirely within one version.\ -E.1.6) World Merge must not be used (#formatLink("https://youtu.be/a-YhOtj6HmE")[Example]) +E.1.6) Cross-world glitches, or glitches that require setup in another world, are legalized on a case-by-case basis. +- Allowed cross-world glitches include: + - E.1.6.a) Slime spectating (#entangledRule("D.1.2.h")) + - E.1.6.b) Credits warp (#entangledRule("D.1.2.ah")) +- Banned cross world glitches include: + - E.1.6.c) World merge (#formatLink("https://youtu.be/a-YhOtj6HmE")[Example]) + - E.1.6.d) Joining a server and a singleplayer world at the same time (#formatLink("https://youtu.be/b9JscBrY8VA")[Example]) == E.2: Timing Glitched Runs #entangled[Entangled Rule(s):]\ @@ -726,6 +736,7 @@ E.2.2) Glitched runs follow the same hierarchy of timers as is outlined == E.3: Internal Runs E.3.1) Internal runs must not leave the world (Save and Quit or crash the game) in accordance with glitchless rules #entangledRule("D.1.3")-#entangledRule("D.1.4"). +E.3.2) Internal runs may not use cross-world glitches. == E.4: External Runs E.4.1) External runs must leave the world (Save and Quit or crash the game). From 9a39eeda9140f69f1e0ef8e5cb783f27e225ac7d Mon Sep 17 00:00:00 2001 From: tildejustin Date: Fri, 13 Feb 2026 20:29:12 -0500 Subject: [PATCH 20/26] ban chunkmap freezing in 1.15 rsg (further restriction tbd) --- rules.typ | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/rules.typ b/rules.typ index 73c0862..c69a8d0 100644 --- a/rules.typ +++ b/rules.typ @@ -843,7 +843,8 @@ H.1.2) In set seed runs, intentional prerotation (spawning into the world rotate == 1.3: Random Seed, 1.13-1.15 1.3.1) Runs under 20 minutes must submit world files.\ 1.3.2) Runs under 17 minutes must submit world files, logs, and gameplay audio.\ -1.3.3) Runs under 17 minutes will be retimed as per top-level retiming rules. +1.3.3) Runs under 17 minutes will be retimed as per top-level retiming rules.\ +1.3.4) Chunkmap freezing is not allowed. Chunkmap freezing consists of using OBS Freeze Filter or another technique to capture an early state of the chunkmap and extend how long it is displayed in that state. == 1.4: Random Seed, 1.9-1.12 1.4.1) Runs under 25 minutes must submit world files, logs, and gameplay audio.\ From 1633a19a9ba274292f85af5a08233bba06404230 Mon Sep 17 00:00:00 2001 From: tildejustin Date: Fri, 13 Feb 2026 20:30:36 -0500 Subject: [PATCH 21/26] fix incongruous headers and sections in catext after glitched merge and category rename, #176 --- rules.typ | 34 +++++++--------------------------- 1 file changed, 7 insertions(+), 27 deletions(-) diff --git a/rules.typ b/rules.typ index c69a8d0..b88baae 100644 --- a/rules.typ +++ b/rules.typ @@ -1207,14 +1207,10 @@ CE9.8.1) The run is considered complete once an oak log, a spruce log, birch log = CE10: All Wool == CE10.1: All Wool Objective and Clarifications -CE10.1.1) The run is considered complete once all colours of wool have been simultaneously obtained. +CE10.1.1) The run is considered complete once all colours of wool have been simultaneously obtained. - CE10.1.1.a) Timing ends once the last colour of wool is obtained. (see #entangledRule("A.5.18")) -#entangled[Entangled Rule(s):]\ -#entangled[CE10.1.1 is referenced by: ] #entangledRule("CE21.1.1")\ -CE10.1.2) The list of all wool colours are: white wool (called wool in Minecraft versions before 1.11), orange wool, magenta wool, light blue wool, yellow wool, lime wool, pink wool, grey wool, light grey wool, cyan wool, purple wool, blue wool, brown wool, green wool, red wool, and black wool.\ -#entangled[Entangled Rule(s):]\ -#entangled[CE10.1.2 is referenced by: ] #entangledRule("CE21.1.1")\ -CE10.1.3) Clarification: There are no specific subcategory rules; thus, runs should only follow their respective rulesets (universal, set seed/random seed, glitchless).\ +CE10.1.2) The list of all wool colours are: white wool (called wool in Minecraft versions before 1.11), orange wool, magenta wool, light blue wool, yellow wool, lime wool, pink wool, grey wool, light grey wool, cyan wool, purple wool, blue wool, brown wool, green wool, red wool, and black wool.\ +CE10.1.3) Clarification: There are no specific subcategory rules; thus, runs should only follow their respective rulesets (universal, set seed/random seed, glitchless/glitched).\ CE10.1.4) All random seed categories begin upon world load, whereas all set seed categories begin upon first input. = CE11: All Minerals @@ -1236,11 +1232,9 @@ CE11.4.1) The run is considered complete once a piece of coal, an iron ingot, a = CE12: Full Iron Armor and 15 Levels == CE12.1: Full Iron Armor and 15 Levels Objective and Clarifications -CE12.1.1) The run is considered complete once an iron helmet, iron chestplate, iron leggings, and iron boots have been simultaneously equipped, and the player has 15 levels of experience. +CE12.1.1) The run is considered complete once an iron helmet, iron chestplate, iron leggings, and iron boots have been simultaneously equipped, and the player has 15 levels of experience. - CE12.1.1.a) Timing ends once the last piece of armour is equipped or once the experience bar turns to 15 levels (whichever comes last). -#entangled[Entangled Rule(s):]\ -#entangled[CE12.1.1 is referenced by: ] #entangledRule("CE22.1.1")\ -CE12.1.2) Clarification: There are no specific subcategory rules; thus, runs should only follow their respective rulesets (universal, set seed/random seed, glitchless, structures/no structures).\ +CE12.1.2) Clarification: There are no specific subcategory rules; thus, runs should only follow their respective rulesets (universal, set seed/random seed, glitchless/glitched, structures/no structures).\ CE12.1.3) All runs begin upon first input. = CE13: All Workstations @@ -1252,9 +1246,9 @@ CE13.1.2) The list of all workstations are: blast furnace, smoker, cartography t CE13.1.3) Clarification: There are no specific subcategory rules; thus, runs should only follow their respective rulesets (universal, set seed/random seed, glitchless).\ CE13.1.4) All runs begin upon first input. -= CE14: Full Inventory += CE14: Full Inventy! -== CE14.1: Full Inventory Objective and Clarifications +== CE14.1: Full Inventy! Objective and Clarifications CE14.1.1) The run is considered complete once all inventory slots are full. - CE14.1.1.a) Timing ends once the last inventory slot is filled. - CE14.1.1.b) Clarification: All 36 main inventory slots must be filled, but the offhand and armour slots do not have to be filled. @@ -1377,20 +1371,6 @@ CE20.3.3) During scouting time only, any external programs may be use - CE20.3.3.a) Clarification: Mods and clients not outlined in section #entangledRule("A.8") are not allowed. CE20.3.4) During scouting time only, any of the game's files may be read, nullifying #entangledRule("A.3.10"). -= CE21: All Wool (Glitched) - -== CE21.1: All Wool (Glitched) Objective and Clarifications -CE21.1.1) All Wool (Glitched) follows the same pretences for completion as All Wool (see #entangledRule("CE10.1.1")-#entangledRule("CE10.1.2")).\ -CE21.1.2) Clarification: There are no specific subcategory rules; thus, runs should only follow their respective rulesets (universal, set seed/random seed, glitched).\ -CE21.1.3) All random seed categories begin upon world load, whereas all set seed categories begin upon first input. - -= CE22: Full Iron Armor and 15 Levels (Glitched) - -== CE22.1: Full Iron Armor and 15 Levels (Glitched) Objective and Clarifications -CE22.1.1) Full Iron Armor and 15 Levels (Glitched) follows the same pretences for completion as Full Iron Armor and 15 Levels (see #entangledRule("CE12.1.1")).\ -CE22.1.2) Clarification: There are no specific subcategory rules; thus, runs should only follow their respective rulesets (universal, set seed/random seed, glitched).\ -CE22.1.3) All runs begin upon first input. - = CE23: Sonic, Tails, and Knuckles == CE23.1: Sonic, Tails, and Knuckles Objective and Clarifications From 0edba5a9b3c1a6766f56227341179a55bc5f8c31 Mon Sep 17 00:00:00 2001 From: tildejustin Date: Fri, 13 Feb 2026 20:31:12 -0500 Subject: [PATCH 22/26] allow crayonallportals tool for all portals, #217 --- rules.typ | 1 + 1 file changed, 1 insertion(+) diff --git a/rules.typ b/rules.typ index b88baae..b60689a 100644 --- a/rules.typ +++ b/rules.typ @@ -1335,6 +1335,7 @@ CE19.3.3) In addition to the external tools allowed by #entangledRule("A.11"), t - CE19.3.3.a) #formatLink("https://github.com/TheTalkingMime/AllPortals")[All Portals [TheTalkingMime]] - CE19.3.3.b) #formatLink("https://github.com/shnenanigans/APgui")[APgui [shnenanigans]] - CE19.3.3.c) #formatLink("https://www.desmos.com/calculator/la7ezpyutu")[Desmos Stronghold Rings] +- CE19.3.3.d) #formatLink("https://github.com/CommonCrayon/CrayonAllPortals")[CrayonAllPortals] (up to v1.0) CE19.3.4) A runner may segment their run if and only if they follow the rules regarding segmentation as outlined by #entangledRule("A.5.19") and its corresponding sub-rules. == CE19.4: All Portals Purist From 55677aed145dd80c0c63bd5972a81c51c74f5272 Mon Sep 17 00:00:00 2001 From: tildejustin Date: Fri, 13 Feb 2026 20:33:27 -0500 Subject: [PATCH 23/26] sonya's terminology clarifications, #99 --- rules.typ | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/rules.typ b/rules.typ index b60689a..3ef6cda 100644 --- a/rules.typ +++ b/rules.typ @@ -99,8 +99,8 @@ Some categories may not have a subcategory ruleset (e.g. External Set Seed Glitc Please refer to #formatLink("https://datatracker.ietf.org/doc/html/rfc2119")[RFC-2119 Requirement Levels] for the explicit definitions of the commands *must, must not, can/may, should/recommended, and should not/not recommended.* === Commands: -- *(at the discretion of verifiers): * An outcome is subjective: it is therefore at the discretion of the mods and verifiers. This outcome is either brought about collectively or is a judgement that the majority of the mods/verifiers would agree upon. -- *Open a thread: * Create a thread in the official Discord server by joining #formatLink("https://discord.gg/jmdFn3C")[the official Minecraft: Java speedrunning Discord], clicking the \#help channel, clicking the Create Thread button, then clicking create. This message will then be sent to all moderators and verifiers; in the message, detail the situation which has caused you to open a thread. +- *(at the discretion of verifiers): * An outcome is subjective: it is therefore at the discretion of the speedrun.com moderators and verifiers as shown in the Moderators section on speedrun.com/mc. This outcome is either brought about collectively or is a judgement that the majority of the mods/verifiers would agree upon. +- *Open a thread: * Create a thread in the official Discord server by joining #formatLink("https://discord.gg/jmdFn3C")[the official Minecraft Java Speedrunning Discord], clicking the \#help channel, and following the instructions in the message from the Iron Golem bot. This message will then be sent to all moderators and verifiers; in the message, detail the situation which has caused you to open a thread. - *[rule] is nullified: * A rule does not apply for a specific category or subset of a category === Sub-Rules: From 8b3e24a02ff7a55d968c4547a108216763d7b377 Mon Sep 17 00:00:00 2001 From: tildejustin Date: Fri, 13 Feb 2026 20:34:52 -0500 Subject: [PATCH 24/26] allow abuse of the unintentional dragon behavior changes introduced in 19w08b, #213 --- rules.typ | 1 + 1 file changed, 1 insertion(+) diff --git a/rules.typ b/rules.typ index 3ef6cda..1b4ce02 100644 --- a/rules.typ +++ b/rules.typ @@ -653,6 +653,7 @@ D.1.1) Only these glitches may be used during glitchless runs. - D.1.1.bb) Trapping wither (#formatLink("https://youtu.be/PCkzhtBl_xY&t=91")[Example], #formatLink("https://youtu.be/O-QgTljCgZw&t=153")[Example \#2]) - D.1.1.bc) Compass glitch (#formatLink("https://youtu.be/fQi1dOHEYLg")[Example]) - D.1.1.bd) Unbreakable Fishing Line / Lead with Dimension Change (#formatLink("https://youtu.be/uxLNbGshih0")[Example], #formatLink("https://youtu.be/wh_tW3lVbuY")[Example \#2]) +- D.1.1.be) Abusing the dragon's reduced max vertical acceleration (#formatLink("https://bugs.mojang.com/browse/MC/issues/MC-272431")[MC-272431]) D.1.2) Any other glitches not included in D.1.1 must not be used during glitchless runs. - Examples of glitches that are not allowed include but are not limited to: - D.1.2.a) Duplication and zero-stack glitches (#formatLink("https://youtu.be/PYFMGuicVWA&t=102")[Example]) From 78e5f0e826e6d5e1bbe20f6305b6864dd44cb533 Mon Sep 17 00:00:00 2001 From: tildejustin Date: Fri, 13 Feb 2026 20:55:00 -0500 Subject: [PATCH 25/26] ban optifine for shield and stealth cycle, tailor ban to ssg only, thread --- rules.typ | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/rules.typ b/rules.typ index 1b4ce02..55c43d1 100644 --- a/rules.typ +++ b/rules.typ @@ -453,7 +453,7 @@ A.8.1) OptiFine is allowed in Minecraft versions 1.0-1.14.4 if and only if the f - A.8.1.v) Fast debug info must be kept off. - A.8.1.w) Debug profiler must be kept off. \ -- A.8.1.x) Exception: Using OptiFine in external glitched categories or in runs that use Oneshot pre 1.13 is not allowed. +- A.8.1.x) Exception: Using OptiFine in external glitched categories or in runs that use Oneshot, Shield Cycle, or Stealth Cycle in pre 1.13 on set seeds is not allowed. - A.8.1.y) Light, Standard, and Ultra are the only versions of OptiFine that may be used. This excludes Multi-Core, Smooth, and AA releases for Minecraft Pre 1.3. #entangled[Entangled Rule(s):]\ #entangled[A.8.1 is referenced by: ] #entangledRule("A.6.4.b.i")\ From e700176e5b389f0a06cb62491fbd09661c9a05fa Mon Sep 17 00:00:00 2001 From: tildejustin Date: Fri, 13 Feb 2026 20:55:20 -0500 Subject: [PATCH 26/26] fix formatting mistakes --- rules.typ | 34 +++++++++++++++++----------------- 1 file changed, 17 insertions(+), 17 deletions(-) diff --git a/rules.typ b/rules.typ index 55c43d1..c1feb55 100644 --- a/rules.typ +++ b/rules.typ @@ -358,7 +358,7 @@ A.5.19) Segmenting, pausing the speedrun for a time by quitting the wor - A.5.19.e) Clarification: For glitchless runs, the segmentation must not provide any additional benefit to the run. - A.5.19.f) Time spent between the segments of the run will not contribute to in-game time or the real time of the run. #entangled[Entangled Rule(s):]\ -#entangled[A.5.19 is referenced by: ] #entangledRules("4.1.2", "CE19.3.4")\ +#entangled[A.5.19 is referenced by: ] #entangledRules(("4.1.2", "CE19.3.4"))\ == A.6: General Submission Rules A.6.1) The run's speedrun.com submission description must include the seed of the world. @@ -718,13 +718,13 @@ E.1.3) If you use Task Manager or another program which forcefully closes the ga E.1.4) External Arbitrary Code Execution (ACE) must not be used. - E.1.4.a) Example: Log4j exploit E.1.5) Glitched runs must be played entirely within one version.\ -E.1.6) Cross-world glitches, or glitches that require setup in another world, are legalized on a case-by-case basis. -- Allowed cross-world glitches include: - - E.1.6.a) Slime spectating (#entangledRule("D.1.2.h")) - - E.1.6.b) Credits warp (#entangledRule("D.1.2.ah")) -- Banned cross world glitches include: - - E.1.6.c) World merge (#formatLink("https://youtu.be/a-YhOtj6HmE")[Example]) - - E.1.6.d) Joining a server and a singleplayer world at the same time (#formatLink("https://youtu.be/b9JscBrY8VA")[Example]) +E.1.6) Cross-world glitches, or glitches that require setup in another world, are legalized on a case-by-case basis.\ +Allowed cross-world glitches include: +- E.1.6.a) Slime spectating (#entangledRule("D.1.2.h")) +- E.1.6.b) Credits warp (#entangledRule("D.1.2.ah")) +Banned cross world glitches include: +- E.1.6.c) World merge (#formatLink("https://youtu.be/a-YhOtj6HmE")[Example]) +- E.1.6.d) Joining a server and a singleplayer world at the same time (#formatLink("https://youtu.be/b9JscBrY8VA")[Example]) == E.2: Timing Glitched Runs #entangled[Entangled Rule(s):]\ @@ -736,7 +736,7 @@ E.2.2) Glitched runs follow the same hierarchy of timers as is outlined - E.2.2.b) Times may be adjusted from other timers to follow E.2.1. == E.3: Internal Runs -E.3.1) Internal runs must not leave the world (Save and Quit or crash the game) in accordance with glitchless rules #entangledRule("D.1.3")-#entangledRule("D.1.4"). +E.3.1) Internal runs must not leave the world (Save and Quit or crash the game) in accordance with glitchless rules #entangledRule("D.1.3")-#entangledRule("D.1.4").\ E.3.2) Internal runs may not use cross-world glitches. == E.4: External Runs @@ -752,8 +752,8 @@ F.1.2) In addition to the world generation settings allowed in #entangle F.1.3) No cheats or actions which could not be accomplished without cheats must be used during the run. - F.1.3.a) Exception: /difficulty may be used, nullifying #entangledRule("A.3.5") (note that in accordance with #entangledRule("A.3.11"), the difficulty must not be set to peaceful, even if toggling between difficulties) - F.1.3.b) Exception: /time set 0 may be used as described in #entangledRule("F.2.2"), nullifying #entangledRule("A.3.5"). -F.1.4) Players with cheats enabled must not use F3+I.\ - F.1.3.c) Exception: /publish may be used, nullifying #entangledRule("A.3.5"). +F.1.4) Players with cheats enabled must not use F3+I.\ F.1.5) The entirety of a co-op run must occur on either an dedicated server or with Open to LAN. - F.1.5.a) Exception: The very start (at the discretion of verifiers) of a run may be played on singleplayer. F.1.6) If more than 16 players are running, choose 16 players while submitting, input the names of 15 of the players, and then list “+others” for the 16th slot. Include the name of all other players not listed in the description of the speedrun.com submission.\ @@ -777,7 +777,7 @@ F.2.2) Runs done on external servers, or runs on LAN which choose to do #entangled[Entangled Rule(s):]\ #entangled[F.2.2 is referenced by: ] #entangledRule("F.1.3.b")\ F.2.3) On external servers, if /time set 0 is not done, then time starts when the server loads the world and server logs must be submitted. -F.2.4) The category is timed by RTA, nullifying #entangledRule("A.5"). +F.2.4) The category is timed by RTA, nullifying #entangledRule("A.5"). == F.3: Video Rules F.3.1) Every player should record their perspective, and all of these perspectives should be submitted with the run. @@ -917,13 +917,13 @@ H.1.2) In set seed runs, intentional prerotation (spawning into the world rotate #entangled[4.1 is referenced by: ] #entangledRules(("3.1.1", "6.1.1"))\ 4.1.1) The run is considered complete once every advancement has been achieved. - 4.1.1.a) Timing ends once the chat notification for the last advancement is shown. -4.1.2) <4.1.2> A runner may segment their run if and only if they follow the rules regarding segmentation as outlined by #entangledRule("A.5.19") and its corresponding sub-rules. +4.1.2) <4.1.2> A runner may segment their run if and only if they follow the rules regarding segmentation as outlined by #entangledRule("A.5.19") and its corresponding sub-rules.\ 4.1.3) <4.1.3> Runs must demonstrate all advancements have been obtained. - This constitutes at least one of the following: -- 4.1.2.a) The advancement file from the world is submitted. -- 4.1.2.b) World files are submitted. -- 4.1.2.c) An advancement tracker is displayed the count of advancements have been completed. -- 4.1.2.d) SpeedRunIGT is set to the right category and autostops. +- 4.1.3.a) The advancement file from the world is submitted. +- 4.1.3.b) World files are submitted. +- 4.1.3.c) An advancement tracker is displayed the count of advancements have been completed. +- 4.1.3.d) SpeedRunIGT is set to the right category and autostops. #entangled[Entangled Rule(s):]\ #entangled[4.1.3 is referenced by: ] #entangledRule("CE24.1.2")\ 4.1.4) All runs begin on world load. @@ -944,7 +944,7 @@ H.1.2) In set seed runs, intentional prerotation (spawning into the world rotate 4.6.1) <4.6.1> The list of all advancements necessary to obtain are: Minecraft, Stone Age, Getting an Upgrade, Acquire Hardware, Suit Up, Hot Stuff, Isn't It Iron Pick, Not Today, Thank You, Ice Bucket Challenge, Diamonds!, We Need to Go Deeper, Cover Me With Diamonds, Enchanter, Zombie Doctor, Eye Spy, The End?, Husbandry, The Parrots and the Bats, Best Friends Forever, A Seedy Place, Two by Two, A Balanced Diet, Serious Dedication, Adventure, Monster Hunter, What a Deal!, Sweet Dreams, Take Aim, Monsters Hunted, Postmortal, Hired Help, Adventuring Time, Sniper Duel, Nether, Return to Sender, Subspace Bubble, A Terrible Fortress, Uneasy Alliance, Spooky Scary Skeleton, Into Fire, Withering Heights, Local Brewery, Bring Home the Beacon, A Furious Cocktail, Beaconator, How Did We Get Here?, The End, Free the End, The Next Generation, Remote Getaway, The End... Again..., You Need a Mint, The City at the End of the Game, Sky's the Limit, Great View From Up Here, Fishy Business, Tactical Fishing, A Throwaway Joke, Very Very Frightening, Ol' Betsy, Who's the Pillager Now?, Two Birds One Arrow, Arbalistic, A Complete Catalogue, Voluntary Exile, Hero of the Village, Sticky Situation, Bee Our Guest, Total Beelocation, Those Were the Days, Hidden in the Depths, Who Is Cutting Onions?, Oh Shiny, This Boat Has Legs, War Pigs, Country Lode Take Me Home, Cover Me in Debris, Not Quite “Nine” Lives, Hot Tourist Destinations, and Bullseye. #entangled[Entangled Rule(s):]\ #entangled[4.6.1 is referenced by: ] #entangledRule("CE24.1.1")\ -4.6.2: RSG runs under 3:00:00 must submit world files and logs. +4.6.2) RSG runs under 3:00:00 must submit world files and logs. == 4.7: SS/SSG/RS/RSG, 1.17 4.7.1) The list of all advancements necessary to obtain are: Minecraft, Stone Age, Getting an Upgrade, Acquire Hardware, Suit Up, Hot Stuff, Isn't It Iron Pick, Not Today, Thank You, Ice Bucket Challenge, Diamonds!, We Need to Go Deeper, Cover Me With Diamonds, Enchanter, Zombie Doctor, Eye Spy, The End?, Husbandry, The Parrots and the Bats, Best Friends Forever, A Seedy Place, Two by Two, A Balanced Diet, Serious Dedication, Adventure, Monster Hunter, What a Deal!, Sweet Dreams, Take Aim, Monsters Hunted, Postmortal, Hired Help, Adventuring Time, Sniper Duel, Nether, Return to Sender, Subspace Bubble, A Terrible Fortress, Uneasy Alliance, Spooky Scary Skeleton, Into Fire, Withering Heights, Local Brewery, Bring Home the Beacon, A Furious Cocktail, Beaconator, How Did We Get Here?, The End, Free the End, The Next Generation, Remote Getaway, The End... Again..., You Need a Mint, The City at the End of the Game, Sky's the Limit, Great View From Up Here, Fishy Business, Tactical Fishing, A Throwaway Joke, Very Very Frightening, Ol' Betsy, Who's the Pillager Now?, Two Birds One Arrow, Arbalistic, A Complete Catalogue, Voluntary Exile, Hero of the Village, Sticky Situation, Bee Our Guest, Total Beelocation, Those Were the Days, Hidden in the Depths, Who Is Cutting Onions?, Oh Shiny, This Boat Has Legs, War Pigs, Country Lode Take Me Home, Cover Me in Debris, Not Quite “Nine” Lives, Hot Tourist Destinations, Bullseye, Whatever Floats Your Goat, Wax On, Wax Off, The Cutest Predator, The Healing Power of Friendship, Glow and Behold!, Light as a Rabbit, Surge Protector, Is It a Bird?, Is It a Balloon?, and Is It a Plane?\