Undo & Redo
What you can take back — scene edits, keys and whole branches — and what undo does to the branch you are viewing.
Undo and Redo
Every change you make to a scene can be taken back. The buttons are in the viewport (bottom-left), and the keyboard shortcuts are Ctrl/Cmd+Z to undo and Ctrl/Cmd+Shift+Z (or Ctrl+Y) to redo. The last 20 steps are kept.
What you can take back
- Anything you do on the pitch — placing, moving or removing players, the ball, cones, targets and zones.
- Anything you key — movement keys, actions, graphics, attachments, zone visual windows, and the segment settings (curve, bend, arch) between movement keys.
- A branch's timeline length — including ✂ Clip time, which trims the branch to its last key.
- Structure, too — adding a sub-branch, removing a branch, renaming one, and changing its priority order (the number box and ▲ ▼). If you split a branch by mistake, undo puts the tree back exactly as it was, branch and all.
One gesture, one step
A whole gesture counts as a single step. Dragging a player across the pitch, or sliding a value, is undone in one press — you go back to how things were before the drag started, never to a half-way position.
Where undo puts you
Undo restores the scene, and it also opens the branch the change belongs to. If you edited a key in one branch, then walked to another branch and undid it, the app switches you back to the branch you edited — so you always see what changed. The other branches are not touched: each one keeps its own timeline.
Redo
Anything you undo can be redone with Ctrl/Cmd+Shift+Z — as long as you have not made a new change in between, which starts a fresh history.
What is not undoable
- Loading a scenario, or starting a new one — that is a fresh start, and the history begins again from there.
- Looking around: selecting a branch, playing, the camera, the 2D/3D toggle. Nothing about navigating is an edit.
- Your picks in the tree (see the tip above).
Read on: Saving, Loading & Sharing → The Scenario Tree → Working in a Branch's Timeline.