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.
Community
General Tabletop Discussion
D&D Older Editions, OSR, & D&D Variants
Converting Old 3E to New 3E standard problems
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="Celebrim" data-source="post: 385925" data-attributes="member: 4937"><p>So, can I get some opinions on what is acceptable? Which of the following is legal and appropriate, if any? Ideas are offered in order of what I would think is least problamatic.</p><p></p><p>Version 1)</p><p></p><p>a) An encounter key (ex. 61.)</p><p></p><p>b) A stat block of the bare encounter with as few amendments as is possible.</p><p></p><p>c) A clearly labeled conversion note with a suggestion and explanation for achieving some goal of play balance.</p><p></p><p>Version 2) </p><p></p><p>As above except that certain mechanics are replaced by some non-equivalent mechanic where in D20 it would now be standard to use the latter mechanic for the situation in question. This most likely would occur in converting traps, since 1st edition had no standard for avoiding traps and each trap used a mechanic of its own. For example, a reflex save is now standard for avoiding pit traps, but 1st edition designers would have varied between dex checks, random luck, and saves vs. paralyzation if they provided any means of avoidance at all. I could retain any of the three mechanics in a conversion, but I'd like to prefer D20's default mechanic of a reflex save.</p><p></p><p>Version 3)</p><p></p><p>As any of the above but follows with section d.</p><p></p><p>d) A stat block for the suggested modified encounter when the suggestion differs by something other than number of opponents or other trivial matter. For example, if original encounter involves 16th level cleric, then as a suggestion a stat block for the same cleric at 12th level is provided. (I haven't converted the module, and am not going to and I don't think it is an ESD, but merely as an example, Arakis from DL was a 33rd level character in 1st edition)</p><p></p><p>Version 4)</p><p></p><p>As any of the above, except that the goal in providing suggestions is capturing some element of 'flavor' which is missing from a straight conversion and not merely play balance. For instance, you might do this if some mechanic has changed vastly from 1st to 3rd edition - ei poison, mechanics of certain spell effects, class abilities, humans types no longer as monster entries, feral humanoids with class levels, prestige classes, etc. </p><p></p><p>Version 5)</p><p></p><p>As any of above, but d and c are offered in a separate companion 'Play Notes' file, in which it is stated that this is the stats I used when running the module in D20 (or intend to) use and why.</p></blockquote><p></p>
[QUOTE="Celebrim, post: 385925, member: 4937"] So, can I get some opinions on what is acceptable? Which of the following is legal and appropriate, if any? Ideas are offered in order of what I would think is least problamatic. Version 1) a) An encounter key (ex. 61.) b) A stat block of the bare encounter with as few amendments as is possible. c) A clearly labeled conversion note with a suggestion and explanation for achieving some goal of play balance. Version 2) As above except that certain mechanics are replaced by some non-equivalent mechanic where in D20 it would now be standard to use the latter mechanic for the situation in question. This most likely would occur in converting traps, since 1st edition had no standard for avoiding traps and each trap used a mechanic of its own. For example, a reflex save is now standard for avoiding pit traps, but 1st edition designers would have varied between dex checks, random luck, and saves vs. paralyzation if they provided any means of avoidance at all. I could retain any of the three mechanics in a conversion, but I'd like to prefer D20's default mechanic of a reflex save. Version 3) As any of the above but follows with section d. d) A stat block for the suggested modified encounter when the suggestion differs by something other than number of opponents or other trivial matter. For example, if original encounter involves 16th level cleric, then as a suggestion a stat block for the same cleric at 12th level is provided. (I haven't converted the module, and am not going to and I don't think it is an ESD, but merely as an example, Arakis from DL was a 33rd level character in 1st edition) Version 4) As any of the above, except that the goal in providing suggestions is capturing some element of 'flavor' which is missing from a straight conversion and not merely play balance. For instance, you might do this if some mechanic has changed vastly from 1st to 3rd edition - ei poison, mechanics of certain spell effects, class abilities, humans types no longer as monster entries, feral humanoids with class levels, prestige classes, etc. Version 5) As any of above, but d and c are offered in a separate companion 'Play Notes' file, in which it is stated that this is the stats I used when running the module in D20 (or intend to) use and why. [/QUOTE]
Insert quotes…
Verification
Post reply
Community
General Tabletop Discussion
D&D Older Editions, OSR, & D&D Variants
Converting Old 3E to New 3E standard problems
Top