Local Saves

Sometimes, you can’t fit a whole game into one session. Luckily in TTP you can save your table state at any time. Simply choose “Save State” from the top menu, name your game, and click “Save.” This will create a Local save.

To resume such a game, click “Local Saves” on the left side of the “Select Game” dialogue. All the games you’ve saved will appear on the righthand side. You can also simply begin a game with the appropriate package, and choose “Load State” from the top menu. You’ll see all your Local Saves in the list, but only ones for your current package will be available.

On beta clients, local saves are conveniently saved with their associated package. When you click on a package in the “Select Game” dialogue, if you have any local saves, you’ll see “New Game” and “Load Game” tabs on the right side of the dialogue.

Autosaves

Sometimes, things go wrong. That’s why Tabletop Playground saves your table state every few seconds, just in case. You can resume from an Autosave by choosing “Autosave” from the Select Game menu and choosing the appropriate timestamp from the list on the right.

As with local saves, you can also load an Autosave while on the table by choosing “Load State” from the top menu; as with local saves, all Autosaves will be shown, but only ones using your current package will be available.

Saving and Loading in Editor

When saving a state in Editor, you’ll see two options on the left-hand side: Local Saves and the name of your package.

Creating a save with the package name selected will create a Starting State for that package. These will be the states that show up in the Select Game dialogue when users are creating a new game. They are considered part of the package, and will be uploaded to mod.io if and when you publish the package.

Local Saves meanwhile are for your personal use; they won’t be uploaded should you publish your package to mod.io.

When you choose a package in editor, you’ll see tabs for Start States, Local Saves, and Autosaves on the righthand side. “Start States” and “Local Saves” work the same as “New Game” and “Load Game” in the Start Game flow.

What Is and Isn’t Saved

Table state saves include, among other things:

• The position of all objects on the table
• Any changes to objects on the table via Properties
• Any Session Options you may have in place, including:
  • Grid visibility
  • Team settings
  • Phase settings and current turn.
  • Edits to Player Slots.
  • Any Global UI you may have added.

But they do not include changes to Object Templates or to Scripts; those are saved at the package level. This means:

• If you’re using a package from mod.io, any updates the creator makes will instantly and retroactively be applied to all local saves you may have of it.
• If you’re working on your own package, any changes you make to an object template will automatically affect all saves of it. You don’t have to save the state for them to “stick,” but you also can’t roll them back by loading a previous save state.