Build your own pack

Before you start

• Create and test your automations first (“Your first automation” and “Test safely” guides).
• Save time: you can also start from a ready-to-tune template, with Start from a template then Use this template, at the start of the creation.
• You need the permission to manage automations on the organization.

Create the pack in three steps

1. In Packs, click Create a pack. The creation steps are Automations, Parameters and Presentation.
2. Automations: tick the ones to bundle, then Continue. They are a starting point.
3. Parameters: a parameter is a setting that the person installing the pack fills in. Give it a Display name, pick its Type, then Add the parameter.
4. Set its Default value, and if needed its bounds (Minimum, Maximum) or its Options.
5. Click Use in… to place the parameter in an automation: pick the Automation, the Step, the Setting, then Apply.
6. Presentation: Title, Summary, Description and Version. The description supports paragraphs, lists with “-” and bold.
7. Click Save. “Pack saved.”

What a pack can hold on top

• Shared memories: a memory owned by The pack is common to all the pack's automations. Its content is not exported with the pack.
• Views: screens tied to its automations. On installation, the Add its views to the menu box places them in the Views menu, and Uninstall removes them.
• Test scenarios: see just below.

On the pack's page, a diagram shows its automations and their links. Click a card to see its detail. The Settings, Presentation and Details tabs are on the right.

Test scenarios

Under the diagram, the Scenarios section replays a made-up match against all of the pack's automations, like the editor's simulator (see “Test safely”).

1. Save the pack: scenarios run on the saved version.
2. Click Add a scenario, name it, add players, events and expectations.
3. Click Run, or Run all to replay them all.

A pack accepts at most 10 scenarios. A scenario without expectations shows what happens but never blocks publishing. Scenarios travel with the pack: official examples, export and import.

Share by file

The file lets you share privately, without the library. Anything specific to your organization is left out: targeted servers, Discord channels, ticket macros, server passwords, memory and history.

1. On the pack's page, click Export.
2. Pick the Format: Handler file (encrypted), unreadable and tamper-proof outside Handler (it only imports on this platform), or Readable JSON, readable and editable by anyone who has the file.
3. For a Handler file, you can tick Protect with a passphrase (at least 12 characters). Without it, nobody can import it. Send it through another channel.
4. Click Download.

To import, open Packs, click Import from a file, pick the file (512 KB at most), type the passphrase if needed, review the Preview (triggers, actions, Permissions needed, To fill in), then Add the pack. It is added to your packs, without being installed.

Publish in the library

The Library is visible to every organization. Others can add your pack to theirs with Add to my packs. Only publish what you are happy to show.

1. In My packs, click Publish a version on your pack.
2. Pick the Pack address: 3 to 48 characters, lowercase letters, digits and hyphens. It can't change later.
3. Write What's new in this version.
4. Click Publish. Handler replays your scenarios with the default values: a failing scenario blocks the publication, and the message names the scenario.

• A published version is frozen. For the next one, raise the Version number in the Presentation step: it must exceed the last published version.
• A Published v… badge appears on the pack. Unlist removes it from the library (only a direct link leads to it), List puts it back.
• Moderation can hide a reported pack, with a reason visible to the organizations involved.