Difference between revisions of "Script:Exalted Successes"
From Roll20 Wiki
(→Changelog) |
|||
| Line 2: | Line 2: | ||
|name=Exalted Successes | |name=Exalted Successes | ||
|author={{user profile|235259|Brian}} | |author={{user profile|235259|Brian}} | ||
| − | |version=2. | + | |version=2.1 |
|dependencies={{api repository link|Interpreted sendChat}} | |dependencies={{api repository link|Interpreted sendChat}} | ||
|lastmodified=2015-01-08}} | |lastmodified=2015-01-08}} | ||
| Line 37: | Line 37: | ||
=== Changelog === | === Changelog === | ||
| + | {{changelog version|2.1|2015-03-14|* [bugfix] Fixed infinite loop chat message problem}} | ||
{{changelog version|2.0|2015-01-08|* Release}} | {{changelog version|2.0|2015-01-08|* Release}} | ||
Revision as of 06:01, 14 March 2015
Version: 2.1
Last Modified: 2015-01-08
Code: Exalted Successes
Dependencies: Interpreted sendChat
Conflicts: None
After posting a message with a roll (either regular or inline) which uses d10s, Exalted Successes will echo the number of successes (or botches) using the dice system in Exalted. This script does not take into account Sidereal Astrology modifying the target number, nor does it try to filter players posting a roll with modifiers and the like. This script does not scrutinize based on normal die rolls (10s count double) vs. damage rolls (10s don't count double).
If this script is in the campaign, every roll which uses d10s will be reported.
Notes
You can achieve similar results with rollable tables, without resorting to the scripts that require mentor-level accounts.
| Name | Weight |
|---|---|
| 0 b | 1 |
| 0 | 5 |
| 1 | 3 |
| 2 | 1 |
Assuming the table is named exalted, you can then roll on it with something like /roll 8t[exalted]. This solution won't accurately report botches, but you can check the roll itself after the fact if no successes were garnered.
For bonus points, you can make alternate tables for damage (1 weighted 4 and no 2) and for Sidereal shenaniganry. It also doesn't require any scripting to achieve.
Changelog
v2.1 (2015-03-14)
- [bugfix] Fixed infinite loop chat message problem
v2.0 (2015-01-08)
- Release
