Perhaps the most important piece of Streamer.bot, actions are at the center of everything you do.
You can configure actions for anything from basic alerts and shoutouts to extremely complex integrations such as TerrierDart's Leaderboard Points System
Actions consist of configurable sets of sub-actions that can be executed by Streamer.bot's event sources, such as Triggers, Commands, various integrations such as Elgato Stream Deck, and even your own voice!
Sub-actions even have the ability to trigger other actions, giving you the ability to organize significant pieces of your setup into consolidated sections, and share logic across multiple event sources.
As sub-actions are executed, another important feature of Streamer.bot comes into play, the argument stack, which consists of all variables available at a given time.
Each sub-action has the ability to populate new variables for upcoming sub-actions, read existing variables from earlier sub-actions, or even modify them on the fly!

The actions tab is split into 3 main parts:
Actions - All of your configured actions are listed here, sorted by groupTriggers - All triggers configured for the selected action will be listed hereSub-Actions - All sub-actions configured for the selected action will be listed hereTo create your first action, Right-Click in the actions pane and select Add to open the configuration dialog

Default queue is configured as a non-blocking queue, meaning actions will execute immediately on request and are allowed to run concurrently.Weight configuration on sub-actions, allowing you to adjust the probability that specific sub-actions will be chosen.Paused stateRight-Click any existing action to reveal the context menu:

Many of the action configuration options outlined above can be quickly modified here.
Additional context menu options are outlined below:
Add Action dialog.Settings tabID of the selected action to your clipboard.To activate the sub-actions pane, you must first select an action via Left-Click in the actions pane.
With an action selected, you can then Right-Click anywhere in the sub-actions pane, on the right, to browse available sub-actions and add them to your selected action.



Settings tabMove to Group sub menu will also display below this optionRandom ExecutionThis will only execute a single, random sub-action from within the group.Weight options on sub-actions inside that group.
Weighting is used to make a sub-action more or less likely to be chosenSettings tabUp, Down, Top, BottomIn Streamer.bot, all actions exist within a queue. The Default queue is created automatically and will contain all action executions unless specified otherwise.

In this section, you will find all the queues that have been created.
At a glance, you can view the status of several queue properties:
Pending Count: Number of actions waiting to be executed within the respective queueCompleted Count: Number of actions that have completed execution within the respective queue
Paused: Shows the current paused status of this queueBlocking: Shows whether the queue is configured as a Blocking queueYou can Right-Click within the Queues pane to reveal the context menu:

Paused, you can select Resume to restart a queue and trigger any pending actions.Active, you can select Pause to temporarily stop new actions from being triggered in that queue. Once resumed, pending actions will be processed.Blocking state of the selected queue.If selected, check mark will appear beside Blocking, indicating that the queue will execute actions in sequence.To create a new queue, Right-Click within the queues pane and select Add

Blocking option.The pending actions view will display any queued actions which are waiting to run.
The action history view will display a log of all actions that have been executed by Streamer.bot

At a glance, you can view the following properties:
Name: The name of the executed actionState: The current status of the executed action
Completed, Cancelled, PendingVariables: The number of variables populated by this actionDuration: Time, in milliseconds, the action took to finish executionQueue: The name of the queue this action was executed inQueued At: The date and time the action was initially queued for executionStarted At: The date and time the action began executionCompleted At: The date and time the action finished executionYou can Right-Click on any entry to open the context menu:


