dnd spell that draws staff out of living trees

In Dungeons & Dragons, if you play a rogue, the class description describes your key powers. All rogues make sneak attacks, cunning actions, and use evasion. If you play a spellcaster, your powers sprawl into the spell list. Every wizard tends to prepare the same powerful spells on the list. Once wizards reach fifth level, they all start casting fireball. Spells also appear as a monster powers, turning some spells into foundational abilities that span the game.

I've asked D&D players and dungeon masters what spells they find the most annoying or the least fun in play. Four spells dominated the list of annoyances.

All of the annoying spells offer enough power to make them common in play once characters can cast them. Like sneak attack, these tend to appear in most fights, but unlike sneak attack, these spells sap a little bit of the fun out of play.

Some readers will ask, "So what? Just ban the spells from your game." But DMs in the Adventures League cannot ban anything. At best, authors of adventures can concoct ways to discourage the spells. In Barovia, Banishment fails. In the D&D Open, players lose points for using spells like Hypnotic Pattern.

Curiously, none of the 4 annoying spells bothered players of previous D&D editions. I wondered why. When I investigated the origins of these 4 spells, I discovered that all introduced critical changes that turned them from forgettable to aggravating. None of these spells even appeared in the playtest documents. Now they're enshrined in the official rules.

So what are the 4 spells and what makes them so irritating?

Hypnotic pattern

What makes it so annoying?

Hypnotic Pattern forces every creature in its area of effect to make a Wisdom save to avoid being incapacitated. Few monsters boast good Wisdom saves. With half or more of their foes incapacitated, a party can focus fire on the few that still pose a threat, picking off the outnumbered monsters. By the end of the encounter, player characters go from one beguiled victim to the next, raining attacks on the defenseless pinatas. As a DM, I may be biased, but I think the least fun scenes in the game come when PCs beat helpless foes to death.

Why did it work before?

Hypnotic Pattern started as the Illusionist class's answer to the Sleep spell. Like Sleep, an ally could break a victim's stupor. Like Sleep, Hypnotic Pattern only affected a limited number of total hit dice. The spell never proved more troublesome than Sleep.

Third edition tinkered with the spell a little. Victims could no longer be roused, but the caster needed to concentrate—and in 3E, concentration demanded a standard action.

Where does it go wrong?

The fifth-edition designers removed the hit-die limit. Perhaps someone decided on a simulationist approach: If everyone in an area sees the pattern, they all should save. Now every creature in the area of effect faced a Wisdom save to avoid becoming incapacitated. Few monsters boast good Wisdom saves. As with the original spell, allies or damage can rouse hypnotized creatures, but those allies face an entire party working to block them. The spell still requires concentration, but concentration in 5E costs no action.

How should it have worked?

The spell should have followed the pattern of Sleep and kept a hit-point limit.

Counterspell

What makes it so annoying?

Part of the fun of Dungeons & Dragons comes from casting imaginary spells to bring down terrible foes. Part of the game's challenge comes from facing evil wizards that rock the battle with spells. Counterspell drains the fun out of those confrontations. Instead of casting spells, you don't. Instead of battling against spell effects, nothing happens.

Meanwhile at the table, everyone gets mired in a rules dispute over whether the wizard who just had his spell countered can counter that Counterspell. (Yes, wizards casting a spell can counter the Counterspell that counters their spell.)

Why did it work before?

Up to fifth edition, D&D lacked a spell named Counterspell. Instead, Dispel Magic could counter spells. In the original Advanced Dungeons & Dragons rules, Dispel Magic can "counter the casting of spells in the area of effect." But the game offered no clue how countering would work in play. Rather than inventing rules for readied actions or reactions decades early, players did the sensible thing and ignored countering.

Third edition introduced the readied action—the foundation players needed to use Dispel Magic as a counterspell. To counter, spellcasters readied a counterspell action and watched for something to counter. If the round passed without anyone starting a spell worth blocking, you wasted an action. In practice, wizards never tried to counter. Better to just cast a spell of your own.

Where does it go wrong?

The counterspell function of Dispel Magic hardly fits the spell's disenchant role. By splitting Counterspell into a separate spell, the 5E designers let the spell work as a reaction. Instead of reading an action to counter, wizards could counter any time, even on their own turn, even as they cast another spell.

Countering spells turned from a process that demanded one or more standard actions, to something wizards could do without losing time for another spell.

For the first time ever, D&D introduced the Counterspell duel. Instead of doing something, dueling spell casters do nothing. Turns out nothing isn't much fun.

Sly Flourish worked to salvage some fun from Counterspell by adding colorful descriptions. He's still making chicken salad out of something other than chicken.

How should it have worked?

In 5E readying a spell such as Dispel Magic costs the spell slot even when the spell goes unused. If Counterspell were gone, and if Dispel Magic worked as it did in 3E, no one would counter spells. I think everyone would be content with that.

Banishment

What makes it so annoying?

The Banishment spell forces targets to make a Charisma save to avoid being sent to another plane.

Banishment lets players split combat scenes into two parts. In part one, the wizard or cleric banishes the toughest foes so their party can gang up on the outnumbered mooks in a one-sided romp. In the second part, the banished creatures spring back into reality and the party ambushes them. A potentially compelling fight turns into a rout followed by a dreary murder scene.

Once 7th-level players gain access to Banishment, it becomes a key factor in encounter design. If any monster enters the battle looking like a boss, he's sure to be banished. Every boss now needs one or more allies of similar power.

Why did it work before?

In The Dungeons & Dragons spells Gary Gygax never meant for players, I told of Gary's tendency to add every magical effect from fantasy to his game. This urge led him to include a spell that banished creatures to whatever hell they came from. Unearthed Arcana introduced the 7th-level spell Banishment along with a 4th-level version called Dissmissal. Because the spells only worked on visitors from another plane, they both rated as weak. Unlike Dismissal, Banishment capped the number of hit dice it could affect, but it offered ways to reduce the target's save. Banishment and Dismissal served a narrow use, so they seldom reached play.

Where does it go wrong?

Someone on the D&D design team must have fancied the notion of banishing enemies from the battlefield. They championed changes that turned Banishment from something no one ever casts into an inevitable opening move. Not only does the spell drop into Dismissal's 4th-level slot, but it also banishes natives from their own plane. I suppose the designer figured that if these banished creatures bounce back after a minute, then the spell would be balanced. Nope. The return just gives one-sided battles an ugly coda.

How should it have worked?

D&D thrived for 11 years without Banishment. The game would have thrived without it.

The 5E version of the spell might be fun if banished creatures returned in 1d8 rounds at a point of their choice within line of sight of their last location. This change would add enough uncertainty to avoid the pinata treatment.

Conjure Animals

What makes it so annoying?

Conjure Animals belongs to a class of annoying spells including Conjure Minor Elementals and Conjure Woodland Beings. The spells imply the caster gets to choose which creatures appear. This invited broken options. For example, conjuring 8 challenge rating 1/4 elk created an instant stampede. Eight challenge rating 1/4 pixies might cast at-will spells like Fly and Phantasmal Force for you.

In a clarification, designer Jeremy Crawford wrote that players only select the number of creatures to summon. The DM chooses the specific creatures, selecting creatures appropriate for the campaign and fun for the scene.

Nonetheless, as soon as Timmy summons 8 of anything, the game screeches to a halt. Suddenly Timmy manages his own actions and those of 8 proxies, taking more actions than the rest of the table combined.

Why did it work before?

Summoning spells came as a recent addition to the game. Originally, druids outdoors could call creatures from the wood, but then the Druid still had to make friends. None of this worked in a fight. At least the forest friends could tidy a cottage during the span of a musical number.

Third edition added actual summoning spells, but none created more than 1d4+1 creatures. Instead of 8 woodland friends, Timmy got about 3. Still, the problem of Timmy taking so much time on stage prompted the 4E designers to avoid summoning spells.

Where does it go wrong?

Somehow in the process of striking all traces of 4E from the D&D, the 5E designers forgot the problem of summoning spells.

How should it have worked?

Spells like Conjure Animals should never bring more than 4 creatures, and the options should favor single creatures.

Related: The 3 Most Annoying High-Level Spells in D&D

mcdonnellhiscambeste.blogspot.com

Source: https://dmdavid.com/tag/how-new-changes-created-the-4-most-annoying-spells-in-dungeons-dragons/

Share this post