>
> When I release products for my own setting, they'll be downloadable zip
> file, which will include the product, and a separate "OCRD" (open
> content reference document). The OCRD will contain all the Open Content
> that is in the product, so that I don't have to go to special trouble to
> identify in the product itself what is Open Content, and the developer
> need not work about mistakenly putting my PI in their works.
>
We plan on doing the something similar for our CRPG (which will use the
OGL/d20 SRD, but
due to license restriction in the D20STL we can't call it d20, use the
trademark or the logo)
I was hoping to get feedback on this idea...
Basically we were thinking of putting a zip file containing the original d20
SRD, along with
a document identifying and describing in detail what rules and features we
changed/added/didn't implement.
We would then include the source code for the relative parts of the game
that implement
these rules. Other parts of the game, such as dealing with networks,
graphics, animation,
sound etc, ie stuff that isn't the core rule engine, wouldn't be included
since it's all PI. That
way there is no confusion of what others can use and extend, only the
sourcecode applicable
to d20 implementation is released. Of course, the copyrighted term d20
wouldn't be used
anywhere, this has nothing to do with the d20 STL.
Anybody see any flaws in this? Since the OGL itself makes no reference to
the term d20.
Furthermore, since we are making no use of the copyrighted term d20 or it's
logo, the
restrictions in the d20 STL/G do not apply.
Regards,
Ryan Rogers
-------------
For more information, please link to www.opengamingfoundation.org
