Please create an account or Login! Have fun!

Controller and Boss Glitch: Difference between revisions

Jump to navigation Jump to search
m
→‎Cause: from pieguy on the topic in the CCBBC Discord https://discordapp.com/channels/343036755999457281/350042613254062091/599384136653864977
m (Text replacement - "CC1" to "CC1")
m (→‎Cause: from pieguy on the topic in the CCBBC Discord https://discordapp.com/channels/343036755999457281/350042613254062091/599384136653864977)
(2 intermediate revisions by one other user not shown)
Line 2: Line 2:


== Cause ==
== Cause ==
The root cause of the glitch is uninitialized variables in the game{{fact}}. That is, some part of the program attempts to read some place in memory without ever writing to it first (or the programmer forgets to write to it first), causing the read data to be something unrelated that was coincidentally written in that place earlier by a different, unrelated part of the program.
The root cause of the glitch is uninitialized variables in the game. That is, some part of the program attempts to read some place in memory without ever writing to it first (or the programmer forgets to write to it first), causing the read data to be something unrelated that was coincidentally written in that place earlier by a different, unrelated part of the program.


== Traps ==
== Traps ==
Line 53: Line 53:
Unusual things happen to bosses or controllers which cannot legally move. A monster stuck in a trap will always work in that direction even when physically trapped (this is frequently used to avert glitch issues); however, when such a monster is released, or any other time one is blocked by [[acting wall]]s, two categories of exceptions begin to arise.
Unusual things happen to bosses or controllers which cannot legally move. A monster stuck in a trap will always work in that direction even when physically trapped (this is frequently used to avert glitch issues); however, when such a monster is released, or any other time one is blocked by [[acting wall]]s, two categories of exceptions begin to arise.


* If left untrapped but immobile: the bug, paramecium, fireball, glider and pink ball will control or boss in the ''opposite'' direction they are facing; a teeth will work in the direction it is facing, a blob will work in a random direction, a walker will exclude its initial direction from the four, and most strangely a tank will not work ''at all'' as long as it does not move, rendering the trap or cloner dead. This mechanic is the cause of one of the rare C/B Glitch issues in [[CCLP3]].
* If left untrapped but immobile: the bug, paramecium, fireball, glider and pink ball will control or boss in the ''opposite'' direction they are facing; a teeth will work in the direction it is facing, a blob will work in a random direction, a walker will exclude its initial direction from the four, and most strangely a tank will not work ''at all'' as long as it does not move, rendering the trap or cloner dead. This mechanic is the cause of one of the rare C/B Glitch issues in [[Chip's Challenge Level Pack 3|CCLP3]].


* If trapped, but released and now immobile: the bug, paramecium, fireball, glider, pink ball ''and'' walker will control or boss in their present direction, while the teeth, blob and tank still function the same way as before. Note that monsters that apply to the original rules of the glitch must themselves be released by their own controllers to function in this manner; if the trap is dead, the monster will still face in its current direction.
* If trapped, but released and now immobile: the bug, paramecium, fireball, glider, pink ball ''and'' walker will control or boss in their present direction, while the teeth, blob and tank still function the same way as before. Note that monsters that apply to the original rules of the glitch must themselves be released by their own controllers to function in this manner; if the trap is dead, the monster will still face in its current direction.
Line 80: Line 80:
* [[Trust Me]]: The boss for the bug clone machines, but in particular the one just to the right of the exit, is a paramecium in the lower left corner, which doesn't move west for a sum total of [31] after the red button is pressed in the [[busted]] solution.
* [[Trust Me]]: The boss for the bug clone machines, but in particular the one just to the right of the exit, is a paramecium in the lower left corner, which doesn't move west for a sum total of [31] after the red button is pressed in the [[busted]] solution.


=== '''[[CCLP2]]''' ===
=== '''[[Chip's Challenge Level Pack 2|CCLP2]]''' ===
Occurrences of the C/B Glitch in CCLP2 are far more rare, since its mechanics had been well-documented by the time of release (2002); only two levels include it.
Occurrences of the C/B Glitch in CCLP2 are far more rare, since its mechanics had been well-documented by the time of release (2002); only two levels include it.


Line 87: Line 87:
* The second level that can use the glitch is [[Dangers of Fire and Beasts]], although it saves only one second and requires luck. Chip can gain an extra [4] by cloning two teeth instead of avoiding two red buttons and save enough of it to add an additional second to Chip's score, but this requires the [[walker]] controller to send one of the teeth south off a trap and into water.
* The second level that can use the glitch is [[Dangers of Fire and Beasts]], although it saves only one second and requires luck. Chip can gain an extra [4] by cloning two teeth instead of avoiding two red buttons and save enough of it to add an additional second to Chip's score, but this requires the [[walker]] controller to send one of the teeth south off a trap and into water.


=== '''[[CCLP3]]''' ===
=== '''[[Chip's Challenge Level Pack 3|CCLP3]]''' ===
Accidental cases of the glitch were all but eradicated by CCLP3's release in late 2010, but it is used intentionally as a level element in one case. One new type of the glitch was officially documented in June 2011.
Accidental cases of the glitch were all but eradicated by CCLP3's release in late 2010, but it is used intentionally as a level element in one case. One new type of the glitch was officially documented in June 2011.


trusted-editors
539

edits

Navigation menu