Please create an account or Login! Have fun!
In-game second: Difference between revisions
m (added Amiga video as reference (thanks moon)) |
m (moved an explanation to its own "Notes" section) |
||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
An '''in-game second''' is the amount of time between two consecutive decrements of the [[time limit|timer]]—or, more generally, any other period of time equal in length | An '''in-game second''' is the amount of time between two consecutive decrements of the [[time limit|timer]]—or, more generally, any other period of time equal in length.<ref group=note>Similar to how "day" can mean "the time between midnight and 11:59pm" or "a period of 24 hours".</ref> This unit of time is intended to emulate 1 real second. In [[Lynx ruleset|Lynx]] and [[Steam ruleset|Steam]], 1 in-game second is in fact 1 real second; in [[Microsoft's version of Chip's Challenge|MSCC]], however, it depends on the machine. On most of the more modern 32-bit machines, MSCC consistently runs at about 1.17 real seconds per in-game second. [[Tile World]]'s emulation of the [[MS ruleset]] attempts to emulate this lag at 1.1 real seconds per in-game second. | ||
== Common subdivisions == | == Common subdivisions == | ||
| Line 10: | Line 10: | ||
A '''half move''' (sometimes hyphenated) is one half of a move, or 1/10 of an in-game second. When most objects slide, they take half a move to move between tiles. | A '''half move''' (sometimes hyphenated) is one half of a move, or 1/10 of an in-game second. When most objects slide, they take half a move to move between tiles. | ||
In MS, the graphics update every half move; i.e., MS runs at 10 "fps". <!--Apparently not accurate but idk how to fix.--> The first and second halves of a move also have different properties in MS: see [[move order]]. | In MS, the graphics update every half move; i.e., MS runs at 10 "fps". <!--Apparently not accurate but idk how to fix.--> Because of this, in the context of MS, the term ''tick'' occasionally is used to mean 'half move'. | ||
The first and second halves of a move also have different properties in MS: see [[move order]]. | |||
=== Tick === | === Tick === | ||
| Line 17: | Line 19: | ||
In Lynx, the graphics update every tick; i.e., Lynx runs at 20 fps. As such, in the context of Lynx, the term ''frame'' is sometimes used interchangeably with 'tick'. | In Lynx, the graphics update every tick; i.e., Lynx runs at 20 fps. As such, in the context of Lynx, the term ''frame'' is sometimes used interchangeably with 'tick'. | ||
Ticks actually have meaning in MS as well. <!--I don't know how ticks work in MS, help.--> | Ticks in this sense actually have meaning in MS as well. <!--I don't know how ticks work in MS, help.--> | ||
=== Frame === | === Frame === | ||
| Line 23: | Line 25: | ||
Every 3rd frame from the beginning of a level is a '''movement frame'''. Even though voluntary moves can only start on movement frames, i.e. once per tick, movement is actually processed every frame, not just their animations, as can be seen when objects slide. <!--I'd mention the whole misalignment thing, but i already have that on 2 other articles. Maybe it should be its own article?--> <!--Also not clear which frames (mod 3) are movement frames, or if movement is processed between frames.--> | Every 3rd frame from the beginning of a level is a '''movement frame'''. Even though voluntary moves can only start on movement frames, i.e. once per tick, movement is actually processed every frame, not just their animations, as can be seen when objects slide. <!--I'd mention the whole misalignment thing, but i already have that on 2 other articles. Maybe it should be its own article?--> <!--Also not clear which frames (mod 3) are movement frames, or if movement is processed between frames.--> | ||
== Notes == | |||
<references group=note/> | |||
== References == | == References == | ||
| Line 29: | Line 34: | ||
== See also == | == See also == | ||
* [[Time limit]] | * [[Time limit]] | ||
* [[M/s]] - "move" in this | * [[M/s]] - "move" in this article, when not referring to the action itself, is a unit of ''distance'', following the [https://en.wikipedia.org/wiki/Taxicab_geometry taxicab metric], equal to 1 square on the grid. | ||
* [[Move order]] | * [[Move order]] | ||
** [[Spring step]] | ** [[Spring step]] | ||
Revision as of 00:23, 5 April 2020
An in-game second is the amount of time between two consecutive decrements of the timer—or, more generally, any other period of time equal in length.[note 1] This unit of time is intended to emulate 1 real second. In Lynx and Steam, 1 in-game second is in fact 1 real second; in MSCC, however, it depends on the machine. On most of the more modern 32-bit machines, MSCC consistently runs at about 1.17 real seconds per in-game second. Tile World's emulation of the MS ruleset attempts to emulate this lag at 1.1 real seconds per in-game second.
Common subdivisions
Move
A move, as a unit of time, is the amount of time most (movable) objects take to move 1 square on the grid in normal circumstances (no sliding, spring steps, teleporting, etc.). In each of the main rulesets (MS, Lynx, and Steam), each in-game second is evenly split into 5 moves. There are, however, some versions of Chip's Challenge in which this is not the case: for example, in the Amiga and Atari ST ports, there are 6 moves in each in-game second.[1]
For the remainder of this article, discussion will be limited to the main rulesets.
Half move
A half move (sometimes hyphenated) is one half of a move, or 1/10 of an in-game second. When most objects slide, they take half a move to move between tiles.
In MS, the graphics update every half move; i.e., MS runs at 10 "fps". Because of this, in the context of MS, the term tick occasionally is used to mean 'half move'.
The first and second halves of a move also have different properties in MS: see move order.
Tick
A tick is 1/4 of a move, or 1/20 of an in-game second. Movement in Lynx and Steam is processed every tick. Step parities aside, in Lynx and Steam, all ticks are equivalent: there is no "first tick" versus "second tick" like there is in MS, and a move from one tile to the next can start on any tick and will always take 4 ticks to complete (2 if sliding).
In Lynx, the graphics update every tick; i.e., Lynx runs at 20 fps. As such, in the context of Lynx, the term frame is sometimes used interchangeably with 'tick'.
Ticks in this sense actually have meaning in MS as well.
Frame
A frame is 1/3 of a tick, or 1/60 of an in-game second. This use of the term only has meaning in Steam, which runs at 60 fps.
Every 3rd frame from the beginning of a level is a movement frame. Even though voluntary moves can only start on movement frames, i.e. once per tick, movement is actually processed every frame, not just their animations, as can be seen when objects slide.
Notes
- ↑ Similar to how "day" can mean "the time between midnight and 11:59pm" or "a period of 24 hours".
References
- ↑ Example video of Amiga gameplay: https://www.youtube.com/watch?v=dP2Vjo7rW0E
See also
- Time limit
- M/s - "move" in this article, when not referring to the action itself, is a unit of distance, following the taxicab metric, equal to 1 square on the grid.
- Move order
- Release desynchronization
