Data resetting: Difference between revisions

101 bytes added ,  14 April 2019
(Turns out any buried north object that can clone will cause a data reset)
Line 17: Line 17:
* '''[14, 32]''' stores the current keystroke's buffer state: 1 if a keystroke is in buffer (more than one keystroke has been attempted within one turn) and 0 if it is not.
* '''[14, 32]''' stores the current keystroke's buffer state: 1 if a keystroke is in buffer (more than one keystroke has been attempted within one turn) and 0 if it is not.
* '''[18, 32]''' and '''[20, 32]''' store the x- and y-directions of the keystroke. Note that one of these must always be zero.
* '''[18, 32]''' and '''[20, 32]''' store the x- and y-directions of the keystroke. Note that one of these must always be zero.
* '''[22, 32]''' stores Chip's [[Death message|autopsy report]]:
* '''[22, 32]''' stores Chip's [[Death message|autopsy report]] (of note is that this is the only reset that ''requires'' a north clone block and not any creature):
** 0. Alive
** 0. Alive
** 1. [[Water|Drowned]]
** 1. [[Water|Drowned]]
Line 28: Line 28:
* '''[28, 32]''' stores the amount of monsters in the monster list before the player starts playing the level.
* '''[28, 32]''' stores the amount of monsters in the monster list before the player starts playing the level.
* '''[30, 32]''' and '''[31, 32]''' store the coordinates of the initial position of the first monster in the [[monster list]].
* '''[30, 32]''' and '''[31, 32]''' store the coordinates of the initial position of the first monster in the [[monster list]].
== Necessary configuration==
== Necessary configuration==


trusted-editors
544

edits