From f873819494138186c5729a1f5a11e3cd34229a94 Mon Sep 17 00:00:00 2001 From: tildejustin Date: Wed, 16 Jul 2025 00:08:45 -0400 Subject: [PATCH 01/23] add rule against automatically changing mappings --- rules.typ | 1 + 1 file changed, 1 insertion(+) diff --git a/rules.typ b/rules.typ index 830baa9..5897f7d 100644 --- a/rules.typ +++ b/rules.typ @@ -478,6 +478,7 @@ A.9.4) If SeedQueue is used, only one instance of Minecraft running SeedQueue ma == A.10: Macro and Rebind Rules A.10.1) You may remap keys using external programs, but each game input may have only one key, and each key may cause only one game input. - A.10.1.a) Example: Shift+F3 cannot be rebound to a singular key. +- A.10.1.b) Key mappings may not be changed during the run, except by other hotkeys defined in the same software (AHK, QMK, etc). Importantly, this excludes using wpstateout.txt state or other file or screen reading to conditionally change mappings. A.10.2) If keys are rebound, they must be to buttons. - This excludes but is not limited to: - A.10.2.a) Remapping to a scroll-wheel From 724cfe43b4147ef129ed56c22f18b85ba65e1f25 Mon Sep 17 00:00:00 2001 From: tildejustin Date: Wed, 16 Jul 2025 17:24:26 -0400 Subject: [PATCH 02/23] remove key mapping changing rule --- rules.typ | 1 - 1 file changed, 1 deletion(-) diff --git a/rules.typ b/rules.typ index 5897f7d..830baa9 100644 --- a/rules.typ +++ b/rules.typ @@ -478,7 +478,6 @@ A.9.4) If SeedQueue is used, only one instance of Minecraft running SeedQueue ma == A.10: Macro and Rebind Rules A.10.1) You may remap keys using external programs, but each game input may have only one key, and each key may cause only one game input. - A.10.1.a) Example: Shift+F3 cannot be rebound to a singular key. -- A.10.1.b) Key mappings may not be changed during the run, except by other hotkeys defined in the same software (AHK, QMK, etc). Importantly, this excludes using wpstateout.txt state or other file or screen reading to conditionally change mappings. A.10.2) If keys are rebound, they must be to buttons. - This excludes but is not limited to: - A.10.2.a) Remapping to a scroll-wheel From 31a6464b5e548f03431c602cc63c9d213fb65fb3 Mon Sep 17 00:00:00 2001 From: tildejustin Date: Wed, 16 Jul 2025 18:21:11 -0400 Subject: [PATCH 03/23] fix? screen reading rules --- rules.typ | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/rules.typ b/rules.typ index 830baa9..6bf0b0d 100644 --- a/rules.typ +++ b/rules.typ @@ -489,11 +489,14 @@ A.10.4) Macros are not allowed to be triggered during a run. - A.10.4.d) Exception: Toggle sprint macros are allowed in all versions. #entangled[Entangled Rule(s):]\ #entangled[A.10.4 is nullified by: ] #entangledRules(("CE20.2.3", "CE20.3.2"))\ -A.10.5) Macros may only be used to reset worlds if resets are triggered by player input. Multiple simultaneous resets may be triggered by a single player input. -- A.10.5.a) Clarification: Any program or macro that reads the screen (directly or indirectly), listens to game audio, or reads the vanilla game files directly must not be used. +A.10.5) Macros may only be used to reset worlds if resets are triggered by player input. Multiple simultaneous resets may be triggered by a single player input. +- A.10.5.a) Clarification: Reading game files or screen reading for determining whether to reset or aiding the player in resetting is not allowed. - A.10.5.b) Clarification: Automatic resetting, or resetting based on anything other than player input is not allowed. #entangled[Entangled Rule(s):]\ #entangled[A.10.5 is subject to an exception by: ] #entangledRule("C.2.1")\ +A.10.6) Any program or macro that does screen reading or listens to game audio for an advantage (at the discretion of verifiers) must not be used. Screen reading is using the data of the pixels of the game window to programmatically capture information from the game (e.g. color for biomes, text recognition for f3, enchantment cracking, inventory contents, etc). +- A.10.6.a) Clarification: Any attempt to get around this rule will not be tolerated (i.e. taking a screenshot and a program reading from that, etc. would not be allowed). +- A.10.6.b) Clarification: This does not include recording software. == A.11: External Resource Rules #entangled[Entangled Rule(s):]\ From e1fffdbdf38f0d2875ce994631502792f2add097 Mon Sep 17 00:00:00 2001 From: tildejustin Date: Wed, 16 Jul 2025 18:23:26 -0400 Subject: [PATCH 04/23] this is not an exception to the *vanilla* file reading ban --- rules.typ | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/rules.typ b/rules.typ index 6bf0b0d..46c062a 100644 --- a/rules.typ +++ b/rules.typ @@ -226,7 +226,7 @@ A.3.8) The chat text must be visible and legible in the video recording and the A.3.9) Runs must not intend to be as slow as possible. At a minimum, an attempt must be made to finish the run quickly.\ A.3.10) You must not read from any files produced by the vanilla game before or during the run. - A.3.10.a) Exception: Players and programs may read from the advancement or statistics files. -- A.3.10.b) Exception: Players and programs may read from the wpstateout.txt file created by WorldPreview or the State Output mod. +- A.3.10.b) Clarification: Players and programs may read from the wpstateout.txt file created by WorldPreview or the State Output mod. - A.3.10.c) Exception: Historically, macros have had limited allowances to read the logs in order to determine game state. While State Output now exists for this, these old macros are still allowed. #entangled[Entangled Rule(s):]\ #entangled[A.3.10 is referenced by: ] #entangledRule("CE20.3.4")\ From d6258e25022522a2abc1dc9cfdbd5a564f9f00bd Mon Sep 17 00:00:00 2001 From: tildejustin Date: Wed, 16 Jul 2025 18:26:38 -0400 Subject: [PATCH 05/23] ban macros reading wpstateout.txt --- rules.typ | 1 + 1 file changed, 1 insertion(+) diff --git a/rules.typ b/rules.typ index 46c062a..7ba47df 100644 --- a/rules.typ +++ b/rules.typ @@ -497,6 +497,7 @@ A.10.5) Macros may only be used to reset worlds if resets are triggered A.10.6) Any program or macro that does screen reading or listens to game audio for an advantage (at the discretion of verifiers) must not be used. Screen reading is using the data of the pixels of the game window to programmatically capture information from the game (e.g. color for biomes, text recognition for f3, enchantment cracking, inventory contents, etc). - A.10.6.a) Clarification: Any attempt to get around this rule will not be tolerated (i.e. taking a screenshot and a program reading from that, etc. would not be allowed). - A.10.6.b) Clarification: This does not include recording software. +A.10.7) Macros may not change key mappings depending on the state of wpstateout.txt == A.11: External Resource Rules #entangled[Entangled Rule(s):]\ From b1a031f75d26666c9c906751b42ce244c984c5cc Mon Sep 17 00:00:00 2001 From: tildejustin Date: Wed, 16 Jul 2025 20:32:42 -0400 Subject: [PATCH 06/23] a.10.7 to be added later (soon, hopefully) --- rules.typ | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/rules.typ b/rules.typ index 7ba47df..465770e 100644 --- a/rules.typ +++ b/rules.typ @@ -494,10 +494,9 @@ A.10.5) Macros may only be used to reset worlds if resets are triggered - A.10.5.b) Clarification: Automatic resetting, or resetting based on anything other than player input is not allowed. #entangled[Entangled Rule(s):]\ #entangled[A.10.5 is subject to an exception by: ] #entangledRule("C.2.1")\ -A.10.6) Any program or macro that does screen reading or listens to game audio for an advantage (at the discretion of verifiers) must not be used. Screen reading is using the data of the pixels of the game window to programmatically capture information from the game (e.g. color for biomes, text recognition for f3, enchantment cracking, inventory contents, etc). +A.10.6) Any program or macro that does screen reading or listens to game audio for an advantage (at the discretion of verifiers) must not be used. Screen reading is using the data of the pixels of the game window to programmatically capture information from the game (e.g. color for biomes, text recognition for F3, enchantment cracking, inventory contents, etc). - A.10.6.a) Clarification: Any attempt to get around this rule will not be tolerated (i.e. taking a screenshot and a program reading from that, etc. would not be allowed). - A.10.6.b) Clarification: This does not include recording software. -A.10.7) Macros may not change key mappings depending on the state of wpstateout.txt == A.11: External Resource Rules #entangled[Entangled Rule(s):]\ From 4e27813c338b0d1996f73a22488c82e763310462 Mon Sep 17 00:00:00 2001 From: tildejustin Date: Thu, 17 Jul 2025 18:19:44 -0400 Subject: [PATCH 07/23] rewrite vanilla & mod file reading rule --- rules.typ | 18 ++++++++++++++---- 1 file changed, 14 insertions(+), 4 deletions(-) diff --git a/rules.typ b/rules.typ index 465770e..7d5842c 100644 --- a/rules.typ +++ b/rules.typ @@ -224,10 +224,20 @@ A.3.6) If you play one instance of Minecraft and then switch to playing another, A.3.7) Non-default shaders, including Super Secret Settings, must not be used.\ A.3.8) The chat text must be visible and legible in the video recording and the Chat setting must be either Shown or Commands Only.\ A.3.9) Runs must not intend to be as slow as possible. At a minimum, an attempt must be made to finish the run quickly.\ -A.3.10) You must not read from any files produced by the vanilla game before or during the run. -- A.3.10.a) Exception: Players and programs may read from the advancement or statistics files. -- A.3.10.b) Clarification: Players and programs may read from the wpstateout.txt file created by WorldPreview or the State Output mod. -- A.3.10.c) Exception: Historically, macros have had limited allowances to read the logs in order to determine game state. While State Output now exists for this, these old macros are still allowed. +A.3.10) World and log files produced by the vanilla game must not be to be read before or during the run.\ +Exception: Advancement or statistics files may be read by people and programs.\ +\ +Historically, macros have had limited allowances to read the logs in order to determine game state. +While State Output now exists for this, these old macros are still allowed.\ +\ +Files created by mods are generally allowed to be read, however there are some restrictions to avoid giving an undue advantage to players using mods.\ +\ +wpstateout.txt state must not be used during a run, as it was designed and allowed for reset macros, which means it was not intended to be allowed for use during a run and provides more information than is necessarily appropriate. +Specifically, use of wpstateout.txt in macro logic during a run and to change rebinds is considered abuse of a resetting mod and of mod-only behavior for an advantage and is banned. +Use of wpstateout.txt state in scripts for aesthetic or continuous (with no regard to whether a run is happening or not) reasons, such as for changing obs properties or time tracking, is generally allowed if it is not for an advantage in the run (at the discretion of verifiers). +Use of just the inworld state with no regard to the substate after the comma as a more performant substitute for window title checking is allowed. +Using the gamescreenopen inworld substate for a "safe reset," i.e. wrapping the reset key and not letting it go through based on that state, is allowed as it is considered a net positive to the leaderboards. This has/will been integrated into Atum in later versions to mitigate the fact that it goes outside the scope of what wpstateout.txt was intended to be allowed for. + #entangled[Entangled Rule(s):]\ #entangled[A.3.10 is referenced by: ] #entangledRule("CE20.3.4")\ #entangled[A.3.10 is subject to an exception by: ] #entangledRule("C.2.1")\ From f42d2141002adb23e42d96361ba9c9160c4cec50 Mon Sep 17 00:00:00 2001 From: tildejustin Date: Fri, 18 Jul 2025 10:09:13 -0400 Subject: [PATCH 08/23] should not (b/c allowed in some circumstances, unfortunately) --- rules.typ | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/rules.typ b/rules.typ index 7d5842c..d02398b 100644 --- a/rules.typ +++ b/rules.typ @@ -232,8 +232,8 @@ While State Output now exists for this, these old macros are still allowed.\ \ Files created by mods are generally allowed to be read, however there are some restrictions to avoid giving an undue advantage to players using mods.\ \ -wpstateout.txt state must not be used during a run, as it was designed and allowed for reset macros, which means it was not intended to be allowed for use during a run and provides more information than is necessarily appropriate. -Specifically, use of wpstateout.txt in macro logic during a run and to change rebinds is considered abuse of a resetting mod and of mod-only behavior for an advantage and is banned. +wpstateout.txt state should not be used during a run, as it was designed and allowed for reset macros, which means it was not intended to be allowed for use during a run and provides more information than is necessarily appropriate. +Specifically, use of wpstateout.txt in macro logic during a run and to change rebinds is considered abuse of a resetting mod and of mod-only behavior for an advantage and is not allowed. Use of wpstateout.txt state in scripts for aesthetic or continuous (with no regard to whether a run is happening or not) reasons, such as for changing obs properties or time tracking, is generally allowed if it is not for an advantage in the run (at the discretion of verifiers). Use of just the inworld state with no regard to the substate after the comma as a more performant substitute for window title checking is allowed. Using the gamescreenopen inworld substate for a "safe reset," i.e. wrapping the reset key and not letting it go through based on that state, is allowed as it is considered a net positive to the leaderboards. This has/will been integrated into Atum in later versions to mitigate the fact that it goes outside the scope of what wpstateout.txt was intended to be allowed for. From 7dadec88eeaab86582a7534f3d29d45a57b77b11 Mon Sep 17 00:00:00 2001 From: tildejustin Date: Fri, 18 Jul 2025 12:35:30 -0400 Subject: [PATCH 09/23] cursor grabbed equivalency --- rules.typ | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git a/rules.typ b/rules.typ index d02398b..9a4e650 100644 --- a/rules.typ +++ b/rules.typ @@ -232,11 +232,9 @@ While State Output now exists for this, these old macros are still allowed.\ \ Files created by mods are generally allowed to be read, however there are some restrictions to avoid giving an undue advantage to players using mods.\ \ -wpstateout.txt state should not be used during a run, as it was designed and allowed for reset macros, which means it was not intended to be allowed for use during a run and provides more information than is necessarily appropriate. -Specifically, use of wpstateout.txt in macro logic during a run and to change rebinds is considered abuse of a resetting mod and of mod-only behavior for an advantage and is not allowed. -Use of wpstateout.txt state in scripts for aesthetic or continuous (with no regard to whether a run is happening or not) reasons, such as for changing obs properties or time tracking, is generally allowed if it is not for an advantage in the run (at the discretion of verifiers). -Use of just the inworld state with no regard to the substate after the comma as a more performant substitute for window title checking is allowed. -Using the gamescreenopen inworld substate for a "safe reset," i.e. wrapping the reset key and not letting it go through based on that state, is allowed as it is considered a net positive to the leaderboards. This has/will been integrated into Atum in later versions to mitigate the fact that it goes outside the scope of what wpstateout.txt was intended to be allowed for. +wpstateout.txt state should not be used during a run, as it was designed and allowed for reset macros, which means it was not intended to be allowed for use during a run and provides more information than is necessarily appropriate or justified. +Specifically, the paused and gamescreenopen states must be treated as the same for any scripts or macros that run after the timer starts. +Use of wpstateout.txt state in scripts for aesthetic or continuous (with no regard to whether a run is happening or not) reasons, such as for changing obs properties or time tracking, do not have to abide by this restriction if it is not for an advantage in the run (at the discretion of verifiers). #entangled[Entangled Rule(s):]\ #entangled[A.3.10 is referenced by: ] #entangledRule("CE20.3.4")\ From 240bb279e90647fbc8a471ebffefef947756e982 Mon Sep 17 00:00:00 2001 From: tildejustin Date: Sat, 19 Jul 2025 22:37:47 -0400 Subject: [PATCH 10/23] split up mod and vanilla file rules --- rules.typ | 18 ++++++++---------- 1 file changed, 8 insertions(+), 10 deletions(-) diff --git a/rules.typ b/rules.typ index 9a4e650..f1abebf 100644 --- a/rules.typ +++ b/rules.typ @@ -226,16 +226,7 @@ A.3.8) The chat text must be visible and legible in the video recording and the A.3.9) Runs must not intend to be as slow as possible. At a minimum, an attempt must be made to finish the run quickly.\ A.3.10) World and log files produced by the vanilla game must not be to be read before or during the run.\ Exception: Advancement or statistics files may be read by people and programs.\ -\ -Historically, macros have had limited allowances to read the logs in order to determine game state. -While State Output now exists for this, these old macros are still allowed.\ -\ -Files created by mods are generally allowed to be read, however there are some restrictions to avoid giving an undue advantage to players using mods.\ -\ -wpstateout.txt state should not be used during a run, as it was designed and allowed for reset macros, which means it was not intended to be allowed for use during a run and provides more information than is necessarily appropriate or justified. -Specifically, the paused and gamescreenopen states must be treated as the same for any scripts or macros that run after the timer starts. -Use of wpstateout.txt state in scripts for aesthetic or continuous (with no regard to whether a run is happening or not) reasons, such as for changing obs properties or time tracking, do not have to abide by this restriction if it is not for an advantage in the run (at the discretion of verifiers). - +Exception: Limited allowances were given for specific reset macros to read logs to get game state before state output was available. these allowances are still in place for only those specific macros or for use without Fabric Loader.\ #entangled[Entangled Rule(s):]\ #entangled[A.3.10 is referenced by: ] #entangledRule("CE20.3.4")\ #entangled[A.3.10 is subject to an exception by: ] #entangledRule("C.2.1")\ @@ -473,6 +464,13 @@ Allowed behaviours include but are not limited to: - A.8.12.e) Grabbing lava from a magma ravine while waiting in the portal animation #entangled[Entangled Rule(s):]\ #entangled[A.8.12 is referenced by: ] #entangledRule("A.8.1.f")\ +A.8.13) Anchiale, antiresourcereload, atum, chunkcacher, fastreset, lazystronghold, no-paus, seedqueue, setspawnmod, standardsettings, state-output, tabfocus, and worldpreview are resetting mods and must not be interacted with after the start of the gameplay segment. The Use Planar Fog sodium setting emulates hardware and must not be modified during the run.\ +Exception: Using wpstateout.txt as a performant replacement for other legal checks is permitted. +Use of wpstateout.txt for aesthetic or continuous (with no regard to whether a run is happening or not) reasons, such as for changing obs properties or time tracking, is permitted if it is not for an advantage in the run (at the discretion of verifiers).\ +#formatNote[Examples: +Checking for "inworld," with no regard to the substate in place of title checking in 1.15.2+ is permitted. +Checking for both the paused and gamescreenopen states as a replacement for checking if the cursor is grabbed is also permitted. +] == A.9: Multi-Instance Rules A.9.1) If multiple instances of Minecraft are opened simultaneously, they must each be in different directories (.minecraft folders).\ From 505bf337ae8b5dea2e618283dff1495a58608c7d Mon Sep 17 00:00:00 2001 From: tildejustin Date: Sat, 19 Jul 2025 22:38:46 -0400 Subject: [PATCH 11/23] capital T --- rules.typ | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/rules.typ b/rules.typ index f1abebf..bbb6e39 100644 --- a/rules.typ +++ b/rules.typ @@ -226,7 +226,7 @@ A.3.8) The chat text must be visible and legible in the video recording and the A.3.9) Runs must not intend to be as slow as possible. At a minimum, an attempt must be made to finish the run quickly.\ A.3.10) World and log files produced by the vanilla game must not be to be read before or during the run.\ Exception: Advancement or statistics files may be read by people and programs.\ -Exception: Limited allowances were given for specific reset macros to read logs to get game state before state output was available. these allowances are still in place for only those specific macros or for use without Fabric Loader.\ +Exception: Limited allowances were given for specific reset macros to read logs to get game state before state output was available. These allowances are still in place for only those specific macros or for use without Fabric Loader.\ #entangled[Entangled Rule(s):]\ #entangled[A.3.10 is referenced by: ] #entangledRule("CE20.3.4")\ #entangled[A.3.10 is subject to an exception by: ] #entangledRule("C.2.1")\ From 659ca990b94cd052bbfffc3d0a60addd15a06395 Mon Sep 17 00:00:00 2001 From: tildejustin Date: Sat, 19 Jul 2025 22:39:42 -0400 Subject: [PATCH 12/23] capitalize obs --- rules.typ | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/rules.typ b/rules.typ index bbb6e39..3dec23d 100644 --- a/rules.typ +++ b/rules.typ @@ -466,7 +466,7 @@ Allowed behaviours include but are not limited to: #entangled[A.8.12 is referenced by: ] #entangledRule("A.8.1.f")\ A.8.13) Anchiale, antiresourcereload, atum, chunkcacher, fastreset, lazystronghold, no-paus, seedqueue, setspawnmod, standardsettings, state-output, tabfocus, and worldpreview are resetting mods and must not be interacted with after the start of the gameplay segment. The Use Planar Fog sodium setting emulates hardware and must not be modified during the run.\ Exception: Using wpstateout.txt as a performant replacement for other legal checks is permitted. -Use of wpstateout.txt for aesthetic or continuous (with no regard to whether a run is happening or not) reasons, such as for changing obs properties or time tracking, is permitted if it is not for an advantage in the run (at the discretion of verifiers).\ +Use of wpstateout.txt for aesthetic or continuous (with no regard to whether a run is happening or not) reasons, such as for changing OBS properties or time tracking, is permitted if it is not for an advantage in the run (at the discretion of verifiers).\ #formatNote[Examples: Checking for "inworld," with no regard to the substate in place of title checking in 1.15.2+ is permitted. Checking for both the paused and gamescreenopen states as a replacement for checking if the cursor is grabbed is also permitted. From 3df75898c718592162bebdbd69ffdb1ea45892b5 Mon Sep 17 00:00:00 2001 From: tildejustin Date: Sun, 20 Jul 2025 14:55:01 -0400 Subject: [PATCH 13/23] labels labels labels --- rules.typ | 23 ++++++++++------------- 1 file changed, 10 insertions(+), 13 deletions(-) diff --git a/rules.typ b/rules.typ index 3dec23d..c9d6038 100644 --- a/rules.typ +++ b/rules.typ @@ -224,9 +224,9 @@ A.3.6) If you play one instance of Minecraft and then switch to playing another, A.3.7) Non-default shaders, including Super Secret Settings, must not be used.\ A.3.8) The chat text must be visible and legible in the video recording and the Chat setting must be either Shown or Commands Only.\ A.3.9) Runs must not intend to be as slow as possible. At a minimum, an attempt must be made to finish the run quickly.\ -A.3.10) World and log files produced by the vanilla game must not be to be read before or during the run.\ -Exception: Advancement or statistics files may be read by people and programs.\ -Exception: Limited allowances were given for specific reset macros to read logs to get game state before state output was available. These allowances are still in place for only those specific macros or for use without Fabric Loader.\ +A.3.10) World and log files produced by the vanilla game must not be to be read before or during the run. +- A.3.10.a) Exception: Advancement or statistics files may be read by people and programs. +- A.3.10.c) Exception: Limited allowances were given for specific reset macros to read logs to get game state before state output was available. These allowances are still in place for only those specific macros or for use without Fabric Loader.\ #entangled[Entangled Rule(s):]\ #entangled[A.3.10 is referenced by: ] #entangledRule("CE20.3.4")\ #entangled[A.3.10 is subject to an exception by: ] #entangledRule("C.2.1")\ @@ -464,12 +464,11 @@ Allowed behaviours include but are not limited to: - A.8.12.e) Grabbing lava from a magma ravine while waiting in the portal animation #entangled[Entangled Rule(s):]\ #entangled[A.8.12 is referenced by: ] #entangledRule("A.8.1.f")\ -A.8.13) Anchiale, antiresourcereload, atum, chunkcacher, fastreset, lazystronghold, no-paus, seedqueue, setspawnmod, standardsettings, state-output, tabfocus, and worldpreview are resetting mods and must not be interacted with after the start of the gameplay segment. The Use Planar Fog sodium setting emulates hardware and must not be modified during the run.\ -Exception: Using wpstateout.txt as a performant replacement for other legal checks is permitted. -Use of wpstateout.txt for aesthetic or continuous (with no regard to whether a run is happening or not) reasons, such as for changing OBS properties or time tracking, is permitted if it is not for an advantage in the run (at the discretion of verifiers).\ -#formatNote[Examples: -Checking for "inworld," with no regard to the substate in place of title checking in 1.15.2+ is permitted. -Checking for both the paused and gamescreenopen states as a replacement for checking if the cursor is grabbed is also permitted. +A.8.13) Anchiale, antiresourcereload, atum, chunkcacher, fastreset, lazystronghold, no-paus, seedqueue, setspawnmod, standardsettings, state-output, tabfocus, and worldpreview are resetting mods and must not be interacted with after the start of the gameplay segment. The Use Planar Fog sodium setting emulates hardware and must not be modified after the world is first rendered.\ +- A.8.13.a) Exception: Using wpstateout.txt as a performant replacement for other legal checks is permitted. Use of wpstateout.txt for aesthetic or continuous (with no regard to whether a run is happening or not) reasons, such as for changing OBS properties or time tracking, is permitted if it is not for an advantage in the run (at the discretion of verifiers).\ +- #formatNote[A.8.13.a.note) Examples: + - Checking for "inworld," with no regard to the substate in place of title checking in 1.15.2+ is permitted. + - Checking for both the paused and gamescreenopen states as a replacement for checking if the cursor is grabbed is also permitted. ] == A.9: Multi-Instance Rules @@ -496,13 +495,11 @@ A.10.4) Macros are not allowed to be triggered during a run. #entangled[Entangled Rule(s):]\ #entangled[A.10.4 is nullified by: ] #entangledRules(("CE20.2.3", "CE20.3.2"))\ A.10.5) Macros may only be used to reset worlds if resets are triggered by player input. Multiple simultaneous resets may be triggered by a single player input. -- A.10.5.a) Clarification: Reading game files or screen reading for determining whether to reset or aiding the player in resetting is not allowed. +- A.10.5.a) Clarification: Reading game files or screen reading to reset or to aid the player in resetting is not allowed. - A.10.5.b) Clarification: Automatic resetting, or resetting based on anything other than player input is not allowed. #entangled[Entangled Rule(s):]\ #entangled[A.10.5 is subject to an exception by: ] #entangledRule("C.2.1")\ -A.10.6) Any program or macro that does screen reading or listens to game audio for an advantage (at the discretion of verifiers) must not be used. Screen reading is using the data of the pixels of the game window to programmatically capture information from the game (e.g. color for biomes, text recognition for F3, enchantment cracking, inventory contents, etc). -- A.10.6.a) Clarification: Any attempt to get around this rule will not be tolerated (i.e. taking a screenshot and a program reading from that, etc. would not be allowed). -- A.10.6.b) Clarification: This does not include recording software. +A.10.6) Any program or macro that does screen reading or listens to game audio for an advantage (at the discretion of verifiers) must not be used. Screen reading is using the data of the pixels of the game window to programmatically capture information from the game (e.g. color for biomes, text recognition for F3, enchantment cracking, inventory contents, etc). Any attempt to get around this rule will not be tolerated (i.e. taking a screenshot and a program reading from that, etc.). == A.11: External Resource Rules #entangled[Entangled Rule(s):]\ From 61d0185f36d773bfcdd713357a7364240bdf7a4b Mon Sep 17 00:00:00 2001 From: tildejustin Date: Sun, 20 Jul 2025 14:59:02 -0400 Subject: [PATCH 14/23] example flavor text --- rules.typ | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/rules.typ b/rules.typ index c9d6038..3a42810 100644 --- a/rules.typ +++ b/rules.typ @@ -466,9 +466,9 @@ Allowed behaviours include but are not limited to: #entangled[A.8.12 is referenced by: ] #entangledRule("A.8.1.f")\ A.8.13) Anchiale, antiresourcereload, atum, chunkcacher, fastreset, lazystronghold, no-paus, seedqueue, setspawnmod, standardsettings, state-output, tabfocus, and worldpreview are resetting mods and must not be interacted with after the start of the gameplay segment. The Use Planar Fog sodium setting emulates hardware and must not be modified after the world is first rendered.\ - A.8.13.a) Exception: Using wpstateout.txt as a performant replacement for other legal checks is permitted. Use of wpstateout.txt for aesthetic or continuous (with no regard to whether a run is happening or not) reasons, such as for changing OBS properties or time tracking, is permitted if it is not for an advantage in the run (at the discretion of verifiers).\ -- #formatNote[A.8.13.a.note) Examples: - - Checking for "inworld," with no regard to the substate in place of title checking in 1.15.2+ is permitted. - - Checking for both the paused and gamescreenopen states as a replacement for checking if the cursor is grabbed is also permitted. +- #formatNote[A.8.13.a.note) Examples of permitted uses of wpstateout.txt include: + - Checking for "inworld," with no regard to the substate in place of title checking in 1.15.2+. + - Checking for both the paused and gamescreenopen states as a replacement for checking if the cursor is grabbed. ] == A.9: Multi-Instance Rules From 6f02a4f30b2587a06c914e5d52143b4fdc14f82c Mon Sep 17 00:00:00 2001 From: tildejustin Date: Sun, 20 Jul 2025 14:59:50 -0400 Subject: [PATCH 15/23] people? players --- rules.typ | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/rules.typ b/rules.typ index 3a42810..50a80d8 100644 --- a/rules.typ +++ b/rules.typ @@ -225,7 +225,7 @@ A.3.7) Non-default shaders, including Super Secret Settings, must not be used.\ A.3.8) The chat text must be visible and legible in the video recording and the Chat setting must be either Shown or Commands Only.\ A.3.9) Runs must not intend to be as slow as possible. At a minimum, an attempt must be made to finish the run quickly.\ A.3.10) World and log files produced by the vanilla game must not be to be read before or during the run. -- A.3.10.a) Exception: Advancement or statistics files may be read by people and programs. +- A.3.10.a) Exception: Advancement or statistics files may be read by players and programs. - A.3.10.c) Exception: Limited allowances were given for specific reset macros to read logs to get game state before state output was available. These allowances are still in place for only those specific macros or for use without Fabric Loader.\ #entangled[Entangled Rule(s):]\ #entangled[A.3.10 is referenced by: ] #entangledRule("CE20.3.4")\ From 121e309d77f7b228b33dae14f79686eb8680a2c4 Mon Sep 17 00:00:00 2001 From: tildejustin Date: Sun, 20 Jul 2025 15:08:44 -0400 Subject: [PATCH 16/23] unnecessary backslashes --- rules.typ | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/rules.typ b/rules.typ index 50a80d8..dadee98 100644 --- a/rules.typ +++ b/rules.typ @@ -226,7 +226,7 @@ A.3.8) The chat text must be visible and legible in the video recording and the A.3.9) Runs must not intend to be as slow as possible. At a minimum, an attempt must be made to finish the run quickly.\ A.3.10) World and log files produced by the vanilla game must not be to be read before or during the run. - A.3.10.a) Exception: Advancement or statistics files may be read by players and programs. -- A.3.10.c) Exception: Limited allowances were given for specific reset macros to read logs to get game state before state output was available. These allowances are still in place for only those specific macros or for use without Fabric Loader.\ +- A.3.10.c) Exception: Limited allowances were given for specific reset macros to read logs to get game state before state output was available. These allowances are still in place for only those specific macros or for use without Fabric Loader. #entangled[Entangled Rule(s):]\ #entangled[A.3.10 is referenced by: ] #entangledRule("CE20.3.4")\ #entangled[A.3.10 is subject to an exception by: ] #entangledRule("C.2.1")\ @@ -464,11 +464,11 @@ Allowed behaviours include but are not limited to: - A.8.12.e) Grabbing lava from a magma ravine while waiting in the portal animation #entangled[Entangled Rule(s):]\ #entangled[A.8.12 is referenced by: ] #entangledRule("A.8.1.f")\ -A.8.13) Anchiale, antiresourcereload, atum, chunkcacher, fastreset, lazystronghold, no-paus, seedqueue, setspawnmod, standardsettings, state-output, tabfocus, and worldpreview are resetting mods and must not be interacted with after the start of the gameplay segment. The Use Planar Fog sodium setting emulates hardware and must not be modified after the world is first rendered.\ -- A.8.13.a) Exception: Using wpstateout.txt as a performant replacement for other legal checks is permitted. Use of wpstateout.txt for aesthetic or continuous (with no regard to whether a run is happening or not) reasons, such as for changing OBS properties or time tracking, is permitted if it is not for an advantage in the run (at the discretion of verifiers).\ -- #formatNote[A.8.13.a.note) Examples of permitted uses of wpstateout.txt include: - - Checking for "inworld," with no regard to the substate in place of title checking in 1.15.2+. - - Checking for both the paused and gamescreenopen states as a replacement for checking if the cursor is grabbed. +A.8.13) Anchiale, antiresourcereload, atum, chunkcacher, fastreset, lazystronghold, no-paus, seedqueue, setspawnmod, standardsettings, state-output, tabfocus, and worldpreview are resetting mods and must not be interacted with after the start of the gameplay segment. The Use Planar Fog sodium setting emulates hardware and must not be modified after the world is first rendered. +- A.8.13.a) Exception: Using wpstateout.txt as a performant replacement for other legal checks is permitted. Use of wpstateout.txt for aesthetic or continuous (with no regard to whether a run is happening or not) reasons, such as for changing OBS properties or time tracking, is permitted if it is not for an advantage in the run (at the discretion of verifiers). +- #formatNote[A.8.13.a.note) Examples of permitted uses of wpstateout.txt include:\ +Checking for "inworld," with no regard to the substate in place of title checking in 1.15.2+.\ +Checking for both the paused and gamescreenopen states as a replacement for checking if the cursor is grabbed. ] == A.9: Multi-Instance Rules From 06d9457da0f8bedc4d474789651eb643fa038ae6 Mon Sep 17 00:00:00 2001 From: tildejustin Date: Wed, 23 Jul 2025 22:29:02 -0400 Subject: [PATCH 17/23] address review --- rules.typ | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/rules.typ b/rules.typ index dadee98..9090a4c 100644 --- a/rules.typ +++ b/rules.typ @@ -226,7 +226,7 @@ A.3.8) The chat text must be visible and legible in the video recording and the A.3.9) Runs must not intend to be as slow as possible. At a minimum, an attempt must be made to finish the run quickly.\ A.3.10) World and log files produced by the vanilla game must not be to be read before or during the run. - A.3.10.a) Exception: Advancement or statistics files may be read by players and programs. -- A.3.10.c) Exception: Limited allowances were given for specific reset macros to read logs to get game state before state output was available. These allowances are still in place for only those specific macros or for use without Fabric Loader. +- A.3.10.c) Exception: Limited allowances were given for specific reset macros to read logs to get game state before wpstateout.txt was available. These allowances are still in place for only those specific macros or for use without Fabric Loader. #entangled[Entangled Rule(s):]\ #entangled[A.3.10 is referenced by: ] #entangledRule("CE20.3.4")\ #entangled[A.3.10 is subject to an exception by: ] #entangledRule("C.2.1")\ @@ -467,8 +467,8 @@ Allowed behaviours include but are not limited to: A.8.13) Anchiale, antiresourcereload, atum, chunkcacher, fastreset, lazystronghold, no-paus, seedqueue, setspawnmod, standardsettings, state-output, tabfocus, and worldpreview are resetting mods and must not be interacted with after the start of the gameplay segment. The Use Planar Fog sodium setting emulates hardware and must not be modified after the world is first rendered. - A.8.13.a) Exception: Using wpstateout.txt as a performant replacement for other legal checks is permitted. Use of wpstateout.txt for aesthetic or continuous (with no regard to whether a run is happening or not) reasons, such as for changing OBS properties or time tracking, is permitted if it is not for an advantage in the run (at the discretion of verifiers). - #formatNote[A.8.13.a.note) Examples of permitted uses of wpstateout.txt include:\ -Checking for "inworld," with no regard to the substate in place of title checking in 1.15.2+.\ -Checking for both the paused and gamescreenopen states as a replacement for checking if the cursor is grabbed. +- Checking for "inworld," with no regard to the substate in place of title checking in 1.15.2+.\ +- Checking for both the paused and gamescreenopen states as a replacement for checking if the cursor is grabbed. ] == A.9: Multi-Instance Rules @@ -499,7 +499,7 @@ A.10.5) Macros may only be used to reset worlds if resets are triggered - A.10.5.b) Clarification: Automatic resetting, or resetting based on anything other than player input is not allowed. #entangled[Entangled Rule(s):]\ #entangled[A.10.5 is subject to an exception by: ] #entangledRule("C.2.1")\ -A.10.6) Any program or macro that does screen reading or listens to game audio for an advantage (at the discretion of verifiers) must not be used. Screen reading is using the data of the pixels of the game window to programmatically capture information from the game (e.g. color for biomes, text recognition for F3, enchantment cracking, inventory contents, etc). Any attempt to get around this rule will not be tolerated (i.e. taking a screenshot and a program reading from that, etc.). +A.10.6) Any program or macro that screen reads or listens to game audio for an advantage (at the discretion of verifiers) must not be used. Screen reading is using the data of the pixels of the game window to programmatically capture information from the game (e.g. color for biomes, text recognition for F3, enchantment cracking, inventory contents, etc). Any attempt to get around this rule will not be tolerated (i.e. taking a screenshot and a program reading from that, etc.). == A.11: External Resource Rules #entangled[Entangled Rule(s):]\ From 759560732ae95a83e8e9cce715cc74554ac0a897 Mon Sep 17 00:00:00 2001 From: tildejustin Date: Sat, 2 Aug 2025 07:57:08 -0400 Subject: [PATCH 18/23] remove e.1.2. it's a reminder dressed up as a rule and interacting with fast reset is now (and always was) blanket banned outside resetting so this is obviously implied, nothing special about glitched --- rules.typ | 2 -- 1 file changed, 2 deletions(-) diff --git a/rules.typ b/rules.typ index 9090a4c..4e4d1db 100644 --- a/rules.typ +++ b/rules.typ @@ -694,8 +694,6 @@ D.1.4) The game must not be closed and reopened during a run. == E.1: Glitched Runs E.1.1) Glitched runs must perform at least one glitch during the run that is disallowed in glitchless runs. - E.1.1.a) Clarification: Runs without an internal/external split classification may choose to Save and Quit/crash the game or refrain from doing so. -E.1.2) The FastReset quit button (menu.quitWorld) must not be used during the run. -- E.1.2.a) If menu.quitWorld is used during the run, it may still be verified if it is determined to not affect the run (at the discretion of verifiers). E.1.3) If you use Task Manager or another program which forcefully closes the game, you should include a video of this during the run.\ E.1.4) External Arbitrary Code Execution (ACE) must not be used. - E.1.4.a) Example: Log4j exploit From f993267b68ebbb74d4ebd929fc0be6029dab5347 Mon Sep 17 00:00:00 2001 From: tildejustin Date: Thu, 12 Feb 2026 22:52:28 -0500 Subject: [PATCH 19/23] hermes and dll injection and a bit of a rewrite --- rules.typ | 18 +++++++++++++----- 1 file changed, 13 insertions(+), 5 deletions(-) diff --git a/rules.typ b/rules.typ index 4e4d1db..6b9e015 100644 --- a/rules.typ +++ b/rules.typ @@ -464,12 +464,20 @@ Allowed behaviours include but are not limited to: - A.8.12.e) Grabbing lava from a magma ravine while waiting in the portal animation #entangled[Entangled Rule(s):]\ #entangled[A.8.12 is referenced by: ] #entangledRule("A.8.1.f")\ -A.8.13) Anchiale, antiresourcereload, atum, chunkcacher, fastreset, lazystronghold, no-paus, seedqueue, setspawnmod, standardsettings, state-output, tabfocus, and worldpreview are resetting mods and must not be interacted with after the start of the gameplay segment. The Use Planar Fog sodium setting emulates hardware and must not be modified after the world is first rendered. -- A.8.13.a) Exception: Using wpstateout.txt as a performant replacement for other legal checks is permitted. Use of wpstateout.txt for aesthetic or continuous (with no regard to whether a run is happening or not) reasons, such as for changing OBS properties or time tracking, is permitted if it is not for an advantage in the run (at the discretion of verifiers). -- #formatNote[A.8.13.a.note) Examples of permitted uses of wpstateout.txt include:\ -- Checking for "inworld," with no regard to the substate in place of title checking in 1.15.2+.\ -- Checking for both the paused and gamescreenopen states as a replacement for checking if the cursor is grabbed. +A.8.13) Anchiale, antiresourcereload, atum, chunkcacher, fastreset, hermes, hermes-core, lazystronghold, no-paus, seedqueue, setspawnmod, standardsettings, state-output, tabfocus, and worldpreview are resetting mods and must not be interacted with after the start of the gameplay segment. Hermes and State Output write to files, and except for allowed cases those files must not be read after the start of the gameplay segment. The Use Planar Fog sodium setting emulates hardware and must not be modified after the world is first rendered. +- A.8.13.a) Exception: Using wpstateout.txt, state.json, or other mod-outputted instance state as a performant replacement for checks possible in the unmodified game is permitted. Use of state for aesthetic or continuous (with no regard to whether a run is happening or not) reasons, such as for changing OBS properties or time tracking, is permitted if it is not for an advantage in the run (at the discretion of verifiers). +- #formatNote[A.8.13.a.note) Examples of permitted uses of state include:\ +- Checking for both the paused and gamescreenopen states in wpstateout.txt or checking for a non-null screen in state.json as a replacement for checking if the cursor is grabbed. +- A.8.13.b) Exception: Conditional functionality related to resetting the world (e.g. via the Atum's Create New World key) is allowed. This includes common external tool binds such as "Safe Reset" and "Reset Before 20 Seconds". ] +A.8.14) Certain approved tools are allowed to read Hermes world files during the run. These are: +A.8.14.a) PaceMan Tracker +A.8.14.b) AATool +A.8.14.c) Advancely +#formatNote[ +A.8.14.note) Use of otherwise restricted mod-outputted data may be allowed on an per-application basis though formal legalization or permission from the mod team. If you have a prospective use that is not intended to create an advantage in the run, you should make a thread. +] +A.8.15) DLL injection is allowed, but injection of DLLs that are not explicitly whitlelisted may result in run rejection. The list of whitelisted DLLs is maintained at legal-dlls.csv. Injection of any explicitly allowed DLL is allowed only if LibLogger.dll is also injected. Program-independent DLLs such as for OBS Game Capture and Discord Game Overlay are generally allowed. == A.9: Multi-Instance Rules A.9.1) If multiple instances of Minecraft are opened simultaneously, they must each be in different directories (.minecraft folders).\ From a4753ed8a8401b05540928965c51553cbbc0c2c4 Mon Sep 17 00:00:00 2001 From: tildejustin Date: Fri, 13 Feb 2026 19:33:37 -0500 Subject: [PATCH 20/23] rewrite a bit more --- rules.typ | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/rules.typ b/rules.typ index 6b9e015..6fb7753 100644 --- a/rules.typ +++ b/rules.typ @@ -224,7 +224,7 @@ A.3.6) If you play one instance of Minecraft and then switch to playing another, A.3.7) Non-default shaders, including Super Secret Settings, must not be used.\ A.3.8) The chat text must be visible and legible in the video recording and the Chat setting must be either Shown or Commands Only.\ A.3.9) Runs must not intend to be as slow as possible. At a minimum, an attempt must be made to finish the run quickly.\ -A.3.10) World and log files produced by the vanilla game must not be to be read before or during the run. +A.3.10) World and log files produced by the vanilla game must not be read before or during the run. - A.3.10.a) Exception: Advancement or statistics files may be read by players and programs. - A.3.10.c) Exception: Limited allowances were given for specific reset macros to read logs to get game state before wpstateout.txt was available. These allowances are still in place for only those specific macros or for use without Fabric Loader. #entangled[Entangled Rule(s):]\ @@ -464,8 +464,9 @@ Allowed behaviours include but are not limited to: - A.8.12.e) Grabbing lava from a magma ravine while waiting in the portal animation #entangled[Entangled Rule(s):]\ #entangled[A.8.12 is referenced by: ] #entangledRule("A.8.1.f")\ -A.8.13) Anchiale, antiresourcereload, atum, chunkcacher, fastreset, hermes, hermes-core, lazystronghold, no-paus, seedqueue, setspawnmod, standardsettings, state-output, tabfocus, and worldpreview are resetting mods and must not be interacted with after the start of the gameplay segment. Hermes and State Output write to files, and except for allowed cases those files must not be read after the start of the gameplay segment. The Use Planar Fog sodium setting emulates hardware and must not be modified after the world is first rendered. -- A.8.13.a) Exception: Using wpstateout.txt, state.json, or other mod-outputted instance state as a performant replacement for checks possible in the unmodified game is permitted. Use of state for aesthetic or continuous (with no regard to whether a run is happening or not) reasons, such as for changing OBS properties or time tracking, is permitted if it is not for an advantage in the run (at the discretion of verifiers). +A.8.13) Anchiale, antiresourcereload, atum, chunkcacher, fastreset, hermes, hermes-core, lazystronghold, no-paus, seedqueue, setspawnmod, standardsettings, state-output, tabfocus, and worldpreview are resetting mods and must not be interacted with after the start of the gameplay segment. The Use Planar Fog sodium setting emulates hardware and must not be modified after the world is first rendered. +A.8.14) Hermes, State Output, SpeedRunIGT, WorldPreview write out files, and except for allowed cases those files must not be read after the start of the gameplay segment. +- A.8.14.a) Exception: Using wpstateout.txt (State Output and previously WorldPreview), state.json (Hermes), record.json (SpeedRunIGT), or other mod-outputted instance state as a performant replacement for checks possible in the unmodified game is permitted. Use of the data in these files for aesthetic, continuous (with no regard to whether a run is happening or not), or generally unproblematic reasons, such as for changing OBS properties, time tracking, Atum reset counts, pausing music, etc. is permitted if it is not for an advantage in the run (at the discretion of verifiers). If you think your use of mod state could be considered an attempt to create a mod-only advantage and would like clarification on if your particular use is allowed, please open a thread. - #formatNote[A.8.13.a.note) Examples of permitted uses of state include:\ - Checking for both the paused and gamescreenopen states in wpstateout.txt or checking for a non-null screen in state.json as a replacement for checking if the cursor is grabbed. - A.8.13.b) Exception: Conditional functionality related to resetting the world (e.g. via the Atum's Create New World key) is allowed. This includes common external tool binds such as "Safe Reset" and "Reset Before 20 Seconds". @@ -475,9 +476,9 @@ A.8.14.a) PaceMan Tracker A.8.14.b) AATool A.8.14.c) Advancely #formatNote[ -A.8.14.note) Use of otherwise restricted mod-outputted data may be allowed on an per-application basis though formal legalization or permission from the mod team. If you have a prospective use that is not intended to create an advantage in the run, you should make a thread. +A.8.14.note) Use of otherwise restricted mod-outputted data may be allowed on an per-application basis though formal legalization or permission from the mod team. If you have a prospective use that is not intended to create an advantage in the run, you should open a thread. ] -A.8.15) DLL injection is allowed, but injection of DLLs that are not explicitly whitlelisted may result in run rejection. The list of whitelisted DLLs is maintained at legal-dlls.csv. Injection of any explicitly allowed DLL is allowed only if LibLogger.dll is also injected. Program-independent DLLs such as for OBS Game Capture and Discord Game Overlay are generally allowed. +A.8.15) DLL injection is allowed, but injection of DLLs that are not explicitly whitelisted may result in run rejection. The list of whitelisted DLLs is maintained at legal-dlls.csv. Injection of any explicitly allowed DLL is allowed only if LibLogger.dll is also injected. Program-independent DLLs such as for OBS Game Capture and Discord Game Overlay are generally allowed. == A.9: Multi-Instance Rules A.9.1) If multiple instances of Minecraft are opened simultaneously, they must each be in different directories (.minecraft folders).\ From 9449dc02c5ee67eb1b9cc9bf4f83d1e2577cdb93 Mon Sep 17 00:00:00 2001 From: tildejustin Date: Fri, 13 Feb 2026 21:03:28 -0500 Subject: [PATCH 21/23] genericize liblogger reference --- rules.typ | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/rules.typ b/rules.typ index 6fb7753..40ec4c3 100644 --- a/rules.typ +++ b/rules.typ @@ -478,7 +478,7 @@ A.8.14.c) Advancely #formatNote[ A.8.14.note) Use of otherwise restricted mod-outputted data may be allowed on an per-application basis though formal legalization or permission from the mod team. If you have a prospective use that is not intended to create an advantage in the run, you should open a thread. ] -A.8.15) DLL injection is allowed, but injection of DLLs that are not explicitly whitelisted may result in run rejection. The list of whitelisted DLLs is maintained at legal-dlls.csv. Injection of any explicitly allowed DLL is allowed only if LibLogger.dll is also injected. Program-independent DLLs such as for OBS Game Capture and Discord Game Overlay are generally allowed. +A.8.15) DLL injection is allowed, but injection of DLLs that are not explicitly whitelisted may result in run rejection. The list of whitelisted DLLs is maintained at legal-dlls.csv. Injection of any explicitly allowed DLL is allowed only if a an allowed LibLogger build is also injected. Program-independent DLLs such as for OBS Game Capture and Discord Game Overlay are generally allowed. == A.9: Multi-Instance Rules A.9.1) If multiple instances of Minecraft are opened simultaneously, they must each be in different directories (.minecraft folders).\ From 0a2356a5d28f22021f9fb6e7c99b961c3c733a2e Mon Sep 17 00:00:00 2001 From: tildejustin Date: Fri, 13 Feb 2026 22:13:44 -0500 Subject: [PATCH 22/23] link to legal-builds and legal-dlls --- rules.typ | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/rules.typ b/rules.typ index 40ec4c3..9e35005 100644 --- a/rules.typ +++ b/rules.typ @@ -450,7 +450,7 @@ A.8.3) All versions of Legacy Fabric Intermediaries are allowed. - A.8.3.a) Clarification: Legacy Fabric LWJGL must not be used, which is bundled in the first party Legacy Fabric MultiMC Instances. A.8.4) All official LWJGL 3 releases up to v3.3.3 are allowed for Minecraft 1.13+. Official GLFW versions up to 3.3.8 are allowed. Woofdoggo's #formatLink("https://github.com/tesselslate/resetti/blob/d8eb8634c2efe60e9a1c19f3cf5c30288cc93cfc/contrib/glfw-xinput.patch")[Linux GLFW xinput patch] or #formatLink("https://github.com/tesselslate/waywall/blob/ad569de1ddae6b034c7095795a42f044746a55a7/contrib/glfw.patch")[GLFW patch for Waywall] may be used.\ A.8.5) Rules relating to what Fabric mods are legal and the conditions of their use are documented on the #formatLink("https://github.com/Minecraft-Java-Edition-Speedrunning/legal-mods")[legal-mods] GitHub repository. Some mods have special conditions of use, such as for use in Set Seed categories only, as described in the README.md. -- #formatNote[A.8.5.note) legal-builds.csv documents every currently legal jar file. Use of a Fabric mod jar not listed in that file at the time of the run is illegal and will cause your run to be rejected. The files stored in the GitHub are not intended users to download directly and instead we recommend you use other tools provided to do so, linked in the README. Previously legal builds of mods are often made illegal upon updates for closer vanilla parity or bug fixes, do not assume that just because the mods you have installed were legal at the time they are still legal now. A grace period of a month to update mods is typically given for parity updates, this is often shorter for bug fixes.] +- #formatNote[A.8.5.note) #formatLink("https://github.com/Minecraft-Java-Edition-Speedrunning/legal-mods/blob/main/legal-builds.csv")[legal-builds.csv] documents every currently legal jar file. Use of a Fabric mod jar not listed in that file at the time of the run is illegal and will cause your run to be rejected. The files stored in the GitHub are not intended users to download directly and instead we recommend you use other tools provided to do so, linked in the README. Previously legal builds of mods are often made illegal upon updates for closer vanilla parity or bug fixes, do not assume that just because the mods you have installed were legal at the time they are still legal now. A grace period of a month to update mods is typically given for parity updates, this is often shorter for bug fixes.] A.8.9) If SeedQueue is used, you must not increase the max queued seeds beyond 30. The mod enforces this limit, you must not make any attempts to bypass it.\ A.8.10) All versions of Ornithe Intermediaries are allowed.\ A.8.11) Fabric Intermediaries are allowed.\ @@ -478,7 +478,7 @@ A.8.14.c) Advancely #formatNote[ A.8.14.note) Use of otherwise restricted mod-outputted data may be allowed on an per-application basis though formal legalization or permission from the mod team. If you have a prospective use that is not intended to create an advantage in the run, you should open a thread. ] -A.8.15) DLL injection is allowed, but injection of DLLs that are not explicitly whitelisted may result in run rejection. The list of whitelisted DLLs is maintained at legal-dlls.csv. Injection of any explicitly allowed DLL is allowed only if a an allowed LibLogger build is also injected. Program-independent DLLs such as for OBS Game Capture and Discord Game Overlay are generally allowed. +A.8.15) DLL injection is allowed, but injection of DLLs that are not explicitly whitelisted may result in run rejection. The list of whitelisted DLLs is maintained at #formatLink("https://github.com/Minecraft-Java-Edition-Speedrunning/legal-builds/blob/main/legal-dlls.csv")[legal-dlls.csv]. Injection of any explicitly legalized DLL is allowed only if an allowed build of LibLogger is also injected. Program-independent DLLs such as for OBS Game Capture and Discord Game Overlay are generally allowed. == A.9: Multi-Instance Rules A.9.1) If multiple instances of Minecraft are opened simultaneously, they must each be in different directories (.minecraft folders).\ From 65c68156d3e130036040c548c92d4951a8ed0de6 Mon Sep 17 00:00:00 2001 From: tildejustin Date: Fri, 13 Feb 2026 22:23:35 -0500 Subject: [PATCH 23/23] remove aatool and advancely for now --- rules.typ | 2 -- 1 file changed, 2 deletions(-) diff --git a/rules.typ b/rules.typ index 9e35005..6e7bc1d 100644 --- a/rules.typ +++ b/rules.typ @@ -473,8 +473,6 @@ A.8.14) Hermes, State Output, SpeedRunIGT, WorldPreview write out files, and exc ] A.8.14) Certain approved tools are allowed to read Hermes world files during the run. These are: A.8.14.a) PaceMan Tracker -A.8.14.b) AATool -A.8.14.c) Advancely #formatNote[ A.8.14.note) Use of otherwise restricted mod-outputted data may be allowed on an per-application basis though formal legalization or permission from the mod team. If you have a prospective use that is not intended to create an advantage in the run, you should open a thread. ]