My one concern is this.  We have gotten in the habit of creating 
developmental tools that concist of canonical lists of "open game elements" 
(feats/features/etc) for our designers / authors.  Such things as a 
spreadsheet listing all of the feats and class features, with keys for 
appropriate uses and prerequisits.  This is a tremendous advantage as it 
vastly simplifies creating new and interesting "supra-game elements" 
(character classes/ NPCS / creatures)  Because we put a great deal of work 
on these in at the very beginning, these tools have become invaluable to our 
authors.

In the past, adding one of these game elements from an open source meant 
adding the "copyright notice" from that work into the SEC. 15 of our 
products' OGL.

The developmental list of "MONSTER SPECIAL ABILITIES" is currently rather 
short, consisting of material from the SRD + two or three other sources.  
Placing these into SEC 15 has not really resulting in much additions to our 
SEC 15.

With the system you are proposing, however - should we want to include your 
material in our developmental archives for our authors to use, we would have 
to put literally dozens and possibly HUNDREDS of new entries into our 
section 15.  Evewn just using more than a couple of creatures from this book 
could result in some real recordkeeping headaches...

Or am I missing something.  How many different authors/sources are we 
talking about here?

Faust


>From: Clark Peterson <[EMAIL PROTECTED]>
>
>I think Martin is trying to make this way more
>complicated than it is. I want to find a way to do
>this easier than how I proposed it. Not more
>difficult. But of course, I dont expect to constrain
>the discussion to only my agenda. :)


_________________________________________________________________
MSN Photos is the easiest way to share and print your photos: 
http://photos.msn.com/support/worldwide.aspx

_______________________________________________
Ogf-l mailing list
[EMAIL PROTECTED]
http://mail.opengamingfoundation.org/mailman/listinfo/ogf-l

Reply via email to