Reply to thread

Message

<blockquote data-quote="Lyxen" data-source="post: 8416770" data-attributes="member: 7032025">Then too bad, it's clearly what the devs intended.And in these case, it's not your abilities as a player, it's only NPCs and monsters...And again, although once more it can be played in many equally entertaining ways, 5e is not even about house rules but about rulings that don't necessarily want to make their way into house rule. You can (and probably should) make a local ruling for each individual NPC as to whether a given trait is a spell (or a magic item, or an innate power, or whatever else), you don't need to make it a &quot;house rule&quot; that would apply to all future NPCs. As the devs say this &quot;would be counter to the open-endedness of D&amp;D&quot;, why tie all your future games on the local decision made for an NPC, moreover one that you probably don't even need to make, since when using the power, no-one might even have counterspell ready, or a chance to perceive the casting and do anything about it ? Just make a simple ruling if the situation arises, no need to over think it and over design it in advance...And for me, it is inflated waaaayyyy out of line with people (not you) whining all over the place about their precious counterspells, mage slayer feats, and &quot;right to know when a spell is being cast&quot;. Not to mention all the expert designers (despite not having ever designed anything of note) around here (not you again) who claim once more that the people who have designed the most successful TTRPG game ever, and who have finally brought that hobby into a respectable spotlight are basically idiots who have no idea what they are doing and who have, once more, done something idiotic.Of course it can, it can be ignored, discarded, improved, made to suit your table and your game. These are just new possibilities and even if you are using the published module, you are free when you run it to use the abilities any way you like and to allow counterspell and mage slayer if you think your players will enjoy it more.</blockquote>

[QUOTE="Lyxen, post: 8416770, member: 7032025"] Then too bad, it's clearly what the devs intended. And in these case, it's not your abilities as a player, it's only NPCs and monsters... And again, although once more it can be played in many equally entertaining ways, 5e is not even about house rules but about rulings that don't necessarily want to make their way into house rule. You can (and probably should) make a local ruling for each individual NPC as to whether a given trait is a spell (or a magic item, or an innate power, or whatever else), you don't need to make it a "house rule" that would apply to all future NPCs. As the devs say this "would be counter to the open-endedness of D&D", why tie all your future games on the local decision made for an NPC, moreover one that you probably don't even need to make, since when using the power, no-one might even have counterspell ready, or a chance to perceive the casting and do anything about it ? Just make a simple ruling if the situation arises, no need to over think it and over design it in advance... And for me, it is inflated waaaayyyy out of line with people (not you) whining all over the place about their precious counterspells, mage slayer feats, and "right to know when a spell is being cast". Not to mention all the expert designers (despite not having ever designed anything of note) around here (not you again) who claim once more that the people who have designed the most successful TTRPG game ever, and who have finally brought that hobby into a respectable spotlight are basically idiots who have no idea what they are doing and who have, once more, done something idiotic. Of course it can, it can be ignored, discarded, improved, made to suit your table and your game. These are just new possibilities and even if you are using the published module, you are free when you run it to use the abilities any way you like and to allow counterspell and mage slayer if you think your players will enjoy it more. [/QUOTE]

Verification