Ticks: Difference between revisions
mNo edit summary |
(Marked this version for translation) |
||
| (3 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
<languages/> |
|||
| ⚫ | |||
<translate> |
|||
<!--T:1--> |
|||
| ⚫ | |||
<!--T:2--> |
|||
'''Relevant Minecraft Wiki Articles:''' |
|||
| ⚫ | |||
| ⚫ | |||
<!--T:3--> |
|||
<br /> |
<br /> |
||
== Tickrate == |
== Tickrate == <!--T:4--> |
||
<!--T:5--> |
|||
The physics engine runs at '''20 ticks''' per second, meaning the game's physics are updated every '''50ms.''' |
The physics engine runs at '''20 ticks''' per second, meaning the game's physics are updated every '''50ms.''' |
||
<!--T:6--> |
|||
This includes the player’s position and speed, the environment, and entities. |
This includes the player’s position and speed, the environment, and entities. |
||
<!--T:7--> |
|||
In-game actions are performed at the end of each tick, regardless of the time or order in which they were called. |
In-game actions are performed at the end of each tick, regardless of the time or order in which they were called. |
||
<!--T:8--> |
|||
Due to the game working this way, inputs may take up to 50ms of delay |
Due to the game working this way, inputs may take up to 50ms of delay between the button press and their activation. |
||
| ⚫ | |||
<!--T:10--> |
|||
| ⚫ | |||
<!--T:11--> |
|||
| ⚫ | |||
However, the game has to keep a copy of the player's rotation for movement calculations, which it updates once every tick. The moment the player's rotation is copied is called the '''turn tick'''. |
|||
| ⚫ | |||
For movement calculations, the game has to keep a copy of the player's rotation, which is updated once every tick. |
|||
<!--T:12--> |
|||
From the player's perspective, there is no way to control when the turn tick happens. This has a severe impact on turn-based jumps, which become partially luck-based as a result: given the same (smooth) turning sequence, the player's resulting movement could be quite different. |
|||
The term '''turn tick''' refers to the manifestation of tickrate delay in mouse movement. |
|||
<!--T:13--> |
|||
Suppose you turn 45° smoothly over the course of 50ms. There is no way to predict what value will be kept in memory, as it could have been sampled at any time during the turn. This phenomenon is especially troublesome for jumps that require precise mouse movement, as they can be impossible to do consistently due to this problem. |
|||
One solution is to turn instantly every 50ms to land precisely on the wanted angle. This is feasible for simple turn strats such as [[Special:MyLanguage/45 Strafe|45° Strafes]], but not for more complex strats that would require smooth turning. |
|||
</translate> |
|||
Latest revision as of 14:04, 23 August 2021
Ticks are the standard unit of time in Minecraft, with one tick being equal to 50 milliseconds.
Tickrate
The physics engine runs at 20 ticks per second, meaning the game's physics are updated every 50ms.
This includes the player’s position and speed, the environment, and entities.
In-game actions are performed at the end of each tick, regardless of the time or order in which they were called.
Due to the game working this way, inputs may take up to 50ms of delay between the button press and their activation.
Turn Tick
Mouse Movement is not inherently tied to tickrate, but rather the framerate.
However, the game has to keep a copy of the player's rotation for movement calculations, which it updates once every tick. The moment the player's rotation is copied is called the turn tick.
From the player's perspective, there is no way to control when the turn tick happens. This has a severe impact on turn-based jumps, which become partially luck-based as a result: given the same (smooth) turning sequence, the player's resulting movement could be quite different.
One solution is to turn instantly every 50ms to land precisely on the wanted angle. This is feasible for simple turn strats such as 45° Strafes, but not for more complex strats that would require smooth turning.