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

[5e OGL] Removing Crit from Global Damage

Hello!

I had another question using the [5e OGL] sheet I have a rage macro as a global damage modifier the macro is something like this 

?{Raging|No,0|Yes,[[{2+{floor(@{base_level}/9),1}kl1+{floor(@{base_level}/16),1}kl1 }]]}[Rage]

I was wondering if there was something I could tack on to remove the crit factor for this, ever crit it doubles my rage damage.

And I guess in addition is there a query I could run similarly on the Global Attack modifier for -5 for GWM?

I was just fiddling in the character sheet the other day and noticed that it actually does remove non-dice rolls from the crit damage. Unfortunately this is only the case when using flat numbers, no queries, no attributes, no formulas. This is simply because it is difficult to be able to guess the purpose of these calculation types before sending to the chat window.

So, if you want the rage damage to not be included on a crit, remove the query and condense the calculation of damage into 2[Rage], 3[Rage], or 4[Rage] when needed.The same would apply for great weapon master.

When I do that, if I crit I get errors I just had 2[Rage] In global damage modifier so I tried to maybe use the guys of the query

[[{2+{floor(@{base_level}/9),1}kl1+{floor(@{base_level}/16),1}kl1 }]]

But that also doesn't work so well either, I just enjoy messing with this stuff even if it isn't necessary.

No, I mean that the global modifier for rage has to be 2[Rage] or 3[Rage], etc. Nothing else. Even just wrapping it within [[]] will cause it to roll on a crit.

I did that and when I did crit I was receiving errors

Nevermind putting the space was doing it

DjSeaghost said:

Nevermind putting the space was doing it

Are you saying that you had " 2[Rage]" (with a space in front) in the field and it was still counting it during a critical hit? If so, that is a bug that needs fixed.

was 2 [Rage]