Skip to Content

Limits of time travel

Time travel in the tutorial is record and replay of a deterministic simulation. It is not a snapshot of a live editor. Knowing what is recorded tells you what a replay can and cannot show.

What is recorded

RecordedNot recorded
The seed.Rendered frames. The recording shows the simulation’s shapes, not what the engine drew.
The ticks on which a flap was used.Video.
The state after each step: input, game state, height, velocity, score and pillars.Anything outside the simulation’s state.
The engine and project version.A live editor world.

What a fork point is

A fork point is a tick of a recorded run. It is not a live editor state. A fork re-simulates the run from tick 0 without a window, so it cannot rewind an editor you have open.

Every tick of a recorded run is a fork point.

When a replay is exact

A replay with no input changed writes the same frames.jsonl as the run it came from, byte for byte. The tutorial’s FloppyBird.Replay.ReplayReproducesRecordedFrames test checks this.

Each run’s manifest.json records the seed and the engine and project version it was made with.

Other limits

  • A run that is still being played is converted when it ends. It is not streamed into the viewer.
  • Tests do not record. The automation tests’ worlds never begin play, so they write no runs unless a test asks for recording.
  • A fork needs a built project. It also takes as long as starting an editor without a window.
  • These pages describe the Floppy Bird tutorial. Another game needs its own recorder, its own replay command and its own agent/trainer.json.

Next steps

Last updated on