Oosh said: As far as I know there's no way to do this with a global modifier - it doesn't call the modifiers in the right part of the macro to change the attack rolls. They modify the result, rather than the actual roll. Are you saying this homebrew spell is the thing causing the cs19? As in, you cast this spell on someone and all of their attacks are now cs>19? If so, the easiest (but not accurate) way to achieve this is to edit the d20 Attribute on your sheet, change its value to 1d20cs>19. Change it back when the spell wears off. If your DM has API you can use a script to macro it. This approach is inaccurate because it will also affect saving throws and skill checks. AFAIK there is no way to affect the d20 roll ONLY for attack rolls, so for a truly accurate representation of the effects you would need to edit each attack on the sheet/add a second version of each attack on the sheet. I'd say it depends on personal preference - I have a Hexblade character where I just use a second copy of my main 2 attacks for the expanded crit range, because it is only attacks and only on the one target which are effected, so it would be silly to modify the core d20 roll. If it changes all of your attacks & spells on all targets, then modifying the core roll is probably your best bet: remember the crit range is (RAW) irrelevant in ability checks & saving throws anyway, so you can just ignore it. If you choose this option, don't forget you can rearrange Attributes - I'd be dragging that d20 Attribute to the top of the list so you can edit it easily, if you don't have API access. If it's the kind of ability that you have up ALOT (like towards 50% uptime) your other option would be to throw a query in the d20 Attribute: 1d20cs>?{Crit range?|20|19|18} This would drive me boonta, personally, but YMMV! This will also mess with the {rtype} for advantage/disadvantage will need some HTML substitution to make it work I think. Thank you so much! I opted for moving the d20 to the top and modifying it because it effects all attacks and spells on all targets, and I'll keep the query in mind if I use the option more frequently than anticipated. Thanks for the comprehensive information!