Despawning and Respawning Glitch: Difference between revisions

Latest revision as of 13:38, 10 May 2024

This page describes a mechanic specific to the Steam rerelease of Chip's Challenge (and anything that emulates it). It may not exist in any other Chip's Challenge game.

Chip's Challenge 2 has some odd internal structuring that allows objects to be removed from a level through certain glitches and show up again on another level, or on the next playthrough of the same level. This behavior as a whole is known as the Despawning and Respawning Glitch. It seems to be a way of dealing with multiple entities from the same layer being on the same tile.

Despawned stateEdit

Objects in a despawned state will be intangible and invisible to the level until they attempt to move. They will also persist across all level changes and resets while despawned.

Despawning objectsEdit

Via spring miningEdit

All methods of spring mining can cause despawning if turtles are involved or if the tile being mined onto switches to an orientation that would not allow a block to be pushed on it.

Non-block entities, curiously, only despawn when spring mining a turtle, and not spring mining any other tile:

Note that dying and despawning, as it is defined, are different. If an entity that spring mines a turtle does not have flippers, they will simply die rather than despawn.

Via failed despawnsEdit

If you do something that should cause a despawn but the despawn is interrupted by a level change or reset, any entity that was on the tile where the despawn took place will be despawned on level load.

Entities will respawn as soon as they attempt to move, which is why the glider in the above gif had to be enclosed in toggle doors in order for the despawning not to be immediately undone.

Via swapping with a despawned objectEdit

If a despawned object respawns on a tile that already has an object on it, the despawned object "swaps places" with the present object, causing it to despawn.

Respawning objectsEdit

Despawned objects will spawn in the same spot they were before once the next level begins. They will only become tangible and visible once they attempt to move.

Objects can respawn on top of other objects. Suppose you were to reset an additional time after the glider-in-toggle-doors test:

Because multiple despawned entities can have the same position, the above process can be repeated many times to spawn many players:

However, if there is not already more than one player to start with, the extra player will be unusable since player switching is not enabled in levels with only one player. (Also note that character switching is disabled once only one player needs to exit.) Sometimes, upon a level change, despawned player entities will be unable to move and thus unable to respawn. Level resets seem to work fine.

Unsafe despawningEdit

When NOT gates are introduced into a wired blue teleport system, they cause the resulting teleportation to be one-way. If the NOT gate leads to a wire that terminates without reaching a teleport, any object that enters the teleport will despawn. However, the game will then crash once you restart or load a new level and attempt to start the level, presumably because the despawned object now occupies an invalid position.

The gif above shows this happening with a player, but this crash will happen regardless of the object or objects that teleport.

If the currently selected player gets in this state, or you switch to a player that is in this state, moving will do nothing and you will be unable to drop/shuffle items or switch characters. Furthermore, teleports that have caused an unsafe despawn will act as though they are permanently partial posted, and will not allow anything to enter.

External linksEdit

Original video on the Waterbirth Glitch
Variant of Block Deletion involving swivels but no sliding

This article is a stub. You can help Chip's Challenge Wiki by expanding it.

@@ Line 1: / Line 1: @@
-The '''Waterbortion Glitch''' is a glitch in [[Chip's Challenge 2]]. It results in entities starting on a particular [[turtle]] disappearing if the level is reset while something is [[Spring Mining|spring mined]] off that turtle.
+{{Steamonly}}
-It can be seen in this example gif, wherein Chip spring mines a [[block]] off a turtle and resets the level after dying from doing so. The eye is only included for visibility.
+<!-- "vanishing" was a temporary name for "despawning", and "generating" a temporary name for "respawning". you might see some abandoned references here and there in the filenames.-->
+[[Chip's Challenge 2]] has some odd internal structuring that allows objects to be removed from a level through certain glitches and show up again on another level, or on the next playthrough of the same level. This behavior as a whole is known as the '''Despawning and Respawning Glitch'''. It seems to be a way of dealing with multiple entities from the same layer being on the same tile.
-[[File:Waterb.gif|frameless]]
+== Despawned state ==
+Objects in a despawned state will be intangible and invisible to the level until they attempt to move. They will also persist across ''all'' level changes and resets while despawned.
-See also this gif, which demonstrates that the object doing the pushing does not need to be the player as long as you restart at the right time:
+== Despawning objects ==
+=== Via spring mining ===
-[[File:Waterb2.gif|frameless]]
+All methods of [[spring mining]] can cause despawning if [[turtle]]s are involved or if the tile being mined onto switches to an orientation that would not allow a block to be pushed on it.
-This also works when the entity that is spring mined off the turtle does not match the entity at the start of the level:
+[[File:SpringMineVanish1.gif]]
-[[File:Waterb3.gif|frameless]]
+[[File:SpringMineVanish2.gif]]
+Non-block entities, curiously, only despawn when spring mining a turtle, and not spring mining any other tile:
+[[File:SpringMineVanish3.gif]]
+Note that dying and despawning, as it is defined, are different. If an entity that spring mines a turtle does not have flippers, they will simply die rather than despawn.
+=== Via failed despawns ===
+If you do something that should cause a despawn but the despawn is interrupted by a level change or reset, any entity that was on the tile where the despawn took place will be despawned on level load.
+[[File:PostresetVanish1.gif]]
+[[File:PostresetVanish2.gif]]
+Entities will respawn as soon as they attempt to move, which is why the glider in the above gif had to be enclosed in toggle doors in order for the despawning not to be immediately undone.
+=== Via swapping with a despawned object ===
+If a despawned object respawns on a tile that already has an object on it, the despawned object "swaps places" with the present object, causing it to despawn.
+[[File:GenerateVanishSwap.gif]]
+== Respawning objects ==
+Despawned objects will spawn in the same spot they were before once the next level begins. They will only become tangible and visible once they attempt to move.
+[[File:GenerationAbuse.gif]]
+Objects can respawn on top of other objects. Suppose you were to reset an additional time after the glider-in-toggle-doors test:
+[[File:DuplicateGliders.gif]]
+[[File:Waterbirth.gif]]
+Because multiple despawned entities can have the same position, the above process can be repeated many times to spawn many players:
+[[File:RedundantWaterbirth.gif]]
+However, if there is not already more than one player to start with, the extra player will be unusable since player switching is not enabled in levels with only one player. (Also note that character switching is disabled once only one player needs to exit.)
+Sometimes, upon a level change, despawned player entities will be unable to move and thus unable to respawn. Level resets seem to work fine.
+== Unsafe despawning ==
+<!-- some of this may be irrelevant, consider moving to another page? -->
+When [[NOT gate]]s are introduced into a [[wire]]d [[blue teleport]] system, they cause the resulting teleportation to be one-way. If the NOT gate leads to a wire that terminates without reaching a teleport, any object that enters the teleport will despawn. However, the game will then crash once you restart or load a new level and attempt to start the level, presumably because the despawned object now occupies an invalid position.
+[[File:NOTGateVanishCrash.gif]]
+The gif above shows this happening with a player, but this crash will happen regardless of the object or objects that teleport.
+If the currently selected player gets in this state, or you switch to a player that is in this state, moving will do nothing and you will be unable to drop/shuffle items or switch characters. Furthermore, teleports that have caused an unsafe despawn will act as though they are permanently [[partial posting|partial post]]ed, and will not allow anything to enter.
+== External links ==
+<!-- Temporary - these 2 videos were removed from the Glitch article after some cleanup, but maybe they're useful for this page? -->
+* [https://www.youtube.com/watch?v=T15oEC9Mocg Original video] on the Waterbirth Glitch
+* [https://www.youtube.com/watch?v=Wunm7N-j-NQ Variant of Block Deletion] involving swivels but no sliding
 {{stub}}
+[[Category:Glitches]]