You know it seems to me, reading this thread, that the problem is that the PCGen guys are a bunch of programmers, with a programming attitude towards the OGL. Not a slam, just an observation.
They are not actually "looking" at the OGL as a spec they have to follow, they are on a "bug hunt" trying to get complient. Instead of starting with the OGL/D20 and actually following the licenses they are trying to "fix" the OGL "bugs" in PCGen.
Everytime someone brings up an OGL/D20 issue that they have missed (some simple and obvious issues), they respond with "we will fix it in the next release", or "oops, we forgot about that" type statements. Inching ever closer to what they think the "user" (Wotc/AV) requires/wants.
What this
appears like is that the PCGen crew doesn't really have a basic understanding of the OGL at all, and just are waiting for Wotc/AV to tell them what they have to do or have done wrong. This may not be true, but from this (and other) threads, that is the impression I get.
The guys at PCGen need to *all* sit down and actually read and understand the OGL/D20 license. And I mean *all*, list and code monkeys alike. It isn't all that difficult and there are many resources available for help in understanding the license.
An alterative may be to designiate a "D20 Monkey", to handle all the license issues/questions, I have noticed that quite a few publishers have went this route, freeing the creative folks from having to wade through license issues.
Regardless someone at PCGen needs to understand and be able to apply the license. Think of it as another spec you have to write your code to.
