Quote:
Originally Posted by Mobhack
No - find out from experience of combat, like normal troops do.
We don't tend to give any details out, especially specific numbers, for many reasons. For one thing, they are subject to change, and for another it gets us into detailed circular arguments with the rivet-counter a-retentive types.
The SP type games are not "chess type" games with guaranteed pre-ordained results from given actions, so everything is subjected to a bit of randomness. It's a "Monte Carlo" type simulation. That was how SSI designed them, and how we have continued. Real life is somewhat random, unlike chess or whatever. Real life is more of a roulette game really. perhaps the best approximation of most of the code routines is a pinball type affair. Sometimes a flipper can be triggered that rebounds the code down an unusual branch of the sprawling tree of routines. It is not a deterministic set of tables in any manner of speaking. There are "dice rolls" all throughout.
So for whatever data point you are wanting to examine, then the real way to find out what happens is to set up an exactly repeatable test scenario and then repeat that test a statistically significant number of times. Probably at least 100 iterations.
Even if you had the source code to hand, that would really be the best way to exactly figure out what happens  !.
Cheers
Andy |
I wasn't looking for the exact formula
Just you know... a hint... 5% 15% 25%?
Great now you having me counting rivets thinking about what kind of scenario I would have to create to generate a reasonable experiment
