At 10:31 AM 8/21/00 -0400, Doug Meerschaert <[EMAIL PROTECTED]> wrote:
>I think that would be a *developer's* standpoint. A *consumer* doesn't care about
>the OGL--she cares about a usable work, and just wants to be able to slap "Snakemen
>of blahblahblah" into her game.. A *developer* cares about the OGL, because he wants
>to utilize the cool rules for "Snakemen of Blahblahblah" in one of his own projects.
Actually, I was trying to address a point as a consumer. If you put
something in a gray box in a module and the only reason for the
shading is OGL-related, as the license describes somewhere else,
there's going to be consumer confusion. Usually when I see a gray
box in a game or supplement, I think it means the material is
optional.
AD&D modules used to make it a practice of devoting a page at the
end of the book to each new monster introduced in the book. That seems
like a usage that could be compatible with OGL -- in a closed work
like a module, put the things you intend to share in an appendix
followed by the license that spells out how they can be shared.
I'm looking forward to seeing how people handle the open/closed issue,
but as a consumer I think the gray-box-here and gray-box-there method
seems less than ideal.
Rogers Cadenhead
E-mail: [EMAIL PROTECTED]
Web: http://www.prefect.com
-------------
For more information, please link to www.opengamingfoundation.org
