trusted-editors
994
edits
Slide delay: Difference between revisions
m
no edit summary
m (link) |
mNo edit summary |
||
| Line 1: | Line 1: | ||
'''Slide delay''' is a | '''Slide delay''' is a [[glitch]] that exists only in the MS version of [[Chip's Challenge]], and was programmed into [[Tile World]], that makes [[monster]]s and [[block]]s lag when sliding, and it can greatly alter the outcome of a level. It pertains to [[monster]]s and [[block]]s that enter and leave [[force floor]]s, [[ice]], and [[teleport]]s. | ||
== The sliplist == | == The sliplist == | ||
The ''sliplist'' is a list of moving objects, blocks or monsters, that are currently sliding on force floors, ice, or teleports. Chip will never be on the sliplist, is never affected by slide delay, and, importantly, always moves before sliding blocks. Each row in the sliplist contains two elements: the object, and the coordinates of the destination square on the Chip's Challenge [[grid]]. | The ''sliplist'' is a list of moving objects, blocks or monsters, that are currently sliding on a [[sliding tile]] (force floors, ice, or teleports). Chip will never be on the sliplist, is never affected by slide delay, and, importantly, always moves before sliding blocks. Each row in the sliplist contains two elements: the object, and the coordinates of the destination square on the Chip's Challenge [[grid]]. | ||
At the start of a level, the sliplist is empty, even if [[monster]]s are currently on sliding tiles; objects cannot enter the sliplist until they make a move. When a monster or block steps on any sliding tile | At the start of a level, the sliplist is empty, even if [[monster]]s are currently on sliding tiles; objects cannot enter the sliplist until they make a move. When a monster or block steps on any sliding tile, that object will be added to the end of the sliplist, and when it leaves a "slip" tile, it will be removed from the sliplist. Additionally, if a block slides directly off a sliding tile onto a [[trap]] (like in [[Torturechamber]]), it will remain on the sliplist, and when released, it will slide off the trap one further square in the same direction it was sliding in. | ||
Also notably, should only one sliding space separate Chip from a sliding block in front of him, and the block reaches the ice corner at the same time slide delay affects it, Chip will gain an extra half-move and be one space behind. Since Chip is unaffected by slide delay, he moves before the block, and [[cross-checking]] occurs. | Also notably, should only one sliding space separate Chip from a sliding block in front of him, and the block reaches the ice corner at the same time slide delay affects it, Chip will gain an extra half-move and be one space behind. Since Chip is unaffected by slide delay, he moves before the block, and [[cross-checking]] occurs. | ||
| Line 39: | Line 39: | ||
</div> | </div> | ||
In play, the above glider will not appear as moving in the MS version, but in [[Lynx ruleset|Lynx]], failed moves can be seen, so a glider in this type of prison would be shown | In play, the above glider will not appear as moving in the MS version, but in [[Lynx ruleset|Lynx]], failed moves can be seen, so a glider in this type of prison would be shown switching between left and right every [[tick]]. | ||
== | == The glitch == | ||
Every tick ([[half move]] in this context), the game accesses the sliplist and processes them in sequential order, moving each tile from its starting square to its destination square. When an object leaves the sliplist in the middle of this processing, the table will be modified (everything after that object will be shifted up one). However, the processing will ignore this and continue to process the object at the next index; as a result, an object will be skipped. This is what is known as slide delay. | Every tick ([[half move]] in this context), the game accesses the sliplist and processes them in sequential order, moving each tile from its starting square to its destination square. When an object leaves the sliplist in the middle of this processing, the table will be modified (everything after that object will be shifted up one). However, the processing will ignore this and continue to process the object at the next index; as a result, an object will be skipped. This is what is known as slide delay. | ||
| Line 127: | Line 127: | ||
== External links == | == External links == | ||
*([[David Stolp]]) [http://www.davidstolp.com/old/chips/slidedelay/index.html Dr. pieguy explains slide delay] | |||
[[Category:Glitches]] | |||
[[Category:Mechanics]] | [[Category:Mechanics]] | ||