NWN Conversions of existing modules - big "No-No"

[kaliban]

OGL content

The only thing that I see preventing me from releasing my content(i.e. modules) as OGL is a restriction placed by Bioware/Infogrames. NWN modules are not software anymore than PDFs are. If I write content, regardless of its format, I believe I can release it under any ole liscence(OGL, GPL, LGPL, etc) I want, except in this case the EULA that comes with NWN may not allow it. I need to read more of it.

Assuming there is a conflict with NWN's EULA and the OGL what I predict you will see is people releasing their content in a divided format. You'll see the map parts and the things that have to be done with the toolset released as one file that is released under NWN's EULA and then the scripts that make up the heart of a module released as a SECOND file that is released under OGL and thus allowing for use of OGC. Then it will be left to the end user to put the scripts in the module. Certain OGC (like places, maps,etc,) that can only be done on the toolset will not be able to released but the majority will.


-Len

 

[Skarp Hedin]

NWN modules are not software anymore than PDFs are.

That's a really interesting point you got there.

I'm not sure I would agree with you, but I'm not sure I disagree either. However, I'd agree that there's an argument to be made there.

You can't view a .pdf without Acrobat
You (presumably) can't view an NWN module without NWN

To most people, I'd imagine that .pdf's don't seem even remotely similar to software, since it's just words and images on a page, sorta like, you know, a book.. while an NWN module is certainly not very similar to a book. Non-text vs. text media. Maybe the license covers that, I dunno. Interesting anyhow.

 

[Cergorach]

You can't view a .pdf without Acrobat
You (presumably) can't view an NWN module without NWN

What kind of BS is this?
1.) You can view pdfs with other programs than Acrobat (ghostview for example).
2.) You can't read a simple ASCII file without an OS. What's your point? Want to make a difinition of software?
3.) Could you please point me to the sentence that forbids me to make software for (use with) the OGL? I believe only the D20 Liscence restricts software production.
4.) Everything you make for use with NWN falls under the EULA, that also means scripts, thus making OGL -> free use for Bioware.

 

[Thebalrog]

I guess Im missing the big copyright deal here.


I mean in order for a person to be prosicuted for copyright infringment for adapting an old published and copyrighted module they have to make it an exact copy, right?

I mean, if you change a few things in the campaign then it would be ok, right?

If I'm wrong, then what are the rules. It would seem that if you walk into a dungeon and get jumped by an orc party your infringing on someones rights.

So if Im wrong wheres the grey area.

 

[Orcus]

It doesnt have to be an exact copy, derivative works can infringe.

It doesnt have to be sold by you, you making $ is not an element of copyright violation.

Clark

 

[kaliban]

The conflict I possibly see with the OGL and NWN's EULA is under the last sentence of section 2 of the OGL.

No other terms or conditions may be applied to any Open Game Content distributed using this Liscence.

-Len

 

[herald]

OGL is a complete red herring <sp?> in this discussion. NWN is not being realeased under the OGL and doesn't have to satisfy any of it's requirements. It's simular to Kenser's Kalamar licence and White Wolf's Ravenloft. The reality of it is that all of NWN is closed IP wise. In addition it has been published that NWN reserves ownership on all "modules" developed with the NWN tool set. Since the EULA would conflict with the IP of WOTC, (or some other company) WOTC would more than likely not want to see any of there original adventures recreated without permission.

Having said that, it's a fact that people will go ahead and recreate old adventures. And I know people with distribute these game even if they don't do it over these boards. While there is a potential for copywrite infringment that could possibly hurt some companies, I personally feel that the damage would be little and not worth mentioning. For a few thousand dollars a company could hire a mod specialist and create a expantion pack with a module that would be much better than most of us could create and then pursue a deal with Infrogrames to distribute it.

Piracy will hurt the makes of this game more than people recreating this game in 3d graphics.

But this is just my opinion and there might be some points I have missed.

 

[smetzger]

1) A NWN module is not software. Its is a file that has information in it just as a PDF, HTML, or RTF.

2) If a pen and paper module is OGC or OGL then there are no legal prohibitions from reformating that module into a NWN module file.

3) A great majority of pen and paper modules do not have enough content designated as OGC to be able to do a legal conversion (for the public) of the module.

4) One notable exception to number 3 is the Freeport series by Green Ronin. Green Ronin has marked all text as OGC. The only stuff they have kept to themselves are the pictures and maps. So, it would be very easy to do a legal d20 NWN module of the Freeport adventures. You would just need to make your own map of freeport, your own map of a pirate ship, and your own map of a small basement/dungeon (may be a couple of other maps needed I haven't looked at the 3rd module in awhile).

*:> Scott

 

[Morrus]

2) If a pen and paper module is OGC or OGL then there are no legal prohibitions from reformating that module into a NWN module file.

Yeah, there is.

You can't use OGC in conjunction with any other license. You can't make a NWN module without using the NWN EULA. Thus you can't use OGC to make a NWN module.

 

[kaliban]

You can't use OGC in conjunction with any other license. You can't make a NWN module without using the NWN EULA. Thus you can't use OGC to make a NWN module.

Which is why you will see folks release OGL/OGC content that is not a NWN module that can be imported into one.

-Len