The Commands card appears on every other tab in Consequence and provides quick access to essential project operations that interact with your local game project.

• These commands communicate with the Consequence Client running on your local network or development machine.
• Ensure the Consequence Client is online and connected to your project to enable these commands.
• If the Consequence Client is busy or offline, you will receive an error message.

Available Commands

Submit to Source Control

Submits the latest project data (events, lines, rules, characters, strings) to your Perforce depot via the Consequence Client. This is the primary way to push your writing into your game project.

• Learn more at Submitting to your Project.
• The Source Control submission process always syncs facts and strings as part of the operation. It does not sync audio.

Sync Facts

Synchronizes gameplay tags (facts) from your game project back into Consequence, ensuring your trigger tags and facts are up-to-date.

Sync Strings

Synchronizes UI strings from your game project back into Consequence. All strings are exported from Consequence to a .json file on your project's Perforce, and the latest strings added to the same file from the Consequence Client are pulled into Consequence at the same time.

In this way, it is possible for your writing and design teams to work on strings in both the engine and in Consequence, although for ease of use and avoiding conflicts, we recommend that for each String Table file or group of strings, you decide where you wish to primarily edit your strings.

Sync Audio

Synchronizes audio recording statuses from your game project, updating line recording statuses based on available audio files. Requires audio user permissions.