> >From: Damian <[EMAIL PROTECTED]>
>
> >Hmm, so if you don't _tell_ the user of the program how to create
> >characters and just do it "behind the scenes," that's okay? But
> >wouldn't Open Sourcing the code "tell" the user in a roundabout
> >fashion? And what about the interactivity of the program? I mean, if
> >you allow the user to choose a method of rolling, or number of points to
> >allocate, aren't you also giving the information?
>
> I don't think he asked about d20, just the OGL.
>
> If he wanted to use the d20 trademarks for his game, he'd have to get some
> agreement with WotC... I wouldn't trust the D20STL to use it, and, IIRC,
the
> current version prohibits that.
>
> Of course, looking at the d20 guide, the definition of character creation
is
> the "description", not the rules. So you might be able to argue that
> inference and automatic creation don't violate it...
>
> I think I'll just wait for Ryan's answer. :)
I may be wrong, but 'mechanics' cannot be copyrighted. Basically, I could
create a Character Creation Software using the exact same mechanics of d20
System. However, I can't say its the d20 System, I can't use the
terminology, etc, etc.
Therefore, he can create a character creation software without anyone's
approval and distribute it. The problem comes when he tries to pass it off
in program or in promotion that it is using the d20 System. Then he would
have to adhere.
But I can publish a game using the d20 'Mechanics' and call it my own
without a problem.
-------------
For more information, please link to www.opengamingfoundation.org
