trusted-editors
544
edits
Data resetting: Difference between revisions
Turns out any buried north object that can clone will cause a data reset
Tylersontag (talk | contribs) m (Tylersontag moved page data resetting to Data resetting over redirect: revert) |
(Turns out any buried north object that can clone will cause a data reset) |
||
| Line 32: | Line 32: | ||
In order to reset data stored in a square [x, 32]: | In order to reset data stored in a square [x, 32]: | ||
*There must be a buried north [[clone | *There must be a buried north cloneable [[Object|object]] (most commonly [[Clone block|clone blocks]]) at [x, 0]. | ||
*A clone connection must be made from a [[red button]] to [x, 32]. | *A clone connection must be made from a [[red button]] to [x, 32]. | ||
*The square at [x, 31] must be free for | *The square at [x, 31] must be free for an object to clone there. | ||
When the red button is pressed, the following will occur: | When the red button is pressed, the following will occur: | ||
* The buried north | * The buried north object will move north, wrapping around the map, and appear at [x, 31] as a normal object of the type that was buried. | ||
* The data stored at [x, 32] will be reset to 0. | * The data stored at [x, 32] will be reset to 0. | ||
* The buried tile in the lower layer of [x, 0] will be replaced with a tile with the index equal to the data formerly occupying [x, 32]. This index is written in the infobox on the respective tile's page. | * The buried tile in the lower layer of [x, 0] will be replaced with a tile with the index equal to the data formerly occupying [x, 32]. This index is written in the infobox on the respective tile's page. | ||
| Line 49: | Line 49: | ||
The result of such behavior also includes changing the tile itself, to create items out of nowhere. If Chip's x-coordinate was 21 and the data at [8, 32] is reset, an [[exit]] will be buried at [8, 0]. Note that most data resets are limited, as they only reach up to one. The level number and Chip's coordinates are generally the most useful. | The result of such behavior also includes changing the tile itself, to create items out of nowhere. If Chip's x-coordinate was 21 and the data at [8, 32] is reset, an [[exit]] will be buried at [8, 0]. Note that most data resets are limited, as they only reach up to one. The level number and Chip's coordinates are generally the most useful. | ||
===Level 49=== | ===Level 49=== | ||
A peculiar effect occurs when performing data resetting in level 49 of a level set. Recall that 49 is the index of a clone machine. Therefore [0, 32], which stores the current level's number, will store (effectively) a clone machine. Performing the steps to reset [0, 32] will in fact not reset the level number as it does in any other level. It will instead clone the | A peculiar effect occurs when performing data resetting in level 49 of a level set. Recall that 49 is the index of a clone machine. Therefore [0, 32], which stores the current level's number, will store (effectively) a clone machine. Performing the steps to reset [0, 32] will in fact not reset the level number as it does in any other level. It will instead clone the object to [0, 31] as if there were a clone machine ''underneath'' the buried object at [0, 0]. | ||
The same effect can be achieved if the level set has exactly 49 levels. In this case, [2, 32] will hold the number 49 for any level in the level set. | The same effect can be achieved if the level set has exactly 49 levels. In this case, [2, 32] will hold the number 49 for any level in the level set. | ||