Menu
News
All News
Dungeons & Dragons
Level Up: Advanced 5th Edition
Pathfinder
Starfinder
Warhammer
2d20 System
Year Zero Engine
Industry News
Reviews
Dragon Reflections
White Dwarf Reflections
Columns
Weekly Digests
Weekly News Digest
Freebies, Sales & Bundles
RPG Print News
RPG Crowdfunding News
Game Content
ENterplanetary DimENsions
Mythological Figures
Opinion
Worlds of Design
Peregrine's Nest
RPG Evolution
Other Columns
From the Freelancing Frontline
Monster ENcyclopedia
WotC/TSR Alumni Look Back
4 Hours w/RSD (Ryan Dancey)
The Road to 3E (Jonathan Tweet)
Greenwood's Realms (Ed Greenwood)
Drawmij's TSR (Jim Ward)
Community
Forums & Topics
Forum List
Latest Posts
Forum list
*Dungeons & Dragons
Level Up: Advanced 5th Edition
D&D Older Editions, OSR, & D&D Variants
*TTRPGs General
*Pathfinder & Starfinder
EN Publishing
*Geek Talk & Media
Search forums
Chat/Discord
Resources
Wiki
Pages
Latest activity
Media
New media
New comments
Search media
Downloads
Latest reviews
Search resources
EN Publishing
Store
EN5ider
Adventures in ZEITGEIST
Awfully Cheerful Engine
What's OLD is NEW
Judge Dredd & The Worlds Of 2000AD
War of the Burning Sky
Level Up: Advanced 5E
Events & Releases
Upcoming Events
Private Events
Featured Events
Socials!
EN Publishing
Twitter
BlueSky
Facebook
Instagram
EN World
BlueSky
YouTube
Facebook
Twitter
Twitch
Podcast
Features
Top 5 RPGs Compiled Charts 2004-Present
Adventure Game Industry Market Research Summary (RPGs) V1.0
Ryan Dancey: Acquiring TSR
Q&A With Gary Gygax
D&D Rules FAQs
TSR, WotC, & Paizo: A Comparative History
D&D Pronunciation Guide
Million Dollar TTRPG Kickstarters
Tabletop RPG Podcast Hall of Fame
Eric Noah's Unofficial D&D 3rd Edition News
D&D in the Mainstream
D&D & RPG History
About Morrus
Log in
Register
What's new
Search
Search
Search titles only
By:
Forums & Topics
Forum List
Latest Posts
Forum list
*Dungeons & Dragons
Level Up: Advanced 5th Edition
D&D Older Editions, OSR, & D&D Variants
*TTRPGs General
*Pathfinder & Starfinder
EN Publishing
*Geek Talk & Media
Search forums
Chat/Discord
Menu
Log in
Register
Install the app
Install
Upgrade your account to a Community Supporter account and remove most of the site ads.
Rocket your D&D 5E and Level Up: Advanced 5E games into space! Alpha Star Magazine Is Launching... Right Now!
Community
General Tabletop Discussion
*Dungeons & Dragons
Spear houserule
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="Sword of Spirit" data-source="post: 8364279" data-attributes="member: 6677017"><p>While doing research for the mass combat rules I may or may not end up successfully creating, I kept running into something that has always bugged me about the 5e weapons: the spear.</p><p></p><p>To start, we have a javelin, a spear, and a pike in the rules to represent the three real-world categories of spear-like weapons. So far, so good.</p><p></p><p>The spear is a cheap simple weapon, as it should be. The problem is that, more than most other simple weapons, it is a weapon that is also used as a primary weapon by more skilled warriors and trained armies. Mechanically, it isn't on par with martial weapons, and it's a bad choice you probably aren't going to take for a PC. And when I look at the <strong>guard</strong> NPC statblock with its pitiful spear, I just feel bad.</p><p></p><p>In addition, there are conceptual issues because an essential part of the historical spear was its reach. Based on my cursory research, real spears were of similar length to glaives and halberds, which do have reach in 5e. But the spear doesn't, for some weird reason. While this is just an annoyance at the normal D&D scale, when you start messing with mass combat considerations, <em>spears don't work</em>. They need to both be usable in one-hand and have reach so they can be used for the actual spear and shield tactics that people used spears for.</p><p></p><p>But I found something interesting in my research. Apparently there are supposed to be two types of (sub-pike) spears. Thrusting and throwing. Javelins are for throwing, and thrusting spears <em>aren't</em>.</p><p></p><p>. . .</p><p></p><p>That was the revelation. What's holding back the spear is that it's being given the Thrown property unnecessarily. Sure, if you throw it it might fly better than if you throw a flail or scimitar, but so would a shortsword and that doesn't have the Thrown property. The thing is that you <em>don't</em> throw your thrusting spear except in extreme situations, because then you don't have it anymore. If you want to throw spears, that's what javelins are for. Carry 7 of them like the Romans.</p><p></p><p>So here is the spear houserule: <strong>Remove the Thrown property; add the Reach property.</strong> Everything else stays the same.</p><p></p><p>Conceptually this puts spears in their correct place on the javelin-spear-pike continuum.</p><p></p><p>Javelins can be used in melee, but are designed for throwing. (1d6 damage, ranged or melee)</p><p></p><p>Spears are designed for thrusting, have reach, and can be used either one-handed with a shield or two-handed. (1d6 damage melee reach with shield, or 1d8 damage melee reach two-handed)</p><p></p><p>Pikes are too big for one-handed use (and obviously have reach). (1d10 damage melee reach two-handed)</p><p></p><p>Mechanically, they now have a meaningful niche and are still balanced properly with other weapons. PCs and NPCs alike have a reason to choose a spear either at the personal or mass combat scale. This does put them on par with martial weapons, but I'm probably okay with that. Spears have been one of the most popular weapons in history, and this rule makes that hold up.</p><p></p><p>I'm hoping it works out the way I like. If everyone gives up on longswords and battleaxes and converts to spears, then I've screwed up. Otherwise, I think this should fix it.</p><p></p><p>EDIT: After following the discussion and putting a lot of thought into it, I decided a better solution was to make a martial warspear with the stats of a war pick, give it to guards, and treat phalanx reach situations as a facet of mass combat rules rather than standard D&D combat.</p></blockquote><p></p>
[QUOTE="Sword of Spirit, post: 8364279, member: 6677017"] While doing research for the mass combat rules I may or may not end up successfully creating, I kept running into something that has always bugged me about the 5e weapons: the spear. To start, we have a javelin, a spear, and a pike in the rules to represent the three real-world categories of spear-like weapons. So far, so good. The spear is a cheap simple weapon, as it should be. The problem is that, more than most other simple weapons, it is a weapon that is also used as a primary weapon by more skilled warriors and trained armies. Mechanically, it isn't on par with martial weapons, and it's a bad choice you probably aren't going to take for a PC. And when I look at the [B]guard[/B] NPC statblock with its pitiful spear, I just feel bad. In addition, there are conceptual issues because an essential part of the historical spear was its reach. Based on my cursory research, real spears were of similar length to glaives and halberds, which do have reach in 5e. But the spear doesn't, for some weird reason. While this is just an annoyance at the normal D&D scale, when you start messing with mass combat considerations, [I]spears don't work[/I]. They need to both be usable in one-hand and have reach so they can be used for the actual spear and shield tactics that people used spears for. But I found something interesting in my research. Apparently there are supposed to be two types of (sub-pike) spears. Thrusting and throwing. Javelins are for throwing, and thrusting spears [I]aren't[/I]. . . . That was the revelation. What's holding back the spear is that it's being given the Thrown property unnecessarily. Sure, if you throw it it might fly better than if you throw a flail or scimitar, but so would a shortsword and that doesn't have the Thrown property. The thing is that you [I]don't[/I] throw your thrusting spear except in extreme situations, because then you don't have it anymore. If you want to throw spears, that's what javelins are for. Carry 7 of them like the Romans. So here is the spear houserule: [B]Remove the Thrown property; add the Reach property.[/B] Everything else stays the same. Conceptually this puts spears in their correct place on the javelin-spear-pike continuum. Javelins can be used in melee, but are designed for throwing. (1d6 damage, ranged or melee) Spears are designed for thrusting, have reach, and can be used either one-handed with a shield or two-handed. (1d6 damage melee reach with shield, or 1d8 damage melee reach two-handed) Pikes are too big for one-handed use (and obviously have reach). (1d10 damage melee reach two-handed) Mechanically, they now have a meaningful niche and are still balanced properly with other weapons. PCs and NPCs alike have a reason to choose a spear either at the personal or mass combat scale. This does put them on par with martial weapons, but I'm probably okay with that. Spears have been one of the most popular weapons in history, and this rule makes that hold up. I'm hoping it works out the way I like. If everyone gives up on longswords and battleaxes and converts to spears, then I've screwed up. Otherwise, I think this should fix it. EDIT: After following the discussion and putting a lot of thought into it, I decided a better solution was to make a martial warspear with the stats of a war pick, give it to guards, and treat phalanx reach situations as a facet of mass combat rules rather than standard D&D combat. [/QUOTE]
Insert quotes…
Verification
Post reply
Community
General Tabletop Discussion
*Dungeons & Dragons
Spear houserule
Top