Actions

Sharing Actions

You can export an action from the Actions page and import it into another Atlas server. Exporting one action creates an .action file. Select several actions before exporting to create an .actionpack file. Exporting is also a useful backup before making large changes.

To import a shared file, open the Actions page and choose Import Action. Atlas accepts .action, .actionpack, and their .txt versions. An action pack imports every action in the file.

# Before you import

An export contains the action's trigger, script, name, cooldown, restriction, enabled state, and flags. For Webhook actions, the webhook token required to run the action is not included in the export. Atlas generates a new token when the action is imported, so use the new action's URL.

Role IDs, channel IDs, user IDs, and action IDs belong to the server they came from. Update any values that refer to the original server before you enable the imported action. This also applies to scripts that import another action by ID. Export related actions together, then update those imports in the new server.

For actions you expect to share, define values such as role or channel IDs in variables at the top of the script. You only need to update those variables after importing instead of finding every use in the script.

Imported command actions need to sync before they appear in Discord. Test an imported action in a safe channel before relying on it.