Record a run
The tutorial records every run you play, from the first step to GameOver. You do not turn anything on. Each run becomes a folder that the Lou view lists.
Before you start
- Create the tutorial project. See Your first game.
- Make sure an engine is found. See Engine setup.
Record
Build
In the Unreal view, choose Build.
Open the editor
Choose Open editor.
Play until GameOver
In Unreal Editor, press Play and play until GameOver. Space or a click flaps.
Open Lou
In GameGen, choose Lou (Decision Model) in the sidebar. The Lou view opens on the Review tab with your run in the list.
Before the first run exists, the Lou view reads No runs recorded yet and repeats these steps. It checks again every few seconds and opens by itself when the first run is saved.
Where runs are saved
Runs are saved in the project, under Saved/Lou/runs/. Each played run has a folder named play-, then the UTC date and time, then a counter.
| File | Contents |
|---|---|
manifest.json | The seed, and the engine and project version. A forked run also names its parent. |
frames.jsonl | Frame 0, then one line per step with the input (flap or wait) and the state after it. |
summary.json | How the run ended, the final tick, the score and the ticks on which a flap was used. Written when the run ends. |
run.rrd | The recording for the viewer, once you build it. |
Saved/ is ignored by git, so runs are not committed.
A run whose editor was closed before GameOver has no summary. It still replays from its frames.
What a run is
A run is its seed plus the ticks on which a flap was used. Tick N is the Nth fixed step, and each step is 1/60 of a second. Nothing else is needed to play the run again.