Skip to content
Void Monster Docs

Type to search guides and API reference.

    Splash/User guide

    Splash 1.2.0

    Public 1.2.0

    Splash 1.2.0 includes the revised editor and playback fixes. For an older installation, use the 1.1.0 guide.

    The editor helps you build an interactive handout from artwork, text and objects. Start from scratch or place an existing prefab, arrange the objects, then test the handout’s states and values before showing it to players.

    Splash pages use Foundry’s journal export and import. Right-click their journal entry in the Journal sidebar and choose Export Data. To load that JSON into another journal, right-click the destination entry and choose Import Data. Import replaces the destination journal’s data, so create a new entry when you want to keep both copies.

    The imported handouts can open alongside their originals as separate windows.

    Players with Observer access can open a fullscreen Splash locally or open a handout. Launching one for another player, editing it and configuring triggers still require Owner access; a global launch requires a GM.

    Binding a trigger grants read access to that Splash page. It leaves the parent journal and its other pages unchanged. Existing higher access and explicit page restrictions stay in place. If a particular player still cannot open it, check that page’s Foundry ownership settings.

    When the GM clicks an authored Close button in the current global Splash, it closes for everyone and removes the live controls. It stays closed after reload. A player’s Close button dismisses only their own view; the global launch remains active. Closing a journal handout or exiting preview affects only that window.

    Choose Synced (shared state) in the splash’s Mode setting when players should share answers and progress. An active GM must be connected to save those shared changes. Built-in Increment actions count each accepted click, including clicks from different players at the same time; Set actions can reset the value again.