Talk:Beam of Radiance (3.5e Spell)

Power Level

True that it's paladin, but I take issue with the idea of uncapped swift action blasts with an additional gravy effect. Not at 1st level at least, I prefer uncapped spells are the realm of higher level things... 3rd or 4th for paladins. -- Eiji-kun 06:28, 21 September 2011 (UTC)

It's only 1d6 damage per two class levels (or 1d6 per class level with Professional Caster/whatever). I could be persuaded to reduce the gravy or increase the action size, though. --Foxwarrior 06:49, 21 September 2011 (UTC)

IMO standard would be good... if most paladins didn't have auto-swift spells anyway (battle blessing) so it's a bit of a pickle. Don't know what to do with that one. Really I'm more concerned with the uncapped bit over the gravy. -- Eiji-kun 12:35, 21 September 2011 (UTC)

Your expression of concern by itself does not convince me. Try other words. --Foxwarrior 19:07, 21 September 2011 (UTC)

Eiji is expressing a concern that this spell, by virtue of being uncapped, remains a relevant and useful level 1 spell far after other level 1 combat spells. The uncapped bit may also lead to it being valued over some 2nd and 3rd level spells that hit their caps, which is a bit odd. Since Paladin CL is half their paladin level, they can start out dealing 2d6 per beam, and even in the uncapped scenario only get up to 10d6. Which is decent, and probably better than most of their 2nd level spells at that CL. Capping the damage value keeps it from ever being stronger than a capped 2nd or 3rd level spell, but that may run counter to your design goals and not be something you particularly care about, especially if you think level 1 spells are weak-sauce and need a boost in general.

While I'm with him in a capping preference (5d6 IMO), I don't know that an action change is needed as much as a clarification and some additional work. Casting the spell is a swift action, but it's not clear that the ranged attack is made as part of that swift action and then as a swift action again for every subsequent round that the spell is active, or if it's a swift to cast and an attack or some other action per beam. Clarification on this point would be nice, and in the event that it is an attack action a limit to attacks made with the primary hand (to prevent TWF beamsage) would probably also be appropriate. - Tarkisflux ^Talk 19:57, 21 September 2011 (UTC)