D&D Will Move To a Creative Commons License, Requests Feedback On a New OGL
“We’re giving the core D&D mechanics to the community through a Creative Commons license, which means that they are fully in your hands,” Brink said in the blog post. “If you want to use quintessentially D&D content from the SRD such as owlbears and magic missile, OGL 1.2 will provide you a perpetual, irrevocable license to do so.” So much trust has been lost over the last several weeks that it will no doubt take a while for legal experts — armchair and otherwise — to pour over the details of the new OGL. These are the bullet points that Wizards is promoting in this official statement: – Protecting D&D’s inclusive play experience. As I said above, content more clearly associated with D&D (like the classes, spells, and monsters) is what falls under the OGL. You’ll see that OGL 1.2 lets us act when offensive or hurtful content is published using the covered D&D stuff. We want an inclusive, safe play experience for everyone. This is deeply important to us, and OGL 1.0a didn’t give us any ability to ensure it
– TTRPGs and VTTs. OGL 1.2 will only apply to TTRPG content, whether published as books, as electronic publications, or on virtual tabletops (VTTs). Nobody needs to wonder or worry if it applies to anything else. It doesn’t.
– Deauthorizing OGL 1.0a. We know this is a big concern. The Creative Commons license and the open terms of 1.2 are intended to help with that. One key reason why we have to deauthorize: We can’t use the protective options in 1.2 if someone can just choose to publish harmful, discriminatory, or illegal content under 1.0a. And again, any content you have already published under OGL 1.0a will still always be licensed under OGL 1.0a.
– Very limited license changes allowed. Only two sections can be changed once OGL 1.2 is live: how you cite Wizards in your work and how we can contact each other. We don’t know what the future holds or what technologies we will use to communicate with each other, so we thought these two sections needed to be future-proofed. A revised version of this draft will be presented to the community again “on or before February 17.”
“The process will extend as long as it needs to,” Brink said. “We’ll keep iterating and getting your feedback until we get it right.”
Read more of this story at Slashdot.