2009-08-18, 12:19 AM
I'm going to concede that my program doesn't calculate it correctly at the moment. Has a problem with not counting all the different ways a certain damage amount can occur (e.g., 42504 can occur 6 different ways). For the case above, I think it should give correct results due to a 50/50 scenario being symmetric... but being correct because of that is hardly satisfactory.
--------------------------
Also, since I must (at some time) rewrite my program, I have a question.
Question: How exactly is damage calculated? More precisely, at what point in damage calculation does the game (randomly) choose a number?
So the reason it matters is because:
If the game calculates damage by a), then there are gaps in damage. Your min/max damage will be possibilities but not so for all the numbers in between. For example, damage possibilities might be like: 14167, 14169, 14170, 14172, etc.
And of course, this affects how I should write the calculation section.
--------------------------
Also, since I must (at some time) rewrite my program, I have a question.
Question: How exactly is damage calculated? More precisely, at what point in damage calculation does the game (randomly) choose a number?
Spoiler
-------------------So the reason it matters is because:
If the game calculates damage by a), then there are gaps in damage. Your min/max damage will be possibilities but not so for all the numbers in between. For example, damage possibilities might be like: 14167, 14169, 14170, 14172, etc.
And of course, this affects how I should write the calculation section.

