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

Disable questionmark in a macro

Hey all, I am trying to make the Blessed Healer (2+cast lvl extra healing) & Disciple of Life (2+cast lvl selfheal) features from the 5e Cleric Life Domain into a singular role. I've got it working properly except that it asks what level you want to cast it as twice. I'm trying to eliminate this extra step. Healing: 1d8+3 Damage2: (Selfheal) ?{Cast at what level|Level 1,3|Level 2,4|Level 3,5|Level 4,6|Level 5,7|Level 6,8|Level 7,9} Higher Level Cast DMG: 1d8+1 Whenever I add a questionmark to " Cast at what level" in the selfheal macro it becomes the exact same question as the main "Cast at what level?" for the normal healing so it's only asked once, but then it rolls the entire chain for selfheal as a higher level cast in *d8's. Is there any way to have a questionmark in a macro without it actually doing something?
1609199486
GiGs
Pro
Sheet Author
API Scripter
You only have "Cast at what level" listed once in the code above. Can you post the full macro, showing it listed twice?
1609201397

Edited 1609201695
Oosh
Sheet Author
API Scripter
If this is the default 5e sheet behaviour that you're trying to match, I think the upcast Query has a ? on the end. So you need ?{Cast at what level ? |<stuff here>} It only uses the same Query input twice if the text is an exact match. The order also matters. Your Query options will be ignored if the sheet's Query comes first in code order, and the same input from the sheet's Query will be inserted into your macro up there. Is this.... cure wounds that you're trying to modify? If I were you, I'd disable the higher level cast in the Spells tab, and do all the upcast Query and math yourself in the Attacks & Spellcasting section. The sheet's Query is probably: ?{Cast at what level?|Level 1,0|Level 2,1|Level 3,2|Level 4,3|Level 5,4|Level 6,5|Level 7,6|Level 8,7|Level 9,8} Which are not the numbers you want.
Yes this is about Cure Wounds. I I think I figured out the problem but don't know a solution.  Damage2: (Selfheal) ?{Cast at what level|Level 1,3|Level 2,4|Level 3,5|Level 4,6|Level 5,7|Level 6,8|Level 7,9} If I put a ? after Cast at what level it takes the prompts answer and casts it as a higher level, merged with the normal higher level cast of cure wounds.  This is the level 1 cast without the questionmark in the macro. This is the level 2 cast without the questionmark in the macro. These 2 I've shown above are correct and the way I want it, only I get prompted twice. Now, this is a level 1  cast where I add the questionmark in the macro.  The higher cast at first level is a 3d8, which is the corresponding answer in the macro for level 1. A first level spell would selfheal for 3, but instead it rolls 3d8 as a higher level with a questionmark added. I hope I explained it properly!
1609260728
Jordan C.
Pro
API Scripter
This should work, I used the values that the higher level cast uses then added 3 after getting the result (simulating the spell level + 2): ?{Cast at what level?|Level 1,0|Level 2,1|Level 3,2|Level 4,3|Level 5,4|Level 6,5|Level 7,6}+3
Can you post the full macro?
1609261541

Edited 1609261564
Jordan C.
Pro
API Scripter
Jarren K. said: Can you post the full macro? That is the full macro; it's placed in one of the additional damage fields of the spell. The original query is made by the sheet where it applies the additional dice for upcasting.
It works, exactly as I want it to, thank you all for your help!
Jordan C. said: Jarren K. said: Can you post the full macro? That is the full macro; it's placed in one of the additional damage fields of the spell. The original query is made by the sheet where it applies the additional dice for upcasting. Sorry, I was intending for TrippinTurtle to respond. I misunderstood his question for a macro, not a query substituted into a damage field. It looks like it's working now!