Learn

Troubleshooting

# My command is missing

Atlas syncs slash commands with Discord after you save a change. Wait a few minutes, then check that the action and its command trigger are enabled. Avoid repeatedly changing the command while it is syncing. Discord limits how many command changes a server can make each day.

If Atlas was offline, it will sync when it reconnects. See Syncing for more detail.

# My script has an error

When a script fails, Atlas usually sends an error message and the location of the error to the channel where the action ran. The message includes a snippet of the script with a pointer to the part that failed. Check the tag's spelling and parameters against Tags, and make sure the tag is available for the action's trigger. For example, {message} only works where Atlas has a message in context.

Start by reducing the script to one line, verify it works, then add the next part back. Your First Action shows a small working example.

# Atlas cannot assign a role

Atlas needs permission to manage roles. Its highest role must be above the role it is trying to assign or remove. Check the bot's role and the server role hierarchy, then try again.

# A plugin is enabled but does nothing

Check its restrictions and required settings. Many plugins need a destination channel, selected role, or created item before there is anything to do. Open the plugin's guide from Plugins and check its setup section.