D&D (2024) Monster Manual 2025: Is Multiattack order prescriptive now?


log in or register to remove this ad

Sure, tight writing is how you get the current dual wielding rules, which allow dual wielding with a shield. Or how a guy carrying a torch isn't visible through darkness because darkness obscures vision. Or all the other instances, like this very thread, where we're left to divining tea leaves of what they really mean.
I didn’t say the rules are written tightly. I said it’s inaccurate to say that WotC doesn’t value tight writing.
The simplest answer is usually the right one. There are a bunch of different people working on different monsters/spells/rules/etc and they write abilities that are close enough to pass whoever is editing at that time, and here we are.
Yes, so like I said, there was no design architect and not enough development time.
I don't imagine too many believe Conjure Minor Elementals was rigorously playtested. Or haphazardly playtested!
Indeed. Shame there wasn’t more development time.
And I mean, it's basically fine. D&D mostly works with loose language because it's a bunch of DM's doing their own thing.
Oberoni fallacy.
 

Oberoni fallacy.

Wasn't there a post about this being a very strange "fallacy." We should remember that a fallacy requires a "mistaken belief" or a "failure in reasoning that renders an argument invalid"

Snarf had a wonderful write up on the issues with this "fallacy." I bolded the important part.

To quote Snarf:

The Oberoni Fallacy- There is no inconsistency/loophole/mechanics issue with Rule X, because you can always Rule 0 the inconsistency/loophole/mechanics issue.

This one is more difficult, and requires a little more unpacking. Let's start by simplifying it and rewording it. There is no PROBLEM with Rule X, because you can always FIX the PROBLEM.
All I've done is simplify the language regarding issues to "PROBLEM" and change Rule 0 to "FIX." Should be pretty uncontroversial. When you've done that, it becomes easier to see the actual issues with this so-called fallacy. First, people would have to agree that there is a problem- this is often the crux of most conversations, which is ignored. One person's problem isn't another person's. But let's assume there is agreement that there is a problem! So you can take the statement literally- "There was never any problem, because you can always fix the problem." Well, that's an absurd statement! "My car's bumper doesn't have a problem, because I duct taped it into place," doesn't mean that there was never a problem with bumper.

But let's turn this around a little; RPGs are, by their very nature, incomplete systems. To the extent that there is a Rule 0 (or similar mechanism for adjudication or modification), that is part of the rules, and changes made pursuant to it are also part of the rules. There will always be room for adjudication. And the norms and expectations in RPGs assume that people will continue to "make games their own," through modification, use of 3PP, and homebrew, or even the creation of their own systems. More simply, RPGs are not cars. When people are having a discussion, they are saying, quite simply, "I don't have an issue with Rule X, because I do this." So to tell them that there is a problem, one that they do not have, is also incorrect.

In more concrete terms for RPGs, we can look at how it applies in two different contexts-
A. Defining the problem. Take the martial/caster debate. PLEASE. Ahem. So, person A says that the martial/caster divide is a problem with 5e. However, that isn't something that is universally agreed-upon. Just because one person believes something to be "a problem" in the rules, doesn't make it so. If person B suggests a way to fix it for person A, then that still doesn't mean that this is "A PROBLEM," it just means that someone is suggesting a fix for person A.

B. Actual rules problems. In AD&D, the PHB stated that Monks attack as thieves. The DMG has them attack as Clerics. This is an actual rule problem- an inconsistency. While there is a "correct" answer (clerics, Sage Advice #31), saying that you could Rule 0 the correct answer doesn't actually get rid of the fact that there was a written issue in the rules.

Generally, though, the problem with this so-called fallacy is that people aren't discussing actual rules inconsistencies, so much as trying to shut down people who are offering their advice with dealing with specific issues. On a higher level, the Oberoni Fallacy isn't a fallacy, it's simply a statement as to the philosophical approach one takes to gaming; one might as well say, to coin a phrase, "Rules, not rulings."

You are dismissing an argument for a difference in philosophy, not because of an actual fallacy.

Source: Fallacious Follies: Oberoni, Stormwind, and Fallacies OH MY!
 
Last edited:

In previous editions, creatures had attack routines stated because that was how they usually attacked. With animals, they rely largely on instinct, so in ordinary situations, they will attack prey in a fairly predictable manner. Creatures like the Roper, or Dragons, who have different reaches with different attacks probably use them in a similar manner as well. When I see a Multiattack that says "do this, then that", I see that more as advice to a DM to give them an idea of how the creature is intended to work, not a strict "it must attack in this way".

For example, few, if any, monsters tell us which attack they use to make opportunity attacks with. Normally they would use the attack with the most reach or damage, but there might be reasons to do otherwise. And if so, there's no reason to say "nope nope, rules don't let you"- I mean, players can generally make their attacks in any order they wish with the Attack action, after all. It's bonus and reaction attacks that usually have qualifiers, if at all.

Now if there is a RAW here, and some creatures are in fact, always expected to attack in the same way every time, like automatons, and they aren't golems or zombies, I can't imagine any DM who wouldn't just ignore that if it didn't make sense to them, so I'm not entirely sure what the debate here is, unless this is just some mental exercise (at which point, carry on, don't mind me!). But I don't believe that there is any real RAW.

After all, then you get questions of "well, if the monster is somehow affected by Haste, which of it's attacks will it use?" lol.

Also! I've noticed some of the new monsters have become very simple with their attacks. The Ancient Green Dragon, at least in the preview I saw, doesn't even bother to have different attacks. It has instead of claws/bite/wing/tail just a generic "Rend" and it's Multiattack lets it Rend thrice, or replace one Rend with a special attack (a spell as I recall). So in some cases, it's kind of moot.

-As an aside, I don't like this approach. I'm not usually a big stickler for verisimilitude, but "Rend" makes me think of a claw attack or something, not a bite or tail slap. Yet "Rend" has a 15' reach, where traditionally, dragons have variable reach based on their body configuration. Probably not relevant to this discussion, but it does strike me as kind of weird.
 

... so I'm not entirely sure what the debate here is, unless this is just some mental exercise (at which point, carry on, don't mind me!). But I don't believe that there is any real RAW.
The OP is the author of the Monsters Know What They're Doing series, so I'm guessing he's worried about giving his customers the "wrong" advice.
 

Wasn't there a post about this being a very strange "fallacy." We should remember that a fallacy requires a "mistaken belief" or a "failure in reasoning that renders an argument invalid"

Snarf had a wonderful write up on the issues with this "fallacy." I bolded the important part.

To quote Snarf:

You are dismissing an argument for a difference in philosophy, not because of an actual fallacy.

Source: Fallacious Follies: Oberoni, Stormwind, and Fallacies OH MY!
🤷‍♀️ whatever wording you want to use for it “the rules aren’t broken because you can fix them” is a bad argument.
 



The point was that it's a difference of opinion, and not a fallacy. If we agree on that, I have nothing more to add to the discussion.
Again, I'm not too fussed what we refer to it as. My point is, @Jefe Bergenstein and I seem to agree that the rules are written loosely and inconsistently, and I don't think "it's not a problem because DMs are going to do what they want with it anyway" is a compelling argument. It is definitely a problem.
 

The rules here aren’t broken though. They are perfectly understandable.

If the rules don’t say X happens, then it doesn’t happen. That’s the general rule in WotC DnD and has been since 3e. That’s why electrical attacks work on flying creatures and underwater.

Do the rules say the order is proscriptive? No? Then they aren’t. End of story.
 

Remove ads

Top