You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: rules.typ
+8-10Lines changed: 8 additions & 10 deletions
Original file line number
Diff line number
Diff line change
@@ -225,16 +225,7 @@ A.3.8) The chat text must be visible and legible in the video recording and the
225
225
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.\
226
226
A.3.10) <A.3.10> World and log files produced by the vanilla game must not be to be read before or during the run.\
227
227
Exception: Advancement or statistics files may be read by people and programs.\
228
-
\
229
-
Historically, macros have had limited allowances to read the logs in order to determine game state.
230
-
While State Output now exists for this, these old macros are still allowed.\
231
-
\
232
-
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.\
233
-
\
234
-
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.
235
-
Specifically, the paused and gamescreenopen states must be treated as the same for any scripts or macros that run after the timer starts.
236
-
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).
237
-
228
+
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.\
238
229
#entangled[Entangled Rule(s):]\
239
230
#entangled[A.3.10 is referenced by: ] #entangledRule("CE20.3.4")\
240
231
#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:
472
463
- A.8.12.e) Grabbing lava from a magma ravine while waiting in the portal animation
473
464
#entangled[Entangled Rule(s):]\
474
465
#entangled[A.8.12 is referenced by: ] #entangledRule("A.8.1.f")\
466
+
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.\
467
+
Exception: Using wpstateout.txt as a performant replacement for other legal checks is permitted.
468
+
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).\
469
+
#formatNote[Examples:
470
+
Checking for "inworld," with no regard to the substate in place of title checking in 1.15.2+ is permitted.
471
+
Checking for both the paused and gamescreenopen states as a replacement for checking if the cursor is grabbed is also permitted.
472
+
]
475
473
476
474
== A.9: Multi-Instance Rules
477
475
A.9.1) If multiple instances of Minecraft are opened simultaneously, they must each be in different directories (.minecraft folders).\
0 commit comments