From 3f82af3f619a560f66cc3ff39534fdbb15b84366 Mon Sep 17 00:00:00 2001 From: tildejustin Date: Wed, 16 Jul 2025 00:08:45 -0400 Subject: [PATCH 01/18] add rule against automatically changing mappings --- rules.typ | 1 + 1 file changed, 1 insertion(+) diff --git a/rules.typ b/rules.typ index 85ea45f..435b5d6 100644 --- a/rules.typ +++ b/rules.typ @@ -477,6 +477,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 dc7be6fd7c3c92c413559c3dcd08ac3a9b4ae267 Mon Sep 17 00:00:00 2001 From: tildejustin Date: Wed, 16 Jul 2025 17:24:26 -0400 Subject: [PATCH 02/18] remove key mapping changing rule --- rules.typ | 1 - 1 file changed, 1 deletion(-) diff --git a/rules.typ b/rules.typ index 435b5d6..85ea45f 100644 --- a/rules.typ +++ b/rules.typ @@ -477,7 +477,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 5ae5cdbdab010de0d522ef45e52123ae2d595834 Mon Sep 17 00:00:00 2001 From: tildejustin Date: Wed, 16 Jul 2025 18:21:11 -0400 Subject: [PATCH 03/18] fix? screen reading rules --- rules.typ | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/rules.typ b/rules.typ index 85ea45f..c10dc7e 100644 --- a/rules.typ +++ b/rules.typ @@ -488,11 +488,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 cb0f4c8b498f13dcc9d9df0005a7bf3f5ac928ce Mon Sep 17 00:00:00 2001 From: tildejustin Date: Wed, 16 Jul 2025 18:23:26 -0400 Subject: [PATCH 04/18] 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 c10dc7e..b9d853a 100644 --- a/rules.typ +++ b/rules.typ @@ -225,7 +225,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 1b0875f7ccf4a6989bba73e0fac24c055f8719ae Mon Sep 17 00:00:00 2001 From: tildejustin Date: Wed, 16 Jul 2025 18:26:38 -0400 Subject: [PATCH 05/18] ban macros reading wpstateout.txt --- rules.typ | 1 + 1 file changed, 1 insertion(+) diff --git a/rules.typ b/rules.typ index b9d853a..94ac2ca 100644 --- a/rules.typ +++ b/rules.typ @@ -496,6 +496,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 50899b8c6757981b7a7f21cd5f7a7462d77a13d5 Mon Sep 17 00:00:00 2001 From: tildejustin Date: Wed, 16 Jul 2025 20:32:42 -0400 Subject: [PATCH 06/18] 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 94ac2ca..e27e192 100644 --- a/rules.typ +++ b/rules.typ @@ -493,10 +493,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 689b553b2ca2bbf30a994e12f19bbb47b0c72b13 Mon Sep 17 00:00:00 2001 From: tildejustin Date: Thu, 17 Jul 2025 18:19:44 -0400 Subject: [PATCH 07/18] 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 e27e192..9508023 100644 --- a/rules.typ +++ b/rules.typ @@ -223,10 +223,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 5659ea67d9a3a94d46c778e1cb6d02e6be3e0072 Mon Sep 17 00:00:00 2001 From: tildejustin Date: Fri, 18 Jul 2025 10:09:13 -0400 Subject: [PATCH 08/18] 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 9508023..fb36c00 100644 --- a/rules.typ +++ b/rules.typ @@ -231,8 +231,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 17b143b47470d603530360bbcc21fb6620598052 Mon Sep 17 00:00:00 2001 From: tildejustin Date: Fri, 18 Jul 2025 12:35:30 -0400 Subject: [PATCH 09/18] cursor grabbed equivalency --- rules.typ | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git a/rules.typ b/rules.typ index fb36c00..8f40cb2 100644 --- a/rules.typ +++ b/rules.typ @@ -231,11 +231,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 afd29eb640a6ed8d773964a0a1b64a13a43a873d Mon Sep 17 00:00:00 2001 From: tildejustin Date: Sat, 19 Jul 2025 22:37:47 -0400 Subject: [PATCH 10/18] 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 8f40cb2..f1b61e9 100644 --- a/rules.typ +++ b/rules.typ @@ -225,16 +225,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")\ @@ -472,6 +463,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 2bdeb5b568a993469be720011e55cb4e2ec96db1 Mon Sep 17 00:00:00 2001 From: tildejustin Date: Sat, 19 Jul 2025 22:38:46 -0400 Subject: [PATCH 11/18] capital T --- rules.typ | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/rules.typ b/rules.typ index f1b61e9..5eb6ae1 100644 --- a/rules.typ +++ b/rules.typ @@ -225,7 +225,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 6827c970c8eeb670744ac7f45b6bef4389eaec54 Mon Sep 17 00:00:00 2001 From: tildejustin Date: Sat, 19 Jul 2025 22:39:42 -0400 Subject: [PATCH 12/18] capitalize obs --- rules.typ | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/rules.typ b/rules.typ index 5eb6ae1..3c8da71 100644 --- a/rules.typ +++ b/rules.typ @@ -465,7 +465,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 135f26d45d1ceb7da1c059f6bf19de90d2e034a0 Mon Sep 17 00:00:00 2001 From: tildejustin Date: Sun, 20 Jul 2025 14:55:01 -0400 Subject: [PATCH 13/18] labels labels labels --- rules.typ | 23 ++++++++++------------- 1 file changed, 10 insertions(+), 13 deletions(-) diff --git a/rules.typ b/rules.typ index 3c8da71..2080c62 100644 --- a/rules.typ +++ b/rules.typ @@ -223,9 +223,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")\ @@ -463,12 +463,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 @@ -495,13 +494,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 043ce12f6aca96b5df110eb1d6d0b2789a7fc4da Mon Sep 17 00:00:00 2001 From: tildejustin Date: Sun, 20 Jul 2025 14:59:02 -0400 Subject: [PATCH 14/18] example flavor text --- rules.typ | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/rules.typ b/rules.typ index 2080c62..f77b629 100644 --- a/rules.typ +++ b/rules.typ @@ -465,9 +465,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 46dd34f83897c60be9839739cf071af1b071c192 Mon Sep 17 00:00:00 2001 From: tildejustin Date: Sun, 20 Jul 2025 14:59:50 -0400 Subject: [PATCH 15/18] people? players --- rules.typ | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/rules.typ b/rules.typ index f77b629..c42d172 100644 --- a/rules.typ +++ b/rules.typ @@ -224,7 +224,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 80a065c6265e581e76ece3fc119032629cf43de6 Mon Sep 17 00:00:00 2001 From: tildejustin Date: Sun, 20 Jul 2025 15:08:44 -0400 Subject: [PATCH 16/18] unnecessary backslashes --- rules.typ | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/rules.typ b/rules.typ index c42d172..228cbea 100644 --- a/rules.typ +++ b/rules.typ @@ -225,7 +225,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")\ @@ -463,11 +463,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 9eac7fe63ad1815f9a87e02a110010e04956eab0 Mon Sep 17 00:00:00 2001 From: tildejustin Date: Wed, 23 Jul 2025 22:29:02 -0400 Subject: [PATCH 17/18] address review --- rules.typ | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/rules.typ b/rules.typ index 228cbea..bbdac00 100644 --- a/rules.typ +++ b/rules.typ @@ -225,7 +225,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")\ @@ -466,8 +466,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 @@ -498,7 +498,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 c62c4147aeca9f73d47755acbc0085af2cd8a1e1 Mon Sep 17 00:00:00 2001 From: tildejustin Date: Sat, 2 Aug 2025 07:57:08 -0400 Subject: [PATCH 18/18] 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 bbdac00..fa23334 100644 --- a/rules.typ +++ b/rules.typ @@ -693,8 +693,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