Wilco
I have tested with IsGM, Power Cards, and Josh's Condition and Status remind.
Jim
I have tested with IsGM, Power Cards, and Josh's Condition and Status remind.
Jim
on("chat:message", function (msg_orig) { var msg; // Exit if not an api command if (msg_orig.type != "api") return; msg = _.clone(msg_orig);
You need to have Mentor status to load APIs.Cesar D. said:
Do i have to put some code in order for the power cards to work? ive tried to just put a test macro but it never works, is something wrong with my chrome or what?
{ . "content": "!msg $[[0]]", . "inlinerolls": [ . . { . . . "expression": "[HR(20—(ceil((10)/1e10) + ceil((10)/4)))] 1D20", . . . "results": { . . . . "resultType": "sum", . . . . "rolls": [ . . . . . { . . . . . . "text": "HR(20—(ceil((10)/1e10) + ceil((10)/4)))", . . . . . . "type": "L" . . . . . }, . . . . . { . . . . . . "dice": 1, . . . . . . "results": [ . . . . . . . { . . . . . . . . "v": 19 . . . . . . . } . . . . . . ], . . . . . . "sides": 20, . . . . . . "type": "R" . . . . . } . . . . ], . . . . "total": 19, . . . . "type": "V" . . . }, . . . "rollid": "—JbghwS——29c5v977dAJ", . . . "signature": "00a0ca795f48b2a499e0ac4d8ea0a2b4b1a9c8f8129ab12829ece6ac311d11f130a3631a182e8c8cc0d2d98a7b2f5d028c5df9091afb626864fd73146afcc100" . . } . ], . "playerid": "—JS3qKxIUPHLzSbK24ve", . "selected": [ . . { . . . "_id": "—Jb8F8l1nGmAx9fWf8vU", . . . "_type": "graphic" . . } . ], . "type": "api", . "who": "The Aaron" }
OldSchoolChris said:
I will be honest: powercard script is why I decided to pay a year at a time. It makes Roll20 all the more worth while.
Wade said:
Does the current version of HoneyBadger's power card generator (https://r20cpcmg.codeplex.com/) still work fully with the most recent updates to this script?
HoneyBadger said:
Wade said:
Does the current version of HoneyBadger's power card generator (https://r20cpcmg.codeplex.com/) still work fully with the most recent updates to this script?
It think it does right now... however, I've been quietly working on a new version of power cards. Trying to make it smaller and less prone to errors. The holidays, getting engaged, and a new WoW expansion have made it difficult to spend time working on it however. So don't expect it any time soon.
Which change?JonMichael (Vante) said:
@TheAaron, does this change need to go into a specific line location?
ATTACK: [[1d20+5]] vs AC:@{target|AC} (@{target|token_name})
!power --name|TIDAL SPIRIT SHOT --usage|At-Will --action|Standard Action --Keywords|Primal, Weapon --Targets|Each enemy in the burst --Range|Area burst 1 within 4/8 range --format|dnd4e --attack?{Number of Targets|1}|[[1d20+11]] --defense|AC --damage|[[1d4+1]] damage, and you can slide the target 1 square.
!power --name|**@{selected|token_name} | Shout of Triumph** --bgcolor|#C40233 --leftsub|Encounter --rightsub|Standard Action --Keywords|Arcane, Implement, Thunder --AoE|__Close Blast__ 3 --Effect|Each ally in the blast may be __slid__ up to @{Con} squares. --AoE|Close Blast 3 --attack|vs Fortitude --Target 1| [[1d20 + @{HalfLevel} + @{Cha} + @{Blade-A-CFEM} + ?{MiscToHit?|0} ]] vs [[@{target|Foe 1|Fort}]] @{target|Foe 1|token_name} --Target 2| [[1d20 + @{HalfLevel} + @{Cha} + @{Blade-A-CFEM} + ?{MiscToHit?} ]] vs [[@{target|Foe 2|Fort}]] @{target|Foe 2|token_name} --Target 3| [[1d20 + @{HalfLevel} + @{Cha} + @{Blade-A-CFEM} + ?{MiscToHit?} ]] vs [[@{target|Foe 3|Fort}]] @{target|Foe 3|token_name} --Target 4| [[1d20 + @{HalfLevel} + @{Cha} + @{Blade-A-CFEM} + ?{MiscToHit?} ]] vs [[@{target|Foe 4|Fort}]] @{target|Foe 4|token_name} --Target 5| [[1d20 + @{HalfLevel} + @{Cha} + @{Blade-A-CFEM} + ?{MiscToHit?} ]] vs [[@{target|Foe 5|Fort}]] @{target|Foe 5|token_name} --Target 6| [[1d20 + @{HalfLevel} + @{Cha} + @{Blade-A-CFEM} + ?{MiscToHit?} ]] vs [[@{target|Foe 6|Fort}]] @{target|Foe 6|token_name} --Target 7| [[1d20 + @{HalfLevel} + @{Cha} + @{Blade-A-CFEM} + ?{MiscToHit?} ]] vs [[@{target|Foe 7|Fort}]] @{target|Foe 7|token_name} --Target 8| [[1d20 + @{HalfLevel} + @{Cha} + @{Blade-A-CFEM} + ?{MiscToHit?} ]] vs [[@{target|Foe 8|Fort}]] @{target|Foe 8|token_name} --Target 9| [[1d20 + @{HalfLevel} + @{Cha} + @{Blade-A-CFEM} + ?{MiscToHit?} ]] vs [[@{target|Foe 9|Fort}]] @{target|Foe 9|token_name} --Hit|[[ ([NH]1d6) +@{Cha} + @{Blade-D-FEMM} + ?{MiscToDamage|0} ]] **Thunder** damage | Crit [[ (1*6) +@{Cha} + @{Blade-D-FEMM} + [NH]2d6 + ?{MiscToDamage} ]] --^1On Hit|Each foe is __slid__ up to [[@{Con}+1]] squares.
Hrm, I don't typically use apostrophes in character names, so this hasn't come up. I may be able to fix it, dunno. Does Roll20 do the space in front of alt characters normally or only through the API?Aetheria said:
I do hope the colin issue gets fixed soon as it is bugging me hardcore (it looks so ugly!).
Can you submit the new edit to the script that fixes it? Or is it not possible until the new release?
Minor bugs:
- Apostrophes in the --title tag will break the tooltip, showing only the text up to right before the first apostrophe. For example, "Mímika Zy'pher fires her gun." shows up as "Mímika Zy".
- Unique characters like vowels with accents over them produce a strange result in the --emote tag, placing a single space before every character that isn't "normal". For example, "Mímika Zy'pher fires her gun." shows up as "M ímika Zy'pher fires her gun."
Requests:This I don't know about either. There's so much math and other dice rolls and such that could be used in there, that I would basically be re-writing the dice parser inside the script.
- Functionality in the highlight tags (ie. "[LR#]") where "#" can actually be a modifiable integer? For example, "[LR(2+?{Foo})]". So if Foo was 2, it'd function as "[LR4]".