Saving, Loading & Sharing
Accounts, teams, saving the whole branch tree, opening older (V2) scenarios, public scenarios, and what is preserved.
Why you need an account
You can open the visualizer, build and play a scenario without logging in — nothing blocks a quick demo or a look around. An account is what lets you keep your work: saving, loading, your teams and the public scenario library all need one. Free accounts have every feature; they see a short ad when saving or loading.
Teams
A scenario points at two teams — your home and away team — and those are what the players wear on the pitch. Pick them from the File menu; both are saved with the scenario and come back with it when you load it again.
Teams are built on the website's Manage Teams page: names, colours, badge, squad numbers, player photos and kit textures. There are downloadable kit templates (shirt front and back, shorts front and back, socks) you can paint in any image editor and upload back to the team.
What gets saved
A scenario is saved as its whole branch tree: every branch, each with its own timeline — its length, its tracks, every movement key, and every action, graphic, attachment and visual key on them — plus the segment settings between movement keys (straight / curved, bend, arch), the scenario's name and its two teams.
| Saved with the scenario | Not saved (yours for the session only) |
|---|---|
|
The branch tree — every branch, and how they are ordered (which one is the default continuation) Each branch's timeline: length, tracks, keys, segments, arcs, attachments, visuals The two teams and the scenario name |
Your picks in the scenario tree — a loaded scenario starts again from the default branches The branch you were looking at, the playhead position, and the camera angle |
Saving
- Open the File menu and choose Save (updates the scenario you opened) or Save As… (creates a copy under a new name).
- If you are not logged in, you are asked to sign in first — your work stays on screen while you do.
- That is it. The branch tree, every branch's timeline and your teams are written in one go.
Loading
- File menu → Load scenario. Your own scenarios are listed there.
- Pick one and it opens on the pitch, ready to play, with its teams restored.
Scenarios from the older frontend (V2)
Older scenarios — everything built before the scenario tree existed — open in exactly the same way. A V2 scenario simply becomes the root branch: its phases, movement keys, curves, arches, attachments and zone windows are all there, as one timeline.
From that point it is a normal V3 scenario: split it by adding sub-branches under it, give each one its own timeline, and reorder them. Nothing you did in the past is rewritten or dropped.
Public scenarios
Public scenarios are shared by other coaches. Opening one loads a copy — it becomes your own scenario, and saving never overwrites the original. If the author's teams are not available to you, the pitch simply keeps the teams you already had.
Sharing what you built
The Capture button (bottom-right of the viewport) saves the current view as a PNG image — handy for a session plan, a group chat or a slide. On mobile it shares straight into your photos.
Read on: Undo & Redo → The Scenario Tree → Animation & Playback.