Roll20 uses cookies to improve your experience on our site. Cookies enable you to enjoy certain features, social sharing functionality, and tailor message and display ads to your interests on our site and others. They also help us understand how our site is being used. By continuing to use our site, you consent to our use of cookies. Update your cookie preferences .
×
Create a free account

[MetaScript ZeroFrame] Thread 2

1636727207

Edited 1636727728
timmaugh
Pro
API Scripter
ZeroFrame FILE LOCATION:   My Personal Repo  & 1-click Installation META SCRIPT: This script is a meta-script, and basis of the ZeroFrame Meta Toolbox. It can be used on its own, or in conjunction with the other meta-toolbox scripts, to modify other scripts' API commands. ABSTRACT: ZeroFrame provides a way to organize, order, and loop over the other meta-scripts in the Meta Toolbox. It can unpack inline-rolls right in the command line, and lets you defer things like inline roll detection or the syntax token (the structures that would trigger the other meta-scripts) by escaping the text with a backslash. This thread was opened because the previous thread for this metascript closed. If you want to read some of the previous usage examples or questions, you can visit this thread .
1636727508

Edited 1636727515
timmaugh
Pro
API Scripter
Version 1.0.10 Released November 12, 2021 FIXED : Bug that incorrectly referenced rolls if multiple inline rolls were deferred for the same loop iteration Update Notes When a roll is deferred, it is actually generated in a new message (separate from the original). The inline roll results are appended to the original set of inline rolls (from any loop passes that occurred previously), and the inline roll markers in the command line are replaced (e.g., $[[0]] is the first roll in the new message, but there are already 2 rolls in the original message; therefore this roll marker needs to become $[[2]]). Previously, if more than one inline roll was deferred to the same loop, the replacement of these markers was flawed. The roll information was still present in the message, but the retrieval was incorrect. With this update, the proper order and reference to each roll is preserved. There is no usage change for this version, and users should not see a noticeable change in the way the script functions.