trusted-editors
994
edits
Move order: Difference between revisions
added note on move boundary
m ((meant to do this last edit)) |
(added note on move boundary) |
||
| Line 4: | Line 4: | ||
===MS=== | ===MS=== | ||
[[Chip]] and enemies make their moves one after the other, not at the same time. The below list may not be completely accurate, but should serve as a solid guideline for when things act in relation to each other. | [[Chip]] and enemies make their moves one after the other, not at the same time. The below list may not be completely accurate, but should serve as a solid guideline for when things act in relation to each other. Note that the points in time that one might intuitively consider to be move boundaries—the relatively large periods of time during which little to nothing happens—are not what [[Microsoft's version of Chip's Challenge|MSCC]] considers internally to be the move boundaries, which are defined to be the points at which the timer ticks down. | ||
# The [[sliplist]] executes first under normal conditions, before anything else. | # The [[sliplist]] executes first under normal conditions, before anything else. | ||
# [[Chip]]'s voluntary move processes next, if one is made at any point in the first half of the move window, followed by any involuntary (sliding) moves at the half-move boundary. | # [[Chip]]'s voluntary move processes next, if one is made at any point in the first half of the move window, followed by any involuntary (sliding) moves at the half-move boundary. | ||
# The sliplist then executes a second time. | # The sliplist then executes a second time. | ||
# Chip can then make a voluntary move if he has either not yet moved in this move, or has completed an involuntary move. This behavior is why rapid 10 [[m/s]] boosting sequences can exist in the MS ruleset. | # Chip can then make a voluntary move if he has either not yet moved in this move, or has completed an involuntary move. This behavior is why rapid 10 [[m/s]] boosting sequences can exist in the MS ruleset. MSCC initiates mouse clicks here, while [[Tile World]] resolves mouse clicks at this time under all circumstances, as of 1.3.2 and 2.2. | ||
# Chip's involuntary move is then executed, if necessary, just before the following move. | # Chip's involuntary move is then executed, if necessary, just before the following move. | ||
# [[Monster]] voluntary moves are processed last, at the very end of each move. This is why monsters that stop sliding will sometimes seem to move again too soon- the sliplist executes, dropping the monster onto acting floor, and when the move ends the monster will immediately move, if able. | # [[Monster]] voluntary moves are processed last, at the very end of each move. This is why monsters that stop sliding will sometimes seem to move again too soon- the sliplist executes, dropping the monster onto acting floor, and when the move ends the monster will immediately move, if able. | ||
| Line 16: | Line 16: | ||
The fact that monsters and Chip move on separate turns is what causes Chip to be unable to pass through a space between two monsters that are moving the other way through that tile. | The fact that monsters and Chip move on separate turns is what causes Chip to be unable to pass through a space between two monsters that are moving the other way through that tile. | ||
===Lynx | ===Lynx=== | ||
===Steam=== | |||
{{stub}} | {{stub}} | ||
[[Category:Terminology]] | [[Category:Terminology]] | ||
[[Category:Mechanics]] | [[Category:Mechanics]] | ||