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
GSL questions for Scott Rouse and Mike Lescault
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="Orcus" data-source="post: 4135953" data-attributes="member: 1254"><p>There are four options:</p><p></p><p><strong>A. Close 4E.</strong> Nothing more to discuss.</p><p></p><p><strong>B. Use the OGL.</strong> That's easy. Just create the 4E SRD and say "this is released as open game content". Then let us use it under the license.</p><p></p><p><strong>C. License the PI and work those restrictions from the old STL back in.</strong></p><p></p><p>This would be really really easy. </p><p></p><p>1. Designate ALL of the 4E core books and their contents as PI and require us to agree not to challenge or dispute said designation or to challenge ownership.</p><p></p><p>2. Then, give the publishers permission per OGL section 7 to use that PI under the OGL v1.0a subject to certain conditions--namely, that they follow some of the conditions from the STL/Guide:</p><p></p><p>a. no describing character creation,</p><p>b. no describing applying XP to a charcter</p><p>c. no interactive games</p><p>d. no minis</p><p>e. no using "core rules"</p><p>f. must meet community standards of decency, such as nudity, race and religion as found in the STL.</p><p></p><p>(you know, all the terms people got around by just going OGL and not using the d20 license because the d20 logo became meaningless).</p><p></p><p>3. Permit publishers to say "For use with Dungeons and Dragons, Fourth Edition, published by Wizards of the Coast" on their products.</p><p></p><p>4. Provide some version of the D&D logo, similar to the one on the back of the "Wizards Presents..." books for our use. </p><p></p><p>5. Let us refer to the name of the book and page numbers for goodness sake!</p><p></p><p>6. Require us to say "This product uses content from the Fourth Edition Dungeons and Dragons game, published by Wizards of the Coast, Inc. All such content is Product Identity and is used with permission and by seperate agreement. No such content is Open Game Content."</p><p></p><p>Then create a smart SRD. Dont just retype all the stuff. All that does is slow the SRD down and prevents us from supporting their future releases. Instead, for each product, simply do a Section 15 listing like what we would for an OGL product telling us how you want us to reference that book, with a provision that we have to say the blurb above. And as each book comes out, update the smart SRD with the title of the book and add it to the PI permission document. </p><p></p><p>Its real easy to license this stuff and keep all the restrictions Wizards is likely concerned about. </p><p></p><p><strong>D. Create a brand new license called the GSL.</strong></p><p></p><p>This is something that could be made from scratch. So its biggest benefit is that new people who didnt do the OGL can say, "yeah, I made that." I have no idea what the issues are. But the downside is that we have been working with the OGL for about 8 years now. We know what can and cant be done. We know how to use it. I'm not sure creating a brand new license is needed when you can simply use <strong>C</strong>, above. </p><p></p><p><strong>My Opinion</strong></p><p></p><p>I think C is the best choice. It continues open gaming. It continues a license we all know how to work with. It works back in the restrictions that Wizards wanted in the license in the first place with the d2) STL. It ties the license back to D&D, which is really what Wizards wants to do--sell D&D books. It precents stand alone competing game systems like M&M, which arguably dont add as much to Wizards' percieved value of open gaming as do, say, products that straight support D&D. It protects their content by making it all PI which is impregnable in the OGL and, frankly, PI is protected even more solidly that regular copyright and it requires us not to challenge ownership.</p></blockquote><p></p>
[QUOTE="Orcus, post: 4135953, member: 1254"] There are four options: [B]A. Close 4E.[/B] Nothing more to discuss. [B]B. Use the OGL.[/B] That's easy. Just create the 4E SRD and say "this is released as open game content". Then let us use it under the license. [B]C. License the PI and work those restrictions from the old STL back in.[/B] This would be really really easy. 1. Designate ALL of the 4E core books and their contents as PI and require us to agree not to challenge or dispute said designation or to challenge ownership. 2. Then, give the publishers permission per OGL section 7 to use that PI under the OGL v1.0a subject to certain conditions--namely, that they follow some of the conditions from the STL/Guide: a. no describing character creation, b. no describing applying XP to a charcter c. no interactive games d. no minis e. no using "core rules" f. must meet community standards of decency, such as nudity, race and religion as found in the STL. (you know, all the terms people got around by just going OGL and not using the d20 license because the d20 logo became meaningless). 3. Permit publishers to say "For use with Dungeons and Dragons, Fourth Edition, published by Wizards of the Coast" on their products. 4. Provide some version of the D&D logo, similar to the one on the back of the "Wizards Presents..." books for our use. 5. Let us refer to the name of the book and page numbers for goodness sake! 6. Require us to say "This product uses content from the Fourth Edition Dungeons and Dragons game, published by Wizards of the Coast, Inc. All such content is Product Identity and is used with permission and by seperate agreement. No such content is Open Game Content." Then create a smart SRD. Dont just retype all the stuff. All that does is slow the SRD down and prevents us from supporting their future releases. Instead, for each product, simply do a Section 15 listing like what we would for an OGL product telling us how you want us to reference that book, with a provision that we have to say the blurb above. And as each book comes out, update the smart SRD with the title of the book and add it to the PI permission document. Its real easy to license this stuff and keep all the restrictions Wizards is likely concerned about. [B]D. Create a brand new license called the GSL.[/B] This is something that could be made from scratch. So its biggest benefit is that new people who didnt do the OGL can say, "yeah, I made that." I have no idea what the issues are. But the downside is that we have been working with the OGL for about 8 years now. We know what can and cant be done. We know how to use it. I'm not sure creating a brand new license is needed when you can simply use [B]C[/B], above. [B]My Opinion[/B] I think C is the best choice. It continues open gaming. It continues a license we all know how to work with. It works back in the restrictions that Wizards wanted in the license in the first place with the d2) STL. It ties the license back to D&D, which is really what Wizards wants to do--sell D&D books. It precents stand alone competing game systems like M&M, which arguably dont add as much to Wizards' percieved value of open gaming as do, say, products that straight support D&D. It protects their content by making it all PI which is impregnable in the OGL and, frankly, PI is protected even more solidly that regular copyright and it requires us not to challenge ownership. [/QUOTE]
Insert quotes…
Verification
Post reply
Community
General Tabletop Discussion
*TTRPGs General
GSL questions for Scott Rouse and Mike Lescault
Top