Please create an account or Login! Have fun!

Glitch

Revision as of 11:37, 1 June 2021 by Sharpeye468 (talk | contribs) (Alphabetical ordering weeeeee)
Jump to navigation Jump to search

A glitch in Chip's Challenge is a fault in the program which is caused by a coding error. The majority of glitches occur in Microsoft's version of Chip's Challenge, and in Chip's Challenge 2. The MS emulation version of Tile World deliberately reproduces most MSCC glitches in order to maintain a fair basis for scorekeeping.

MS ruleset glitches

Boosting

This glitch can cause Chip to move faster than usual after exiting a sliding tile.

Button Smash

This glitch can prevent buttons from working when blocks are flicked onto them.

Controller and Boss

This glitch can sometimes prevent monsters from exiting traps, as well as prevent clone machines from working, or causing them to clone in an unexpected direction.

Convergence

This glitch, involving blocks and teleports, can sometimes result in the creation of a second Chip in the level.

Cross-checking

This glitch sometimes causes sliding blocks to go through ice corners.

Frankenstein

This glitch sometimes causes tanks on top of clone machines to switch direction.

Mouse Panel

This glitch allows Chip to ram or flick a block without stopping to move, when using the mouse.

Non-Existence

This glitch occurs when there is no Chip on the map at the beginning of the level.

Slide Delay

This glitch causes some slipping blocks or creatures to get moved twice while others do not move at all during a tick.

Advanced MS glitches

These glitches exist in MSCC but are are not correctly emulated by Tile World. They may, however, be added to Tile World in the future.

00Floor

This acting wall looks like a North-facing bug over a white background. In Tile World, this tile is displayed like a regular wall.

Data resetting

This glitch, responsible for many insane levels, relies on clone connections beyond the map to produce unexpected results.

Knight

This glitch, related to the Controller and Boss Glitch, sometimes causes monsters to move like a knight in chess.

Multiple Tank

This glitch, responsible for many insane levels, sometimes causes sliding tanks to create other tiles.

Tank Top

This glitch sometimes causes tanks sliding onto tank buttons to turn in an unexpected direction.

Illegal MS glitches

These glitches are banned from competitive scoring, and are therefore excluded from Tile World.

Long First Second

This glitch sometimes causes a second in the in-game timer (not always the first) to be longer than usual, sometimes allowing higher scores.

Time Dilation

This glitch sometimes occurs after Chip dies using a mouse move.

Twice Step

This glitch results in unusual timing of buffered mouse moves. The legality of this glitch is still disputed, but currently only certain aspects of this glitch are legal.

MSCC crashes

These games, when triggered in Microsoft's version of Chip's Challenge, cause the game to crash. They are intentionally absent from Tile World.

Data Size

This glitch causes the game to crash due to running out of memory.

Termination

This glitch causes the game to crash when playing a set that does not have 144 or 149 levels.

Transparency

This glitch causes the game to crash when Chip steps on two transparent tiles at once (usually a monster on top of a key).

Lynx glitches

The Lynx ruleset has relatively few glitches, and many of those that exist do not have wiki pages or even names yet.

Failed Move

Official name pending. The Failed Move Glitch, often referred to informally as The Stupid Glitch, is not actually a glitch, but an exploit of the way Lynx processes movement. This term refers to a specific application in which a monster sees a direction as open, turns to face that direction, then finds that for whatever reason it is no longer able to enter the tile. The most notable cases of this are when a bug, paramecium, glider, or fireball turns around because a block just moved into a space beside it or a toggle wall changed from open to closed, whereas if the block were always there, or the toggle wall were always closed, the monster would choose a different direction. An example of this is in the public TWS for Stratagem.

Release Desynchronization

This glitch, also known as clone desynchronization due to the way it was discovered, causes some cloning streams to desynchronize over time when they would synchronize in MS.

Teleport Stacking

Official name pending. Some of this behavior is demonstrated here.

Chip's Challenge 2

While Chip's Challenge 2 is coded much more professionally than MSCC, it has its fair share of bugs and bizarre behaviors as well. Most of these behaviors do not have wiki pages yet.

Despawning and Respawning

This glitch allows entities to "disappear," remaining invisible and intangible while still occupying a physical location. These entities can reappear later, even after the level resets or changes.

Explosion Sneaking

This glitch allows movable objects within the explosion radius of a time bomb to escape unharmed if moving at the precise tick of the explosion. The Chip and Melinda variant is banned in optimization, but the monster variant remains legal.

Item Bestowal

This glitch makes it possible for monsters to pick up items when they normally should not be able to.

Monster Hooking

When an entity with a hook attempts to move away from another moving entity, the hook will attempt and fail to pull that entity. For the player, this often results in death, as their inability to move allows the other entity to collide with them.

Salmon

This glitch makes it possible to override force floors in directions that would normally be impossible. A demonstration can be found here.

Simultaneous Character Movement

By switching between playable characters at high speed in-between tiles, it can be possible to essentially move several characters at once. This glitch is banned in optimization.

Spring mining

This glitch lets Chip (or other monsters that can push) move onto a tile with a block when pushing the block, in cases where they would normally stay behind while the block moves forward. The glitch is named after the level Spring Mines, in which it can easily be triggered.