We got an official leak of One D&D OGL 1.1! Watch Our Discussion And Reactions!

Glade Riven

Adventurer
That all hinges on whether they can in fact "de-authorize" v1.0(a), which is a very open question at this point.

Sure, WotC can try and say that it's been de-authorized and supplanted by v1.1… but can they actually stop anyone who wants to publish under v1.0a from pretending that v1.1 simply doesn't exit?
There is a thing (at least under US law) which is implied agreement (example 1: courts assume that if you are using software, you are agreeing to the terms of service to use the software; example 2: banks changing their TOS with customers and ending the notification with "if you disagree with these changes, you have until X date to close your account). So if you publish under OGL 1.1 you automatically agree that 1.1 replaces 1.0a.
 

log in or register to remove this ad

S'mon

Legend
There is a thing (at least under US law) which is implied agreement (example 1: courts assume that if you are using software, you are agreeing to the terms of service to use the software; example 2: banks changing their TOS with customers and ending the notification with "if you disagree with these changes, you have until X date to close your account). So if you publish under OGL 1.1 you automatically agree that 1.1 replaces 1.0a.

Yes, don't publish under 1.1 if you don't want to be bound by it!
 



Branduil

Hero
The issue is not just how bad attempting to destroy the OGL 1.0a would be(it's obviously extremely bad), but that they're essentially setting fire to the entire community and proving themselves completely untrustworthy in all future contractual dealings. You can't unring that bell-- if they're willing to wage war to destroy the OGL, nothing else they say or claim in the future can be trusted either. It's monumentally stupid and self-destructive, in a way that's far worse than the GSL was.
 

Jack Daniel

dice-universe.blogspot.com
There is a thing (at least under US law) which is implied agreement (example 1: courts assume that if you are using software, you are agreeing to the terms of service to use the software; example 2: banks changing their TOS with customers and ending the notification with "if you disagree with these changes, you have until X date to close your account). So if you publish under OGL 1.1 you automatically agree that 1.1 replaces 1.0a.

Yes, don't publish under 1.1 if you don't want to be bound by it!

Obviously. But the question at hand is whether publishing under 1.0 can implicitly bind you to 1.1 (and more to the point, whether publishing under 1.0 after 1.1 has been released can do so).
 

mamba

Legend
Obviously. But the question at hand is whether publishing under 1.0 can implicitly bind you to 1.1 (and more to the point, whether publishing under 1.0 after 1.1 has been released can do so).
no, it cannot. Worst case (which also us where this is headed) you cannot publish anything new under 1.0
 


dbolack

Adventurer
That all hinges on whether they can in fact "de-authorize" v1.0(a), which is a very open question at this point.

Sure, WotC can try and say that it's been de-authorized and supplanted by v1.1… but can they actually stop anyone who wants to publish under v1.0a from pretending that v1.1 simply doesn't exit?
Regardless of whether or not they can unilaterally declare it unauthorized ( including for contracts they aren't a party of?! ) they can indeed press you to agree it is unauthorized in a follow-up contract. My
 


Remove ads

Top