trusted-editors
994
edits
Slide delay: Difference between revisions
m
link
Indyindeed (talk | contribs) |
m (link) |
||
| Line 2: | Line 2: | ||
== 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 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]]. | ||
| Line 12: | Line 11: | ||
== Examples == | == Examples == | ||
As this [[glider]] begins on an ice tile, it does not count and it will not be added to the sliplist. | As this [[glider]] begins on an ice tile, it does not count and it will not be added to the sliplist. | ||
| Line 44: | Line 42: | ||
== Slide delay == | == 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. | |||
Every tick | |||
A more concrete example is shown below. | A more concrete example is shown below. | ||