Concepts

Context

Context is the information Atlas has about the event it is handling. Atlas uses it throughout the bot. Commands, plugins, actions, restrictions, and scripts can all use details from the current server, member, channel, message, or event.

Context matters most when writing scripts because it decides which tags have a default value. A Message Create action has a message, user, and channel in context. A Slash Command action has the person who ran the command, its channel, and command options. A feed delivery has {$feed} and {$feedItem}.

Tags often use context when you leave out a value. {user.name} uses the user in context. {message.delete} uses the message in context. In the Tags documentation, a parameter with a default such as context Channel means that you can leave it out when the current context includes a channel.

An action can still work without every kind of context. An interval action has no message because it runs on a schedule. A webhook action has request data instead. In those cases, provide the channel, user, message, or other value directly when a tag needs one.

The action trigger pages list the context each trigger provides. Plugin guides list their script variables where they have their own context.