Complex actions can be built using the logic operators in Streamer.bot.
These will take data from various sources and evalutate them to direct the action, so understanding how they interact is key to building the workflow you want.
All logic in Streamer.bot must be performed against active Arguments. As any argument can only persist until the end of the running action if data need to be saved between actions, Global Variables can be used. Their data must be copied into an Argument to be usable
Global Variables should always be stored in
camelCaseie. with a lower case initial letter.
Streamer.bot can not retrieve data from any store if the initial letter is capitalised.
It is best practice to always name your
Argumentssomething different than the
Globalyou are reading from.
This will make your workflow easier to read and debug and can also prevent strange issues with logic and inline functions
Global Variableinto an argument
Actionif logical test is
Streamer.bot has 2 main variable types;
Arguments will only persist until the end of the currently executing action (or any Action called by it)
Sub-actions in the UI can only use
Arguments as a data source
C# can access an Action's active Arguments using the
Globals will persist beyond the end of the action and are generally used to store data that needs to be read by future Actions
Their data can not be used directly in an Action. To use them a
Global (Get) sub-action must be added to copy the currently stored data into a temporary argument. Subsequent sub-actions can then use this argument and data can be written back to Global storage using a
Global (Set) sub-action.
This should always be in
camelCaseie. with a lower case initial letter, Streamer.bot can not retrieve data from any store if the initial letter is capitalised