Well, Of course I would include the source and license it under the OGL, making the OGC as clearly marked as is possible in a piece of Code, but that would give me three options.
1) Inlude the OGC willy-nilly, but clearly labeled, in the code, wherever it woiuld be most efficient for that particular bit of code to be. 2) Use an include function to have all the OGC in one file, which would make it easier to find, but still force the reader to determine that a line of gibberish actually means "roll a d20 and add the result to this #" and then put the rules in an inteligible format based on the implimentation of the rules in the game. (which would be like watching a gaming group play a game, and without borrowing anyone's books, building the class information of each of thier classes) 3)Or, simply put all that information in an SRD-type format included along with the source (using either of the two above options, the second being my favorite) Or is all this a moot point, because the source, as used in-game, is compiled into a non-human readable DLL? > But if anywhere in your source there appears anyone > else's OGC, or anything > derived from anyone else's OGC, then your source has > to be human readable > and licensed under the OGL. > > Don't blame me. I wish it wasn't like that. But that > appears to be how > Wizards views it. __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com _______________________________________________ Ogf-l mailing list [EMAIL PROTECTED] http://mail.opengamingfoundation.org/mailman/listinfo/ogf-l
