Upgrade your account to a Community Supporter account and remove most of the site ads.

Reply to thread

Message: <blockquote data-quote="Spatzimaus" data-source="post: 472047" data-attributes="member: 3051">Even though I'm in the "objects don't get saves if the spell doesn't allow it" camp, I thought up a simple way to rationalize it for this one specific spell (NOT as a general rule) that could make everyone happy:An unattended, unconstrained magical item in a Blade Barrier makes a save each turn (bonus = 2 + casterlevel/2, doesn't matter if you call it Reflex, Fortitude, or Will, they're all the same for unattended objects).  If it fails the save, it takes the usual damage (minus its hardness).  If it succeeds, the item is deflected out of the area of the blades.If the item is shielded in any way by another object (for example, if the ring was in the pocket of a corpse), the item does not start taking damage until the "container" is destroyed, at which point it makes saves as normal.If the item is both exposed and constrained (example: the cloak and backpack the corpse is wearing) it doesn't get any saves until the constraining object is destroyed but DOES take damage in the meantime.So, your magical sword or ring gets chipped a bit from being whacked by flying blades, but eventually ricochets off enough of them to fly out of the area.  A mundane sword wouldn't survive the process.To those comparing this to Mordenkainen's Disjunction: unattended items are easy to destroy, even magical ones, just under the normal "strike an object" rules.  Under the core rules I could just as easily Fireball the corpse to destroy all the items on it; they're now unattended, and all are within the area of effect, so even with their saving throws most will be destroyed.MD can be used in much more useful ways, though, like NOT having to wait until the guy is dead.</blockquote>

Verification