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
*TTRPGs General
FFG Legendary Class contest submissions
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="Khur" data-source="post: 341185" data-attributes="member: 5583"><p><strong>More stuff....</strong></p><p></p><p>I think I'm alone now, but just in case I'm not</p><p></p><p>More editing points:</p><p></p><ul> <li data-xf-list-type="ul">Eliminate columns.<br /> <br /> Please use the "Game Rule Information" format from the PHB for the layout of class info. That is, the headings: Class Skills (without the space-wasting PHB Chapter 4 reference), Class Features: Armor and Weapon Proficiency (without the space-wasting armor penalty text), followed by a list of class features (gained simply by virtue of joining the class), and a list of "Legendary Class Title" Abilities. Alignment requirements (if any) should be listed among the requirements. Use Ex-"Legendary Class Title" to describe what happens when falling from the class.<br /> <br /> Place single spaces between sentences and punctuation. In proportional typography, double spaces become glaring gaps in text. Double spaces need only be used with fonts that have fixed character widths (like Courier). They're a holdover from the days when typewriters were used (typewriters having only fixed character widths).<br /> <br /> Format your text as Times New Roman (11 pt), flush left, ragged right. Inside of a single section, place no spaces after each paragraph, but indent all paragraphs after the first. The only exception is the "Quests" section in which you should place a single space between differing quests. Place no space between section headers and the text that follows them. Don't use bullets.<br /> <br /> Example:<br /> <br /> <span style="font-size: 9px"><strong>Quests</strong><br /> There is only one true quest involved in becoming a juxaspect. After the character first kills one of his alternate selves, he makes the decision to hunt down others. The second kill, assuming he has enough experience points to gain a level, propels him into his first level as a juxaspect.<br /> <br /> Continuing as a juxaspect in an ongoing quest, because each level the character takes in this legendary class must include experience gained from killing at least one alternate self. The character may not advance in level until an alternate self has been slain. Allies may aid the advancing juxaspect, but he must make the killing blow himself.<br /> <span style="color: red">(indent here)</span>The GM is encouraged to make tracking down alternate selves as difficult as she chooses. Just like the PC, these foes have friends, enemies, and items of power. Many will have taken juxaspect levels themselves, and thus be quite formidable opponents. Not all of these incarnations are of the same class, gender, or even race as the player's juxaspect.</span><br /> <br /> Avoid use of the word "will". <br /> Use this: "Characters travel in groups if they're wise.", instead of: "Characters will travel in groups if they're wise."<br /> <br /> Avoid noncommital words such as may, often, sometimes, and etc.</li> </ul><p>Two more edits:</p><p></p><p><a href="http://www.donkeyfeather.com/legendary/juxaspect_edit.doc" target="_blank">Juxaspect</a></p><p><a href="http://www.donkeyfeather.com/legendary/fmaster_edit.rtf" target="_blank">Forgemaster</a></p></blockquote><p></p>
[QUOTE="Khur, post: 341185, member: 5583"] [b]More stuff....[/b] I think I'm alone now, but just in case I'm not More editing points: [list]Eliminate columns. Please use the "Game Rule Information" format from the PHB for the layout of class info. That is, the headings: Class Skills (without the space-wasting PHB Chapter 4 reference), Class Features: Armor and Weapon Proficiency (without the space-wasting armor penalty text), followed by a list of class features (gained simply by virtue of joining the class), and a list of "Legendary Class Title" Abilities. Alignment requirements (if any) should be listed among the requirements. Use Ex-"Legendary Class Title" to describe what happens when falling from the class. Place single spaces between sentences and punctuation. In proportional typography, double spaces become glaring gaps in text. Double spaces need only be used with fonts that have fixed character widths (like Courier). They're a holdover from the days when typewriters were used (typewriters having only fixed character widths). Format your text as Times New Roman (11 pt), flush left, ragged right. Inside of a single section, place no spaces after each paragraph, but indent all paragraphs after the first. The only exception is the "Quests" section in which you should place a single space between differing quests. Place no space between section headers and the text that follows them. Don't use bullets. Example: [size=1][b]Quests[/b] There is only one true quest involved in becoming a juxaspect. After the character first kills one of his alternate selves, he makes the decision to hunt down others. The second kill, assuming he has enough experience points to gain a level, propels him into his first level as a juxaspect. Continuing as a juxaspect in an ongoing quest, because each level the character takes in this legendary class must include experience gained from killing at least one alternate self. The character may not advance in level until an alternate self has been slain. Allies may aid the advancing juxaspect, but he must make the killing blow himself. [COLOR=red](indent here)[/COLOR]The GM is encouraged to make tracking down alternate selves as difficult as she chooses. Just like the PC, these foes have friends, enemies, and items of power. Many will have taken juxaspect levels themselves, and thus be quite formidable opponents. Not all of these incarnations are of the same class, gender, or even race as the player's juxaspect.[/size] Avoid use of the word "will". Use this: "Characters travel in groups if they're wise.", instead of: "Characters will travel in groups if they're wise." Avoid noncommital words such as may, often, sometimes, and etc.[/list] Two more edits: [URL=http://www.donkeyfeather.com/legendary/juxaspect_edit.doc]Juxaspect[/URL] [URL=http://www.donkeyfeather.com/legendary/fmaster_edit.rtf]Forgemaster[/URL] [/QUOTE]
Insert quotes…
Verification
Post reply
Community
General Tabletop Discussion
*TTRPGs General
FFG Legendary Class contest submissions
Top