Um, there's also a problem right now with collecting data. Something's going on that is not explained by any of the above models. Here's some data from the following combat, performed in the game (v1.1):
Attacker: A = (5, 1, 3), D = (3, 3, 3)
Defender: A = (5, 1, 3), D = (3, 3, 3)
Here's the data as *displayed* in order from first shot to last shot:
(Side firing, damage)
A, 1
D, 2
A, 2
D, 0
A, 2
D, 4
A, 0
D, 3
A, 3
D, 0
A, 1
D, 1
A, 0
D, 0
A, 5 <--
A, 0 <--
D, 1
A, 0
D, 1
A, 0
D, 1
A, 2
D, 0
A, 2
D, 3
A, 1
D, 2
A, 0
D, 1
A, 0
D, 1
A, 0
D, 0
A, 5 <--
A, 1 <--
D, 2
A, 0
D, 1
A, 1
D, 2
A, 3
D, 0
A, 2
D, 0
A, 0
D, 0
A, 5 <--
A, 0 <--
D, 0
A, 5 <--
A, 5 <--
D, 0
A, 2
D, 0
A, 2
D, 4
A, 0
D, 0
A, 5 <--
A, 0 <--
D, 0
A, 5 <--
A, 0 <--
D, 1
A, 2
D, 2
A, 4
D, 0
A, 2
D, 1
A, 0
D, 0
A, 5 (fatal shot, discard)
Occasionally the attacker fires twice in a row; when this happens, the first of the shots is always exactly 5. I've noticed this even in cases where the attacker's total offense is less than 5 (like 1). It appears to be a glitch; it's been reported, but no response from SD. Something like this makes data collection very hard...