gamerprinter
Mapper/Publisher
Delete this post...
Last edited:
But Greggy watched some YouTube videos and so everyone can totally trust their livelihoods to his legal expertise. And if WotC sues you, all you would have to do is send them that video and WotC would totally say "oopsie! Our mistake" and leave you alone.You do understand that most content producers are not lawyers and cannot afford to hire one, right?
Here's the fundamental problem with your argument. If WotC is willing to try to steamroll people for using OGL 1.0(a), then they would be willing to steamroll people for not using using the OGL. And if people can't afford to defend themselves, then it doesn't matter if your argument would hold up in court, because they would be crushed before the case got that far and so their business would be ruined.For software development, the point of open source licenses was that I could take someones entire lifes work, word for word, and reuse it in my project, under the conditions of the license.
The point of the original OGL was that someone could take the 3e D&D rules, reproduce them in their entirety, add their own content and sell that final product as their own.
Examples include Castles and Crusades, 13th age, most of the OSR, etc.
But for all these third-party products, supplements, home brew campaigns, new character classes, new settings... you didn't need the OGL, and you don't need OGL 1.1
nor, in fact, will you need the ORC.
The OGL was a trick to force you on DMSGuild to give away half your profits.
The rules lawyer addresses this specifically at around 11 mins.
Ben talked about this in the past as well.
Of course, if you write an adventure and don't create your own monsters, you just reproduce all the WOTC ones,
a) That is a little lazy.
b) You need the OGL/ORC.
When you realize all this, you also learn how disgusting OGL 1.1 was, trying to steal from prominent creators like Critical Role with no legal standing to do it.
D&D will return when they innovate a 6th edition, but we must teach the Microsoft Executives a lesson. Hopefully, they will be fired.
I don't understand why you posted that.
But for all these third-party products, supplements, home brew campaigns, new character classes, new settings... you didn't need the OGL, and you don't need OGL 1.1
nor, in fact, will you need the ORC.
The OGL was a trick to force you on DMSGuild to give away half your profits.
For the same reason he produced the OP, which is, to be as charitable as possible, poor reading comprehension.I don't understand why you posted that.
Good way to spread your own misunderstandings and confusion about the issue OP.For software development, the point of open source licenses was that I could take someones entire lifes work, word for word, and reuse it in my project, under the conditions of the license.
The point of the original OGL was that someone could take the 3e D&D rules, reproduce them in their entirety, add their own content and sell that final product as their own.
Examples include Castles and Crusades, 13th age, most of the OSR, etc.
But for all these third-party products, supplements, home brew campaigns, new character classes, new settings... you didn't need the OGL, and you don't need OGL 1.1
nor, in fact, will you need the ORC.
The OGL was a trick to force you on DMSGuild to give away half your profits.
The rules lawyer addresses this specifically at around 11 mins.
Ben talked about this in the past as well.
Of course, if you write an adventure and don't create your own monsters, you just reproduce all the WOTC ones,
a) That is a little lazy.
b) You need the OGL/ORC.
When you realize all this, you also learn how disgusting OGL 1.1 was, trying to steal from prominent creators like Critical Role with no legal standing to do it.
D&D will return when they innovate a 6th edition, but we must teach the Microsoft Executives a lesson. Hopefully, they will be fired.
The Mythus lawsuit was clearly at least 95% BS. It had a list of hundreds of "violations" on par with the above. The problem is that you still have to convince the court on each and every one of those points that the complaint has no merit.My statement or theirs? I got it from here:
"(36) The "First Aid" skill in MYTHUS (pages 28 and 165) is
derived from the AD&D "Cure Light Wounds" spell in the AD&D 1st ed. PHB
(page 43) and the AD&D OA (page 57)."
Yeah, they didn't want a Gygaxian rival game, but the methods they used weren't really nice. I don't know how the case law in the last 30 years since that has moved on, but I wouldn't want to be on the receiving end of the lawfare stick. Which is why I'm always a bit wary when it comes to "this clearly can't be copyrighted".
Right. As a non-lawyer, I'm almost certain you can't copyright "roll d20+attack bonus above or equal to the target's armor class to hit." I am also almost certain that you can copyright "Xorn" as a trilaterally symmetrical creature mainly composed of elemental stone and that can swim through earth and stone as easily as a fish can swim through water. Somewhere between these two there is a line defining what can and can't be copyrighted, but I would not take my chances as to where that line is.While a lawyer could certainly point to many elements of the SRD or what have you that are definitely copyright protected, and could point to a few things that are definitely not, there is a vast amount of rules content that falls into a gray area of legal status too unknown to adopt or adapt with confidence that a court would not only find in your favor but refuse to enjoin you from using while the matter is being decided, and this, in fact, covers much of the exact sort of stuff that someone trying to create compatible content would want to adopt.
A few years ago, there was a lawsuit about Tetris, and I would say that if we get 20 people to divide its features between "mechanics" and "presentation", we'd get 20 results (more if lawyers in that group), and probably none would match with the distinction made in the case.Somewhere between these two there is a line defining what can and can't be copyrighted, but I would not take my chances as to where that line is.
The thing that's worth noting here is that this very much a double-edged sword. Both parties are at risk.Somewhere between these two there is a line defining what can and can't be copyrighted, but I would not take my chances as to where that line is.