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

mega macros, possible?

im really new to macros here in roll20, been trying my best to make them as automatic as possible but i find myself stuck when attempting to make macros that not only take into account character's stats but use the value itself to decide whether the it was a hit or not, and at the same time having specific crit and fumble values. [[1d100+@{target|defense}]] ACC 90  this is the average skill roll i have set up as a macro that features only one target (inlcuding one with more would result in a unnecesary long forum post) so checking the wiki (which is great btw, awesome job guys!) i have come up with this, which i think many of you will consider crude and basic, but hey, second week here! now my questions. is there a way to include a success result, while taking the character defence in consideration? do i have to make it a nesting macro to include crits and fumble? and after how many hours spent breaking my skull with this is it ok for me to start bashing my head against the wall? well, thanks in advance for any tip or anything, getting kinda desperate. i apologize to for my english not a native speaker. 
1499975094
The Aaron
Pro
API Scripter
Macros are limited to just a collection of mathematical calculations, by and large.  If you can think of a way to represent what you want in a single mathematical equation (with a single resultant value), then you will be able to do it.   Where you usually run into issues is needing to make some decision based on the result of a roll.  There are some complicated ways to do that if you don't mind losing the value (say by multiplying it by a decimal and adding another then using round or floor to arrive at a result), however you couldn't both display the result of a roll (you rolled a 23 to hit) and display the result (you hit an AC 23).   Complicated decision based results are the purview of the API, which is capable of implementing the type of state machine you'd need.  Roll Templates can fake this a little bit, as they can show or hide output based on limited inspection of various rolls.