> > ---------------------------------------
> > 1. D20STLG, General Definitions:
> > " 'Interactive Game': means a piece of computer gaming software
> > that is designed to accept inputs
> > from human players or their agents, and use rules to resolve the
> > success or failure of those inputs,
> > and return some indication of the results of those inputs to the users."
> > ---------------------------------------
> >
> > Under such definition falls about 99% of all software and
> > non-static websites. Web page what creates
> > NPC name (indication of result) from race & class (user input)
> > from a table (rules) using random generator (success or failure) - its
> already
> > "interactive game" under this terms.
>
> The key phrase in that section is 'success or failure' of those inputs.
> When generating an NPC, Monster, Adventure, or whatever there is no success
> or failure test, simply a tabulation based on the rules. A 'success or
> failure' is a roll of a die for the purposes of resolving an in-game
> situation, such as combat, skill checks, spell resistance, saving throws -
> situations where the term 'failure' means something. It cannot be applied
> to all die rolls (such as a random encounter table) because the concepts of
> 'success' or 'failure' simply don't mean anything in that context.
I totally agree that would be "common sense" reading of this article. However this
article still
leaves too much holes for different legal reading , and i guess no software developer
would want to
spend countless hours developing something really cool for D20 and then have
everything taken from
him in the court based on technicalitiy ( like are die rolls "success or failure" or
not ). Even
random encounter table what have entires like "no encounter" may be considered
"success/failure"
result.... Also, even "common sense" reading restrictions are IMHO too prohobitive -
no skill
schecks, saves, combat resolutions etc... So DM can create NPC, but can't make this
NPC roll skill
check or saves in software? This is very restrictive.
> You will have a much bigger problem with the prohibition on describing
> character creation and level advancement, especially for generating NPCs.
> The process cannot be automated like the Character Generator demo or
> MasterTools and still qualify for the d20 logo.
I'm much less worried about that part, because helper software can simply ask user to
type in
changes of his character advancing a level, or enter his newly created character. Of
course it would
be better to have this part automated, but this is not a showstopper like the rest of
the issues.
> If you forego the d20 logo, you can do anything you want, but the status of
> your code is somewhat undefined at this point. It might be OGC, or PI, or
Correct me if i'm wrong - but if you forego D20 logo, acordign to OGL, 7. you can't
indicate
compatibility with other Product Identity or Trademark. Including D20 trademark.
Software for D20
which can't mention anywhere that its D20 compatible and/or D&D compatible would be
impossible to
promote to target audience.
OGL, 7 certainly make sence taken alone. No one would want someone releasing bunch of
crap under OGL
and then sticking your logo and trademark in every place claiming "compatibility" and
thus degrading
public trust and respect for *your* product. But OGL,7 and D20STLG, Restricted
Trademark Use taken
togeather basicaly prohobits any resonable shareware or software development for D20.
I guess what i'm trying to find out is that prhobition is desired effect by WotC or
its unfortunate
side-effect what going to be adressed before final release of D20STLG. Of course WotC
has all the
right to prohobit independent software development for D20, its their baby, but its
better to be
stated clearly in some document, one way or another.
- Max
