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

Reply to thread

Message: <blockquote data-quote="Daztur" data-source="post: 9436151" data-attributes="member: 55680">A lot of the weapon juggling stuff can be shut down by the DM with a simple "no, stop being silly." But a lot of people ARE legitimately confused about how the TWF system works when you combine WMs and feats and the line between what's an exploit and what isn't is not completely obvious, especially since weapon juggling with loaded pistols WAS a real historical tactic with early firearms.As for dragging people through spike growth I think that was a perfectly fine tactic in 5e that was certainly used by normal players. It was good teamwork, made sense in-character, showed a bit of creativity but nothing abusive. A good fun solid tactic....and now it's ludicrously OPed in 5.5e.Things that used to be fun creative tactics now being BS exploits that I'd have to ban in 5.5e is annoying. And this is REALLY something that they should have seen coming. I mean forced movement is a huge part of 5.5e. How could they not see how powerful even the most basic ways to use forced movement could be?And how do I stop this as a DM? Ban spike growth? Ban players from ever using grappling to drag people into AoEs? No immediately obvious solution of just saying "stop that metagame naughty word" since "I'm going to drag this dude through some spikes" is something that makes perfect sense in character with zero metagaming.This is unacceptably sloppy for the flagship product of what is by far the biggest company in the industry.They REALLY should have hired just one hardcore charop guy waaay back in 3.*ed days and just have him vet all new content. Just one normal charop dude and all kinds of silly naughty word like this and twilight/peace clerics could be prevented.Or hell, just listen to what the charop dudes are saying about the UAs for free. A lot of silly naughty word was published in UAs, widely pointed out as being silly, and then later published intact.</blockquote>

Verification