Reply to thread

Message

<blockquote data-quote="tetrasodium" data-source="post: 9260304" data-attributes="member: 93670">Yes because it comes with either an angry back and forth trying to get the cantrip plus class abilities (ie extra attack/sneak attack/smite/etc) or regular frustration channeling over not being able to do both depending on how much the GM allows.&nbsp; The only exception is when a player finds a loophole allowing them to do both in a way that is ultimately incredibly broken.&nbsp; All of that is before the constant tracking of &amp; cheese attempts at triggering the secondary booming blade rider thst the GM is expected to just mindlessly walk into&nbsp; GFB may avoid the secondary status in favor of a secondary target, but that extra target of damage just gets more &amp; more broken once a loophole for attack+class features+cantrip is used.The weapon &quot;cantrips&quot; don't work at all like cantrips &amp; cause a lot of problems that either break things when applied to (sub)class features expecting cantrips to work like cantrips or they force the design of other (sub)classes to warp around avoiding them</blockquote>

[QUOTE="tetrasodium, post: 9260304, member: 93670"] Yes because it comes with either an angry back and forth trying to get the cantrip [I]plus[/I] class abilities (ie extra attack/sneak attack/smite/etc) or regular frustration channeling over not being able to do both depending on how much the GM allows. The only exception is when a player finds a loophole allowing them to do both in a way that is ultimately incredibly broken. All of that is before the constant tracking of & cheese attempts at triggering the secondary booming blade rider thst the GM is expected to just mindlessly walk into GFB may avoid the secondary status in favor of a secondary target, but that extra target of damage just gets more & more broken once a loophole for attack+class features+cantrip is used. The weapon "cantrips" don't work at all like cantrips & cause a lot of problems that either break things when applied to (sub)class features expecting cantrips to work like cantrips or they force the design of other (sub)classes to warp around avoiding them [/QUOTE]

Verification