• NOW LIVE! Into the Woods--new character species, eerie monsters, and haunting villains to populate the woodlands of your D&D games.

Theory :At what point does a person have to cross to no longer be bound by the OGL?

So I could release a game using D20+skill vs Difficulty Test (DT), with Class Talents, Skills and Feats, six stats (Physique, Agility, Edurance, Intelligence, Wisdom and Presence) and a combat system using Battle Skill (BS) vs Defence and it would be fine even without an OGL?

hmmm thats - something
Personally, before doing this I would get better legal advice then you will receive for free on the internet!

If you rewrite Lord of the Rings, but replace every noun with a synonym, you have not necessarily avoided infringing the copyright enjoyed by the Tolkien Estate. Copying need not always be literal to count as infringing.

In the context of game mechanics it is even more complicated, because of the rule that systems/methods cannot be copyrighted but only the text whereby they are expressed. But in the context of an RPG (unlike, say, a boardgame) there is not just system but story - defining a character and his/her capabilities in terms of the six ability scores is not just a process but also the creation of a fictional conceit.

If the rest of your game also includes the D&D races, monsters etc, presented as identical story elements but with synonyms used at certain key points, I do not think it is certain that you will have avoided infringing WotC's copyright.
 

log in or register to remove this ad

A lot of discussions about OGL games and OGL publishing suffer from a degree of technical confusion.

I don't think Wicht is confused, but I think Saelorn might be.

I am certainly not confused. :D

Method (ii) is built into the terms of the OGL itself: "game mechanics . . . methods, procedures, processes and routines" in a work that is itself subject to the OGL become OGC; and a person who publishes a work subject to the OGL promises to all the world that his/her own OGC is usable under the terms of the OGL.

I would add the caveat that it is possible for a book to contain mechanics that are OGC next to mechanics that are not, under the terms of section 8. Section 1, which you are citing does say that if you publish a mechanic which incorporates OGC then the derivative must itself be OGC. Now, that being said, most users of the OGL, like Paizo, are pretty free with what they declare OGC (ie. everything); but if you introduce a non-derivative mechanic, you can declare it closed, even within the same book. *

The relevant text reads in full, "Open Game Content" means the game mechanic and includes the methods, procedures, processes and routines to the extent such content does not embody the Product Identity and is an enhancement over the prior art and any additional content clearly identified as Open Game Content by the Contributor, and means any work covered by this License, including translations and derivative works under copyright law, but specifically excludes Product Identity. "

The phrase "enhancement" refers to derivative mechanics but excludes non-derivatives. The phrase "and any additional content," clearly refers to possible non-derivative work you should choose, in section 8, to include. But that does create the aforementioned possibility of choosing not to include non-derivative work in your section 8 declaration.

*I know that I have read at least one 3e book which had a section 8 declaration worded to the effect that the contents of chapters 1 and 2 are OGC but the contents of chapters 3 and 4 are closed, including mechanics.
 
Last edited:

I wonder if there would be any interest in writing up a walk-through of how to create a product using the OGL? I suspect though there should already be one or two such things floating around on the internet...
 



I am certainly not confused.
I didn't mean to imply that you were! Quite the opposite.

But I do see a lot of threads on the OGL where posters do not distinguish between the OGC (mostly in the form of the SRD) and the licence itself.

I would add the caveat that it is possible for a book to contain mechanics that are OGC next to mechanics that are not, under the terms of section 8. Section 1, which you are citing does say that if you publish a mechanic which incorporates OGC then the derivative must itself be OGC. Now, that being said, most users of the OGL, like Paizo, are pretty free with what they declare OGC (ie. everything); but if you introduce a non-derivative mechanic, you can declare it closed, even within the same book.

The relevant text reads in full, "Open Game Content" means the game mechanic and includes the methods, procedures, processes and routines to the extent such content does not embody the Product Identity and is an enhancement over the prior art and any additional content clearly identified as Open Game Content by the Contributor, and means any work covered by this License, including translations and derivative works under copyright law, but specifically excludes Product Identity. "

The phrase "enhancement" refers to derivative mechanics but excludes non-derivatives. The phrase "and any additional content," clearly refers to possible non-derivative work you should choose, in section 8, to include. But that does create the aforementioned possibility of choosing not to include non-derivative work in your section 8 declaration.
I don't agree that Section 8 gives rise to the implication you are deriving from it. Section 8 would have a perfectly sensible operation even if all mechanics in an OGL-licensed publication were, ipso facto, OGC: namely, it would require a publisher to expressly call out OGC in the publication. For instance, in a module which contains both story elements (Product Identify), generic "how to use" info (neither OGC nor Product Identity) and stat blocks etc (let's suppose this is all OGC taken fromthe SRD), then the publisher has to clearly identify where the OGC is found in the text that you are publishing. All the work has to be done by Sections 1 and 2: when you use OGC in your text, you are bound by the Licence (s 2), which therefore includes the definitions (s 1).

You are right that Section 1 identified the declaration of "additional material" as OGC - what I described as "Method (i)".

But I think a lot of material is going to be captured by what I described as Method (ii), and I think in practice many publishers would probably want to err on the side of caution.

The relevant parts of section 1 seem to be:

(b) "Derivative Material" means copyrighted material including derivative works and translations (including into other computer languages), potation, modification, correction, addition, extension, upgrade, improvement, compilation, abridgment or other form in which an existing work may be recast, transformed or adapted

. . .

(d) Open Game Content" means the game mechanic and includes the methods, procedures, processes and routines to the extent such content does not embody the Product Identity and is an enhancement over the prior art and any additional content clearly identified as Open Game Content by the Contributor, and means any work covered by this License, including translations and derivative works under copyright law, but specifically excludes Product Identity

. . .

(g) "Use", "Used" or "Using" means to use, Distribute, copy, edit, format, modify, translate and otherwise create Derivative Material of Open Game Content.​

So derivative works under copyright law are expressly declared to be OGC. Likewise any work covered by the licence, which clearly includes material declared to be OGC by someone else's use of Method (i).

OGC is said to mean game mechanics, including methods, procedures, processes and routines are said to be OGC to the extent that such content "is an enhancement over the prior art". To the best of my understanding, "prior art" is a notion from patent law. So the reference to "enhancement over the prior art" seems to be an attempt to both expand and limit what counts as OGC: the same mechanics, methods etc reproduced using different words (and hence perhaps not counting as reproduction in the most literal sense) are nevertheless OGC (this is the expansion, from copyrightable text to the mechanics that text expresses), provided that they were enhancements to prior art (ie not already in the public domain when originally written up - this is the limitation).

The least clear matter, to me at least, is the status of material that falls under the OGL's definition of "Derivative Material" but is not a "derivative work" within the meaning of copyright law.

First, it's not clear to me how extensive that category is, because of the use of the words "addition", "extension" and "upgrade".

Second, the creation of such work is permitted by the OGL subject to the OGL (per Section 2). Is such work "work covered by the licence" - and hence ipso facto OGC?

To the best of my knowledge, the OGL has never been litigated, and so we have no definitive answer. (If I'm wrong about that, I would love to be pointed to any info.) But my own gut feeling is that the answer is yes - because it is Use of the OGC which must be "under and in terms of" the OGL, which itself declares that the OGC is "the game mechanics". Hence game mechanics that are derivative material seem to me to be work "covered by the licence".

If you think I am wrong, then anything which is not a derivative work in the copyright sense need not be identified under section 8.

If I am right, then anything which is a derivative work in the copyright sense, or is otherwise derivative material as defined in the OGL, must be identified as OGC under section 8.

In practice, I think this creates an incentive to identify as OGC anything inspired by, or clearly building on, ideas and mechanical techniques found in the SRD.

After writing the above, I decided to check the notice of OGC in the Malhavoc book "Mystic Secrets" - because these books are somewhat notorious for their thin OGC declarations. The declaration includes all the feats and magic items, plus all the mechanical elements of the spells. But not other mechanical elements which clearly build upon and interact with elements of the SRD (eg various rituals and runes). Do you have a view on whether that is compliant? I have doubts.
 

I think there are more dice systems than the d20 System that use the OGL. A lot of Fate games use the OGL I believe.
I think at least one version of Runequest has been released under the OGL.

Actually "all" FATE games use the OGL. They have to, as Evil Hat released their system under the OGL.
According to the website that I linked above, they have also released under a Creative Commons licence, which is an alternative to the OGL for those wanting to publish Fate games.
 

According to the website that I linked above, they have also released under a Creative Commons licence, which is an alternative to the OGL for those wanting to publish Fate games.

Well, since we were talking about confusion and clarity - the Creative Commons license is rather more than an alternative to the OGL for those wanting to publish FATE games. It is an alternative license for any kind of publishing. Anything that you can put out under normal copyright could have a creative commons license on it. There is, for example, a great deal of graphic art and photography out there released under creative commons licenses. Much of what is on Flickr, for example, is released under a Creative Commons license.
 

Well, since we were talking about confusion and clarity - the Creative Commons license is rather more than an alternative to the OGL for those wanting to publish FATE games. It is an alternative license for any kind of publishing. Anything that you can put out under normal copyright could have a creative commons license on it. There is, for example, a great deal of graphic art and photography out there released under creative commons licenses. Much of what is on Flickr, for example, is released under a Creative Commons license.
Sure.

Since making my post 30 upthread, I've had a look at the FAQ for the OGL on WotC's website. It also notes that the OGL can apply to games other than RPGs - anything where the distinction can be drawn between "game mechanics" and "product identity".
 

After writing the above, I decided to check the notice of OGC in the Malhavoc book "Mystic Secrets" - because these books are somewhat notorious for their thin OGC declarations. The declaration includes all the feats and magic items, plus all the mechanical elements of the spells. But not other mechanical elements which clearly build upon and interact with elements of the SRD (eg various rituals and runes). Do you have a view on whether that is compliant? I have doubts.

IANAL. But...

After consideration, I see where you are coming from with your view of the derivative works but I still think the slightly looser interpretation is the better one, because, 1) the stated need to explicitly state what content is open and what is not implies the possibility that it might not all be open, and 2) we have 15 years now of practice in publishers accepting the looser interpretation without challenge.

I do not know that the OGL has been adjudicated, like you I am not aware of any such challenge. Generally everyone has played nice with it and used it in the spirit it was intended (with WotC being the primary exception; go figure). An actual judge, I am well aware, is free to overthrow my understanding of the license. Until then, however, I am happy to keep doing it the way it has been understood to be done.

I don't have Mystic Secrets, but I do have Arcana Evolved and there are some similar things in that, especially in chapters six, seven, and eight in which, as I read the declaration, any equipment already in the SRD is open and any equipment not in the SRD is closed, likewise with new magic rules. I assume Monte Cooke and his people had decent legal advise when they drew up their declaration, as it reads fairly professionally, which makes me think their lawyer(s), whoever they were, agreed with the looser interpretation. I also seem to recollect that Clark Peterson had the same understanding, and though its been years, I do know a lot of my understanding of the OGL came from reading his comments on it.

Without seeing the actual content of Mystic Secrets, I don't want to comment on the appropriateness of the application in that particular books. But if its truly built upon OGC then in my opinion, the right thing to do is make it OGC.

I would add, for what its worth, that I think publishers who try to play tight with their content when using the OGL don't actually do themselves any favors. It creates no good will among designers, for one thing; the more content made open, the better for everyone, including the publisher (and I am thankful Paizo agrees with me on this). Secondly, its often pointless. Rituals, for instance, were made OGC in 2000 in Relics and Rituals iirc. Trying to close the barn door after the horses are loose is an exercise in futility.
 

Into the Woods

Remove ads

Top