I created a level 8 cleric/level 4 ranger and for the level 7 Blessed Strikes feature I selected Potent Spell casting so my wisdom modifier would be added to my cantrip damage. When DND Beyond rolls the cantrip damage it's both adding the wisdom modifier and rolling an extra d8 for the damage. This is happening for both cantrips and weapon damage. My leveled spells don't add the Divine Strikes die. My understanding is that since I chose Potent Spell Casting I should only be getting the wisdom modifier bonus and not that and the extra d8.
Still happening. I noticed it right away the first time I cast a cantrip with my cleric. Where is that extra 1d8 damage coming from?
Are you sure you're not just seeing the normal extra damage die that cantrips get at certain levels? Pretty much all cantrips that deal damage get an extra damage die at level 5, then again at level 11 and level 17.
I can confirm that I'm getting the same bug. I use Magic Initiate (Druid) on my cleric and the system has been adding a d8 of Blessed Strikes damage to all my cantrips, even my druid ones. You can confirm it on my character here: https://www.dndbeyond.com/characters/140015975.
I can confirm that I'm getting the same bug. I use Magic Initiate (Druid) on my cleric and the system has been adding a d8 of Blessed Strikes damage to all my cantrips, even my druid ones. You can confirm it on my character here: https://www.dndbeyond.com/characters/140015975.
Blessed Strikes isn't a d8 anyway. Your cantrips that deal damage, as listed:
TBH, this sounds like you might be using a third-party extension like Beyond20 that's altering the normal behavior of the site. If that's the case, you'd probably need to contact the creators of that extension for help instead.
I created a level 8 cleric/level 4 ranger and for the level 7 Blessed Strikes feature I selected Potent Spell casting so my wisdom modifier would be added to my cantrip damage. When DND Beyond rolls the cantrip damage it's both adding the wisdom modifier and rolling an extra d8 for the damage. This is happening for both cantrips and weapon damage. My leveled spells don't add the Divine Strikes die. My understanding is that since I chose Potent Spell Casting I should only be getting the wisdom modifier bonus and not that and the extra d8.
Still happening. I noticed it right away the first time I cast a cantrip with my cleric. Where is that extra 1d8 damage coming from?
Are you sure you're not just seeing the normal extra damage die that cantrips get at certain levels? Pretty much all cantrips that deal damage get an extra damage die at level 5, then again at level 11 and level 17.
Can you share a link to your character, and make sure their "Character Privacy" setting is set to "Public"?
Need help with D&D Beyond? Come ask in the official D&D server on Discord: https://discord.gg/qWzGhwBjYr
I can confirm that I'm getting the same bug. I use Magic Initiate (Druid) on my cleric and the system has been adding a d8 of Blessed Strikes damage to all my cantrips, even my druid ones. You can confirm it on my character here: https://www.dndbeyond.com/characters/140015975.
Blessed Strikes isn't a d8 anyway. Your cantrips that deal damage, as listed:
-Fire Bolt: 2d10 (Elven Lineage source)
-Poison Spray: 2d12 (Magic Initiate: Druid source)
-Sacred Flame: 2d8+5 (Cleric source)
-Starry Wisp: 2d8 (Magic Initiate: Druid source)
All of that seems to be working exactly as intended. The character is level 8, so they get 2 damage dice in their cantrips, that's completely normal.
I'm not sure why you're not getting the bug, but it's definitely happening on my end. Is there a way I can submit a screenshot of what's happening?
Edit: I made a copy of the character and the bug went away. Not sure why.
TBH, this sounds like you might be using a third-party extension like Beyond20 that's altering the normal behavior of the site. If that's the case, you'd probably need to contact the creators of that extension for help instead.
Need help with D&D Beyond? Come ask in the official D&D server on Discord: https://discord.gg/qWzGhwBjYr
It turns out the issue is indeed being caused by Beyond20, and there is an option to turn it off on the top of the sheet.