The damage roll for Channel Divinity: Sear Undead on the character sheet, web and mobile, shows 1d8 regardless of the characters Wisdom modifier. This should be a multiple d8 of the Wisdom modifier per the rules: "Whenever you use Turn Undead, you can roll a number of d8s equal to your Wisdom modifier (minimum of 1d8) and add the rolls together. Each Undead that fails its saving throw against that use of Turn Undead takes Radiant damage equal to the roll’s total. This damage doesn’t end the turn effect."
On the list of Actions the correct value is displayed in the text i.e., "Whenever you use Turn Undead, any Undead that fails its saving throw takes 5d8 Radiant damage. This damage doesn’t end the turn effect." when the character has a Wisdom modifier of +5.
This issue has been mentioned in previous threads on the Cleric character sheet but those posts included other issues and several of them have been marked "Resolved" so I am splitting this off into it's own thread to track the resolution of this specific issue.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
The damage roll for Channel Divinity: Sear Undead on the character sheet, web and mobile, shows 1d8 regardless of the characters Wisdom modifier. This should be a multiple d8 of the Wisdom modifier per the rules: "Whenever you use Turn Undead, you can roll a number of d8s equal to your Wisdom modifier (minimum of 1d8) and add the rolls together. Each Undead that fails its saving throw against that use of Turn Undead takes Radiant damage equal to the roll’s total. This damage doesn’t end the turn effect."
On the list of Actions the correct value is displayed in the text i.e., "Whenever you use Turn Undead, any Undead that fails its saving throw takes 5d8 Radiant damage. This damage doesn’t end the turn effect." when the character has a Wisdom modifier of +5.
This issue has been mentioned in previous threads on the Cleric character sheet but those posts included other issues and several of them have been marked "Resolved" so I am splitting this off into it's own thread to track the resolution of this specific issue.