trusted-editors
543
edits
Data resetting: Difference between revisions
m
→Specific data stored in row 32: fixed a small mistake about buffered/sliding directions
(Copied from my user page, massive rewrite, more info, a technical explanation for the glitch) |
m (→Specific data stored in row 32: fixed a small mistake about buffered/sliding directions) |
||
| Line 18: | Line 18: | ||
* '''(12, 32)''' stores Chip's sliding state: 1 if he is on any [[sliding tile]] and 0 if he is not. | * '''(12, 32)''' stores Chip's sliding state: 1 if he is on any [[sliding tile]] and 0 if he 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. | * '''(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.<ref name="direction">The directions can be either +1 or -1, in the negative case (moving left or up) both pieces of the short will be used, however resetting the low-order tile (18, 20 | * '''(18, 32)''' and '''(20, 32)''' store the x- and y-directions of the keystroke. Note that one of these must always be zero.<ref name="direction">The directions can be either +1 or -1, in the negative case (moving left or up) both pieces of the short will be used, however resetting the low-order tile (18, 20, 24, or 26) is enough to halt Chip in place when moving/sliding on the respective axis.</ref> | ||
* '''(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): | * '''(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 | ||