3
edits
Cloning: Difference between revisions
Jump to navigation
Jump to search
m
link fix
ExpergeTech (talk | contribs) ((sort of) merged Premature Cloning into this page aka I just copied and pasted. The old page can be deleted) |
Gladiatrix (talk | contribs) m (link fix) |
||
| Line 51: | Line 51: | ||
*[[Blue Coin|Blue coin]]s by reaching a loading zone before the [[Blue Coin Switch]] runs out | *[[Blue Coin|Blue coin]]s by reaching a loading zone before the [[Blue Coin Switch]] runs out | ||
<!--Finish this list--> | <!--Finish this list--> | ||
Because cloned objects never unload, they gradually fill up the available [[object slots]] and continue to be rendered on screen. This can cause lag, [[game corruption]], and eventually a [[game freeze]] when the object slots run out. | Because cloned objects never unload, they gradually fill up the available [[object slots]] and continue to be rendered on screen. This can cause lag, [[game corruption]], and eventually a [[Crash|game freeze]] when the object slots run out. | ||
=== Infinite shell === | === Infinite shell === | ||
When Mario rides on a [[Koopa Shell]] or [[Shiny Shell]], although the latter is impossible to clone, the shell object stays spawned until he runs into a [[wall]] or presses Z, which causes the shell to break. At this point, Mario sets a flag on the shell, and when the shell next updates, it unloads itself. Because a cloned shell does not update, it does not unload, allowing Mario to repeatedly ride and break a shell after cloning it. | When Mario rides on a [[Koopa Shell]] or [[Shiny Shell]], although the latter is impossible to clone, the shell object stays spawned until he runs into a [[wall]] or presses Z, which causes the shell to break. At this point, Mario sets a flag on the shell, and when the shell next updates, it unloads itself. Because a cloned shell does not update, it does not unload, allowing Mario to repeatedly ride and break a shell after cloning it. | ||