Editing Controller and Boss Glitch
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 1: | Line 1: | ||
The '''Controller and Boss Glitch''', often shortened to ''C/B Glitch'' due to its length, is an [[MS Ruleset]]-exclusive glitch that affects the way [[teeth]], [[bug]]s, and the [[paramecium|paramecia]] behave when they attempt to exit a [[clone machine]] or [[trap]]. It is among the earliest documented glitches in [[Chip's Challenge 1|CC1]], being encountered earlier than even the [[Transparency Glitch]]. | The '''Controller and Boss Glitch''', often shortened to ''C/B Glitch'' due to its length, is an [[MS Ruleset]]-exclusive glitch that affects the way [[teeth]], [[bug]]s, and the [[paramecium|paramecia]] behave when they attempt to exit a [[clone machine]] or [[trap]]. It is among the earliest documented glitches in [[Chip's Challenge 1|CC1]], being encountered earlier than even the [[Transparency Glitch]]. | ||
== Cause == | == Cause == | ||
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. | 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. | ||
== Traps == | == Traps == |