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 .
×

Nested Macros not being called

1592852344

Edited 1592852423
I am attempting to create my own version of a Pokemon mystery Dungeon campaign and I am running into some issues with Nested Macros the current Ability I am working with goes like this :  &{template:default} {{name=Attack!}} {{Hit | Roll:=[[ceil(@{Move 1 Accuracy}*?{Accuracy Change?|No Change, 1|-6, .25|-5, .29|-4, .33|-3, .40|-2, .50|-1, .66|+1, 1.5|+2, 2.0| +3, 2.5|+4, 3.0|+5, 3.5|+6, 4.0})]] | [[d100]]}} {{?{How effective is the move?|Effective, #Effective-P1|Not Very Effective, #Not-Very-Effective-P1|Super Effective, #Super-Effective-P1}}} {{Critical | Roll:=[[ceil(((@{Base Speed}/2)/(256))*100)]] | [[d100]]}} I have 3 macros in the Collections tab named Effective-P1, Not-Very-Effective-P1, Super-Effective-P1. For some reason when the table is output it shows the text  and does not call the macro. (I have tried this with both an Ability(%) and Macro(#) ) When I do the macro by itself it will output fine  {{Effective:=[[ceil(((((@{CH1|Level}*2/5+2)*@{CH1|Attack}*@{CH1|Move 1 Power}/@{target|Defense})/50)+2)*@{CH1|Move 1 STAB}*1)]]}} I would like this to be a drop down menu because there are many different modifiers I will have to add for physical/special attack and physical special defense. Can anyone point me in the right direction ?
1592856365
GiGs
Pro
Sheet Author
API Scripter
See here;&nbsp; <a href="https://wiki.roll20.net/Macros#Advanced_Usage_for_Roll_Queries" rel="nofollow">https://wiki.roll20.net/Macros#Advanced_Usage_for_Roll_Queries</a> Note that nested macros are expanded and placed into the top macro before being run. So if the nested macro has an commas, closing curly brackets, or pipes (, } or |) in it, it will cause the top level query to break. Note that attribute calls are exempt from this, so @{name|attribute} always works properly and does not need replacing. If your macros include the {{ }} around them, remove those and it should work. I''m not seeing anything else in the posted macro that would cause an issue.