Is this just an oversight because the field "Attack/Save" can only support one value?
Is the spell intended to work both ways (based on original rules text it should)
The spell itself works with both melee and ranged weapons according to the actual rules.
That "Attack/Save" feature is part of D&D Beyond's presentation of the spell and is not part of the actual rules. The fact that it says "melee" is a data entry error on D&D Beyond's part.
Same thing with Shillelagh. It says "Melee" but the spell itself is not a Melee attack...or ANY attack at all.
While I understand the intent, some people assume this restricts the spells mode or way its executed. I think WotC should improve/clarify these 'extra' fields.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
In D&D Beyond, truestrike as the "Attack/Save" field listed as melee.
The original printing of this spell in PHP and SRD do not mention melee anywhere in the RULES TEXT. Spells like booming blade do call out melee.
Is this just an oversight because the field "Attack/Save" can only support one value?
Is the spell intended to work both ways (based on original rules text it should)
The spell itself works with both melee and ranged weapons according to the actual rules.
That "Attack/Save" feature is part of D&D Beyond's presentation of the spell and is not part of the actual rules. The fact that it says "melee" is a data entry error on D&D Beyond's part.
pronouns: he/she/they
Same thing with Shillelagh. It says "Melee" but the spell itself is not a Melee attack...or ANY attack at all.
While I understand the intent, some people assume this restricts the spells mode or way its executed. I think WotC should improve/clarify these 'extra' fields.