From the WotC Boards: Mearls on 'Aggro'

I don't get it. The way "aggro" seems to work is exactly how every D&D game I've played has had monsters behave - They beat up whoever is doing the most damage to them (typically whomever hit them last, but not always), and if smart enough try to hurt the healer if he's healing people. That's how it's always been for me.

Is the complaint because aggro is forced/intrinsic, instead of just the DM choosing to run a monster like that? I haven't played any MMORPG, but I'm aware that there are set tactics that revolve around aggro.
 

log in or register to remove this ad


By the way, has anybody read that snippet on the paladin's "Divine Challenge" in the text:
mearls said:
However, his ability does not say that the monster must attack him. It makes it a better option, but doesn't eliminate other options.

Looks interesting - it seems "Divine Challenge" is more one of the lose-lose scenarios of the Bo9S crusader!

Cheers, LT.
 

Celebrim said:
Yes, apparantly they initially set out to make a video game. Gradually they are coming to thier senses. I hope it isn't too late.

Or they aren't so arrogant as to think that D&D couldn't possibly learn something from a game with almost 10 million active players. I wish the gamers on this forum would do the same.
 

wayne62682 said:
I don't get it. The way "aggro" seems to work is exactly how every D&D game I've played has had monsters behave - They beat up whoever is doing the most damage to them (typically whomever hit them last, but not always), and if smart enough try to hurt the healer if he's healing people. That's how it's always been for me.

Well, that is the issue with MMOs. The NPCs aren't smart enough, unless run by an actual person. So they have to be scripted. Which makes them predictable, unlike a GM controlled NPC.

wayne62682 said:
Is the complaint because aggro is forced/intrinsic, instead of just the DM choosing to run a monster like that? I haven't played any MMORPG, but I'm aware that there are set tactics that revolve around aggro.

I think that is the major gripe. If the GM WANTS the NPC to go after the Wizard, but the Paladin has an ability to force the NPC to attack him instead, apparently that is a bad thing.

Think of the reverse... You as a player want to go after an enemy Wizard, but his body guard has an ability to force you to attack him instead. Suddenly, you are no longer in control of your own choices. Might as well hand your character sheet to the GM and let him run the character...
 


Gloombunny said:
It's little dismaying to hear that they were actually trying out an aggro system at all, but they did finally scrap it, so that's good. Interesting that even the paladin's magic doesn't force someone to attack him. Sounds more like Iron Guard's Glare than knight's challenge.

My sentiments pretty much. Glad they were wise enough to get rid of this idea. Somewhat worried that they considered it seriously in the first place, but not too worried in any case.
 

Fifth Element said:
That's the negative interpretation. The fairer interpretation is that they were open-minded and willing to try out mechanics that work in another medium, to see if they work in D&D. Finding one that didn't, they dropped it.

Sure, it's a negative interpretaton. Doesn't mean it's not "fair," though. It's just more pessimistic.

My question is why would they even want to consider a mechanic that would take away so much choice in the game....
 
Last edited:

Whizbang Dustyboots said:
Inspiration comes from somewhere. No one sits around in a dark room, waiting for it to strike.

Well, other than Michael Keaton in Batman Returns, but that was silly.

Indeed.


Whizbang Dustyboots said:
*cough* inspired by Diablo *cough*

I thought it was more inspired by Fallout, but I may be mistaken.
 

Wolfspider said:
But why would they even want to consider a mechanic that would take away so much choice in the game?

*Simple*

Because the "bodyguard" role that I'd wager is one of the most common roles in fiction just DOES NOT WORK in D&D. Unless you are in a corridor with your charge behind you, there was nothing preventing the enemy from simply ignoring you (sure, in 3E, you eat an attack of opportunity but the tradeoff...in D&D before AoO? There's nothing for the enemy to worry about).

The thing is, in fiction, this doesn't happen. The enemy can't ignore the bodyguard due to the "one hit, you're dead" feature of most fiction.

The aggro mechanic was created to try and get this _COMMON_ role in fiction to actually work.
 

Remove ads

Top