Prone in D&D 5e: Why 'Melee vs. Ranged' Isn't the Actual Rule

The fighter shoves the ogre down, the rogue steps in for the kill, and the table already knows what's coming: advantage, because it's a melee attack against a downed target. Across the room, the ranger's player pulls out a bow and asks if they get disadvantage since they're shooting instead of swinging. Most tables answer yes, on reflex, because that's the rule everyone learned: melee gets advantage, ranged gets disadvantage.

It's not the rule. It's a coincidence that happens to be right most of the time, which is exactly what makes it dangerous the moment a reach weapon or a close-range shot shows up.

The Actual Prone 5e Rule Is About Distance, Not Weapon Type

Here's what the rule actually says, with nothing simplified out of it: an attack roll against a creature in this condition has advantage if the attacker is within 5 feet of it. Otherwise, the attack roll has disadvantage. That's the whole mechanic, and it says nothing about melee or ranged weapons anywhere in the text.

The downed creature's own attacks work differently. Being on the ground imposes disadvantage on every attack roll it makes, no matter what weapon it's holding or how close the target is. That half of the rule genuinely doesn't care about distance, which is part of why the "melee vs. ranged" shorthand feels so intuitive from the other side of the exchange.

Most of the time, this distance rule and the melee/ranged shorthand land on the same answer. Melee attackers are usually standing within 5 feet of their target, so they usually get advantage. Ranged attackers are usually shooting from farther away, so they usually get disadvantage. The shorthand isn't wrong often enough for anyone to notice, which is exactly why it survives at table after table. It just isn't the actual mechanism producing the result.

Where the Shorthand Breaks: Reach Weapons

The first crack shows up with reach. A glaive, halberd, or whip-wielding character threatens 10 feet instead of 5, and a fighter with one of those weapons can absolutely make a melee attack against a downed enemy from 10 feet away.

This isn't an edge case invented for a rules article. Reach weapons exist specifically so a character can attack without closing to melee range, and knocking something down is a common enough combo with a Polearm Master build or a battlemaster's Trip Attack that the interaction comes up regularly at tables running either.

Where the Shorthand Breaks: Close-Range Ranged Attacks

The second crack runs the other direction, and it's the one that trips up even players who already know the distance rule. A separate, unrelated rule says a ranged weapon attack has disadvantage if the attacker is within 5 feet of a hostile creature that can see them and isn't incapacitated. That's the rule that punishes archers for staying in melee range instead of falling back.

Now put both rules on the same roll. An archer standing 5 feet from a downed enemy gets advantage from the condition, because they're within 5 feet, and disadvantage from the close-range ranged rule, because they're within 5 feet of a hostile creature with a bow in hand. Those aren't two reasons stacking on the same side. They're one of each, and advantage and disadvantage never partially cancel: any advantage plus any disadvantage is a flat roll, full stop.

So a ranged attack against a target 5 feet away who's on the ground isn't advantage, and it isn't disadvantage either. It's a plain d20, no bonus dice in either direction. A lot of tables that know the distance rule still get this exact scenario backward, assuming the archer eats disadvantage twice or that the ground-level advantage wins the argument, when the honest answer is that the two effects erase each other completely.

Standing Up Costs More Than People Remember

The other half of the condition that gets missed under time pressure: getting up isn't free, and it isn't a bonus action or a reaction. Standing up costs an amount of movement equal to half your speed. For a character with a standard 30-foot speed, that's 15 feet gone before they've taken a single step toward anything else. A creature with 0 speed, whether from a spell, an injury, or a heavy load past its carrying capacity, can't stand up at all until that's resolved.

That matters tactically in ways that get glossed over in the heat of a round. A rogue who was just shoved down and wants to stand and still close the distance to attack might not have enough movement left to do both after paying the standing-up tax. Choosing to crawl instead of standing pays double for every foot of movement on top of that, which is almost always worse than just eating the disadvantage on the next attack and standing up properly.

What Actually Knocks Someone Prone

The Shove action is the default way to force this condition onto a target: as part of the Attack action, a creature can replace one of its attacks with an Athletics check contested by the target's Athletics or Acrobatics, either shoving them 5 feet away or knocking them to the ground. It's an option every character has access to, not a class feature, which is why it shows up in nearly every campaign sooner or later.

Beyond Shove, plenty of class features and spells knock targets down directly: a battlemaster fighter's Trip Attack maneuver, a Grease or Grasping Vine spell, and a long list of monster abilities that state it outright in their stat block. None of those alternate sources change how the condition itself works once it lands. A creature knocked down by a spell resolves attacks against it exactly the same way as one shoved down by a fighter.

Did the 2024 Rules Change Prone?

No. Of the fifteen conditions in the game, only a handful got real mechanical rewrites in the 2024 Player's Handbook, exhaustion moved from a stacking penalty table to a flat cumulative modifier, grappled and incapacitated both picked up clarified edge cases, and the condition covered here wasn't one of them. The advantage-within-5-feet, disadvantage-beyond-5-feet split, along with the always-disadvantage penalty on the downed creature's own attacks, reads the same in the 2024 core rules as it did in 2014.

What did change is presentation, not mechanics: the 2024 rulebook folded every condition into a single glossary appendix that every spell, feature, and monster stat block now points back to, instead of scattering slightly different phrasings across multiple books the way 2014-era sourcebooks sometimes did. That consistency is genuinely useful. It just isn't a rules change, and a table that already had this one right under the 2014 books doesn't need to relearn anything under the new ones.

Why This Keeps Coming Up at the Table

The condition touches two of the most common actions in 5e combat, attacking and moving, which means it comes up in nearly every fight that lasts more than a round or two. Add a reach weapon to one side of the table or a ranged character who likes to fight up close, and the melee/ranged shorthand stops being close enough and starts producing the wrong answer at the exact moment it matters most, usually mid-combat with everyone waiting on the ruling.

Rogues run into a version of this constantly. A player angling for Sneak Attack will often shove a target down first specifically to guarantee the melee advantage that triggers it, then get confused when the same rogue's own ranged attack from across the room, against the very target they just knocked down, doesn't carry the same bonus. It's the identical distance rule producing two different answers depending on where the rogue is actually standing, not a special case for Sneak Attack at all.

This is the same category of problem that runs through flanking, opportunity attacks, and cover: a rule that's genuinely simple once written out correctly, but that gets compressed into a slightly-wrong shorthand because the shorthand is faster to say out loud than "check the distance." The shorthand works until the one turn it doesn't, and there's rarely a rulebook open at that exact moment to settle it.

An AI Game Master doesn't have that problem, because it isn't reaching for a shorthand in the first place. StoryRoll's narration tracks the actual distance between a downed target and whoever's attacking it, applies advantage or disadvantage off that distance rather than off weapon type, and layers in the separate close-range ranged penalty when it actually applies, resolving the whole stack the same way whether it's a straightforward melee follow-up or the reach-weapon and point-blank-archer cases that usually need a rulebook check. Knocking someone down stays a real tactical choice with real consequences either way, worth setting up on purpose with a Shove or a battlemaster maneuver. What disappears is the argument over which shorthand was supposed to apply this time.

Frequently Asked Questions

Does prone give advantage to melee attacks and disadvantage to ranged attacks in 5e?

That's the common shorthand, but it's not the actual rule. Prone 5e is distance-based: any attack against a prone creature has advantage if the attacker is within 5 feet, and disadvantage otherwise, regardless of whether the attack is melee or ranged.

What happens if a melee attacker uses a reach weapon against a prone target from 10 feet away?

The attack has disadvantage. Reach only changes how far a melee weapon can hit, not the prone rule's 5-foot threshold. A reach weapon attacking a prone creature from 10 feet away is still farther than 5 feet, so it gets disadvantage exactly like a ranged attack would.

Does a ranged attack against a prone target within 5 feet get advantage?

The prone rule alone grants advantage at that range, but a separate rule imposes disadvantage on ranged attacks made within 5 feet of a hostile creature that can see you and isn't incapacitated. Those two effects cancel out, so the net result is a flat roll, not advantage.

How much movement does it cost to stand up from prone in 5e?

Standing up costs an amount of movement equal to half your speed. A creature with a 30-foot speed uses 15 feet of movement to stand, and can't stand at all if it doesn't have that much movement left or if its speed is reduced to 0.

What can knock a creature prone in D&D 5e?

The Shove action (an Athletics check contested by the target's Athletics or Acrobatics) is the most common way, but several spells and monster abilities also knock targets prone directly, including Trip Attack-style features, Grease, and any effect that explicitly says so.