What macros can do: The Macro language has two main functions: 1) to lookup info from sheets and tokens 2) To roll dice These two functions can be used in concert with each other. Example: A dice formula or modifier can be read from the sheet and used to perform a die roll. They can only send their results to the chat tab. What macros can't do: The macro syntax is not a programming language. It does not have looping or conditional logic. It can't do one thing if a condition is true and another if it is false. Macros cannot write values to sheets or tokens. They can only read them. Where macros are stored: The collections tab of a user's instance of the game. Every user has a different macro collection, but the GM can share specific macros with players. Macros can be written and saved on character sheets. Here they are called "Actions". The syntax is virtually identical but can be simpler for doing sheet attribute lookups. Sheets usually have built in macros. These are stored in the code and accessed by roll buttons. For example, on the D&D 5th Edition by Roll20 Sheet, attacks, saving throws and ability checks are all roll buttons. Macros can be run from the Collections tab. They can also be displayed from the macro bar at the bottom of the screen. A macro or Action defined as a Token Action can be set to display on the token action bar at the top of the screen. These only appear when their associated character token is selected. You can find more specific explanations and examples in the Help Center, or the Help Wiki, both accessible from the Community menu at the top of this page. PS. Macros can also issue commands to API scripts, which can do all sorts of marvelous things, but API access and and scripts are a Pro perk, and not really part of the macro language itself.
