You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 22, 2023. It is now read-only.
proepkes edited this page Feb 15, 2019
·
1 revision
There are multiple TickComponents in different contexts, each with a slightly different purpose:
GameState: This is the primary TickComponent which every other component refers to. It describes the actual Tick of the simulation (you can also say Frame-number) and gets incremented on every Tick
Input: Whenever you want to execute a command, you have to specify at which tick it should be executed on
Snapshot: A 'lookup' to find for which tick a snapshot exists (for example: if a rollback for tick 50 is requested, it will look for which ticks a snapshot exists. If a snapshot was created in tick 42, then the simulation will rollback to tick 42 and fast-forward to tick 50)
Game: There is no direct TickComponent in the game-context. However, the backup-component stores a reference to a tick. The reference indicates for which tick the backup was created (same as snapshot)