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
*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
*TTRPGs General
*Pathfinder & Starfinder
EN Publishing
*Geek Talk & Media
Search forums
Chat/Discord
Menu
Log in
Register
Install the app
Install
Community
General Tabletop Discussion
*Dungeons & Dragons
Put Some Sword World In Your D&D 1 - Basic Combat
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="Iosue" data-source="post: 9519562" data-attributes="member: 6680772"><p>A couple of years ago, I did a <a href="https://www.enworld.org/threads/lets-read-sword-world-2-5.691213/" target="_blank">Let's Read</a> of Sword World 2.5 (SW2.5), Japan's premier fantasy role-playing game. I thought it might be interesting to bring some of the ideas that I found interesting in SW2.5 as alternatives to "standard" 5e D&D (though I think any of these could be easily adapted to almost any edition of D&D).</p><p></p><p>For example, while not as reliant on a battle map as, say, 4th Edition, I would say that 5e still works <em>cleanest</em> on a battle map. While a DM could certain run it as theater-of-the-mind, as written this essentially means that the DM is still keeping track of where everyone is, distances, who's engaged with whom, and all that stuff. SW2.5's basic combat can help streamline that.</p><p></p><p>SW2.5's basic combat deals with three zones: the <strong>front line zone</strong>, the <strong>PCs' rearguard zone</strong>, and the <strong>enemies' rearguard zone</strong>. If characters from both sides share a zone, that zone becomes a <strong>melee zone</strong>. Practically, this means that most combats will have the melee combat characters fighting in the front line zone, while magical support and ranged combat characters stay in the rearguard zones. Once the front line zone has been cleared, then characters can proceed to the opposing rearguard zone.</p><p></p><p>For purposes of movement and ranged attacks, there are 30 feet between the zones. So one can move into an adjacent zone with a regular move, but moving from one rearguard zone to the other will require at least 60 feet of movement. Likewise, for ranged attacks, a range of 60 feet or more means one can attack the opposing rearguard zone, but a range of less than 60 feet can reach only an adjacent zone.</p><p></p><p><em>Optional rule:</em> In SW2.5, one needs the Targeting ability to shoot into a melee zone, and the Eagle Eye ability to shoot <strong>through</strong> a melee zone to the opposing rearguard zone. Otherwise, the target of the ranged attack is chosen randomly! For 5e, we could say that a character attacking with proficiency can choose their targets and attack the opposing rearguard, but if one is making a ranged attack without proficiency, then the target is chosen randomly.</p><p></p><p>Melee zones are "sticky;" once entered, they cannot be easily left. For 5e, that means if a character attempts to leave the melee zone , they provoke Opportunity Attacks. For a retreat to one's own rearguard zone*, there is one Opportunity Attack from a random enemy combatant. If a character is trying to push through to the opposing rearguard zone, then <em>every</em> enemy combatant gets an Opportunity Attack. The Disengage action cancels one Opportunity Attack.</p><p></p><p>And that's basically it. Initiative/turn order otherwise runs as per the written rules. The DM and players need only track which of the three zones any of the characters are in. The DM can track which enemy is engaged in melee with which PC, or for even less bookkeeping, they can determine enemy melee attacks randomly against any PC in the melee zone.</p></blockquote><p></p>
[QUOTE="Iosue, post: 9519562, member: 6680772"] A couple of years ago, I did a [URL='https://www.enworld.org/threads/lets-read-sword-world-2-5.691213/']Let's Read[/URL] of Sword World 2.5 (SW2.5), Japan's premier fantasy role-playing game. I thought it might be interesting to bring some of the ideas that I found interesting in SW2.5 as alternatives to "standard" 5e D&D (though I think any of these could be easily adapted to almost any edition of D&D). For example, while not as reliant on a battle map as, say, 4th Edition, I would say that 5e still works [I]cleanest[/I] on a battle map. While a DM could certain run it as theater-of-the-mind, as written this essentially means that the DM is still keeping track of where everyone is, distances, who's engaged with whom, and all that stuff. SW2.5's basic combat can help streamline that. SW2.5's basic combat deals with three zones: the [B]front line zone[/B], the [B]PCs' rearguard zone[/B], and the [B]enemies' rearguard zone[/B]. If characters from both sides share a zone, that zone becomes a [B]melee zone[/B]. Practically, this means that most combats will have the melee combat characters fighting in the front line zone, while magical support and ranged combat characters stay in the rearguard zones. Once the front line zone has been cleared, then characters can proceed to the opposing rearguard zone. For purposes of movement and ranged attacks, there are 30 feet between the zones. So one can move into an adjacent zone with a regular move, but moving from one rearguard zone to the other will require at least 60 feet of movement. Likewise, for ranged attacks, a range of 60 feet or more means one can attack the opposing rearguard zone, but a range of less than 60 feet can reach only an adjacent zone. [I]Optional rule:[/I] In SW2.5, one needs the Targeting ability to shoot into a melee zone, and the Eagle Eye ability to shoot [B]through[/B] a melee zone to the opposing rearguard zone. Otherwise, the target of the ranged attack is chosen randomly! For 5e, we could say that a character attacking with proficiency can choose their targets and attack the opposing rearguard, but if one is making a ranged attack without proficiency, then the target is chosen randomly. Melee zones are "sticky;" once entered, they cannot be easily left. For 5e, that means if a character attempts to leave the melee zone , they provoke Opportunity Attacks. For a retreat to one's own rearguard zone*, there is one Opportunity Attack from a random enemy combatant. If a character is trying to push through to the opposing rearguard zone, then [I]every[/I] enemy combatant gets an Opportunity Attack. The Disengage action cancels one Opportunity Attack. And that's basically it. Initiative/turn order otherwise runs as per the written rules. The DM and players need only track which of the three zones any of the characters are in. The DM can track which enemy is engaged in melee with which PC, or for even less bookkeeping, they can determine enemy melee attacks randomly against any PC in the melee zone. [/QUOTE]
Insert quotes…
Verification
Post reply
Community
General Tabletop Discussion
*Dungeons & Dragons
Put Some Sword World In Your D&D 1 - Basic Combat
Top