You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If i try to roll a critical strike with foundry native rolls it just rolls the normal damage and no additional dice.
i found that the damage formula is written in Brackets
if i delete the brackets and write it like 1d6+3[Slashing] i would be able to roll crit damage. But as son as i roll out of DnD Beyond again the formula is written with brackets again. Anyone else encountered this issue and know how to fix it?
The text was updated successfully, but these errors were encountered:
That is a dnd5e system bug unfortunately... It had been mentioned when adding the native support when talking to the midi-qol devs here: https://gitlab.com/tposney/midi-qol/-/issues/1087
The issue above also explains why the parenthesis are required in the formula, if you want to read that conversation.
I didn't remember the issue until now but looks like we had known about it before, and it had been reported to the dnd5e developers, who fixed it I assume, and last month, it was reported again by someone else as a regression (i.e something that was fixed but then broken again in a subsequent release) here: foundryvtt/dnd5e#2343
Nothing to do on your side other than wait for the dnd5e system developers to fix the logic for crits on their side.
allright thanks for the realy fas response. We just paused our campain for1.5 month so it makes sense that the issue is kinda new for me. Thanks for your great work!
If i try to roll a critical strike with foundry native rolls it just rolls the normal damage and no additional dice.
i found that the damage formula is written in Brackets
if i delete the brackets and write it like 1d6+3[Slashing] i would be able to roll crit damage. But as son as i roll out of DnD Beyond again the formula is written with brackets again. Anyone else encountered this issue and know how to fix it?
The text was updated successfully, but these errors were encountered: