Character Vault
Any Concept / Any System
Compendium
Your System Come To Life
Roll20 for Android
Streamlined for your Tablet
Roll20 for iPad
Streamlined for your Tablet

Personal tools

Script:Rollable Table Macros

From Roll20 Wiki

Revision as of 02:35, 18 February 2024 by Robert R. (Talk | contribs)

Jump to: navigation, search

Main Page: API:Script Index

API ScriptAuthor: Nathanael W
Version: 1.1
Last Modified: 2017-05-22
Code: RollableTableMacros
Dependencies: none
Conflicts: none

This is a simple script that allows you to execute chat commands with a rollable table. Basically, this script will select an item on a table as normal, but instead of displaying the result as a rollable table result, it enters the title of the table item into the q Text Chat. This allows you to use things like inline rolls and macros.

Contents

Syntax

!rtm table-name
!rtm table-name Message As
!rtm table-name myself

Installation and Configuration

The API is avaiable in the One-Click install menu in Roll20.

Or install manually: Copy the script's code, available from the menu on the right and stored at Roll20's API GitHub Repository. Paste the code into a new script in your campaign's API Script Editor. Save the new script and it will be available inside your campaign.

Script Use

Simply type !rtm table-name and the script will select an item from the specified table (respecting item weight as usual). The name of the item will be entered into the chat, and any commands/rolls will be run as normal. An exception is roll queries, which are not supported at this time.

By default, the 'from' or 'speaking as' of the chat messages will be the formated name of the table (example: wild-magic-surge becomes Wild Magic Surge). However, you can specify your own names by including it after the table name in the command (example: !rtm table-name Message As). Alternatively, !rtm table-name myself will set the speaking as to whichever player entered the command.

Changelog

v1.1 (2017-05-22)

  • update


v1.0 (2017-04-26)

  • Release


2024/2/17- functionally not working, perhaps needs an update

Related Pages