Re: Dimini****ng Returns in Game Engineering

In article <O9qdnXnuktvjFM7VnZ2dnUVZ_s_inZ2d@[EMAIL PROTECTED]
>,
anglewyrm@[EMAIL PROTECTED]
 says...
> "Geoffrey Summerhayes" <sumrnot@[EMAIL PROTECTED]
> wrote in message 
>
news:0dd22911-c0fa-4762-a012-bf1f85d5941f@[EMAIL PROTECTED]
> > Ok, here's an example of a damage model that uses a lot of stats
> > average damage=
> > (max 0,
> > ((max((minimum chance to hit),
> >    min((maximum chance to hit),
> >        (base % to hit for class and level)+
> >        (agility bonus)+
> >        (equipment hit bonus))))*
> >  ((average weapon damage)+
> >   (strength bonus)+
> >   (equipment damage bonus)+
> >   ((critical %)*
> >    (average critical damage)))*
> >  (100% -
> >   (****eld block %)+
> >   (enemy agility bonus)+
> >   (enemy equipment block bonus)))-
> > ((enemy armour absorption)+
> >  (enemy constitution bonus)))
> 
> This example displays a firm grasp of what these values are generally
used 
> for. I just want to make it clear that I'm not implying anything less.
But 
> the general use pattern -- not the designer -- has a problem.
> 
> The problem is that the full range is obfiscated. It is no longer clear
what 
> the maximum 'average damage' is, even though of course there is one.
> 
Isn't that a little bit like the real world?

Mike