Profile of Mauser

Number 1 of Golden rule of Wehr and PE: Camp your stuff at enemy cut off, not a middle of nowhere

So as Ostheer

Yes, assuming it is a cutoff map (kolodny summer/winter). I suggest get m3 if he double mg camps on those maps.

On ALL the other maps you can get around.

Also even on kholodny, you can go harass his fuel and take the north if you want to avoid his mg's at the cutoff

I also like the elefant. I think you must get either a p4 or an ostwind out first though. You won't survive if he gets a t70. Trying to avoid the su85 with ostwind works, you can even take it out with shrecks/faust coupled with the ostwind. Ostwind will make sure he can't push with inf, and counters air. Then just stall out till you got elefant. The scope on the ost/light vehicle will also give line of sight for your paks.

Yeh, I understand the probability of a whole squad dying as that's pretty straightforward (said as much myself on a very similar thread http://www.coh2.org/topic/5122/comments-on-the-july-10-patch-notes/page/2#post_id51187 ), what threw me is trying to understand and apply weighting to the thing above from Mauser that was going a level deeper. Perhaps it doesn't need weighting. Which is kind of what I was asking.

I don't think it needs any "weighting", my example was just explaining it through binary, cr4wler's way uses normal mathematics which is a more general approach. If I understand correctly you are asking whether you need to "weigh" each row's averages? You don't need to because the chance is 50% for every squad member to die. So in my example the chance is 50% that it ends up 0 and 50% that it ends up 1. See also that in each coloumn sniper #1 is value 1(alive 50%) of the time and sniper 2 is value 0(dead) 50% of the time.

Cr4wler's way of calculating the percentages is easier if you want to calculate larger squads which he explains correctly above. If the squad size is 6 you would need 6 coloumns of binary thus

000000
000001
000010
000011
000100
etc
etc..

Which will take much longer than just using P = 0.5^6

Also you asked earlier if "there isn't a greater chance for (one of the two to die) than (both of them dying and none of them dying). The answer to that question is no. This is because:

01 (#1 dies)
10 (#2 dies)
Above combinations happen 2 out of 4 times.

00 (both die)
11 (both live)
Above combinations happen 2 out of 4 times.

The only reason I used binary for the 2 snipers is because it visually shows you the probabilities of 1's and 0's which is nice.

Note: if the chance was 30% for each squad member to die (or any number other than 50%) you hve to use P = 0.3^x because the binary will only work for 50%. Each bit is a '0' 50% of the time and a '1' 50% of the time. This cannot change.

Hehe, it pays to do the math in rts games

I'd like to explain the M3 change on units garrisoned. It's not like when the M3 dies you have 50% of chances to lose the squad, it's 50% per entity, so for each soldier. The chances to lose the entire squad are minimal

About the other changes to tanks you are asking, Relic knows about that and changes will be made. And Stephenn, that's exactly what I think too.

Cool thing is that if he uses sniper in the M3 then there is a 50% chance for each member to die when M3 is destroyed. Thus there is 25% chance that both die when M3 explodes. There is also a 75% chance that one (or both) of the two snipers will die, thus making it easy to chase down the remaining member with the german 222(or whatever unit) you killed it with.

Chances for larger squads are obviously lower yes, as Marcus correctly mentioned, so his cars will still be very viable.

I like the way they made it risk vs reward, cos now its a gamble putting units in the M3. Micro'ing M3's and last second disembarking is going to be a huge thing from now on for soviet clown car spammers

Im also very glad the 222 got a buff cos it was only useful at killing M3's. Haven't tried it yet but maybe it will be better vs inf now. 222's damage took a slight nerf, but its rate of fire and accuracy were increased. Having 0.2 accuracy instead of 0.125 is a huge increase, maybe this will mean they do a lot more damage in general (also to infantry)?

Lastly, I wonder wether at nades and fausts will be changed in a future patch cos dodging them is very hard and you can't micro out of range once the animation started. Maybe they should make it so that if you are out of a certain (longer than casting) range the nade/faust will not be thrown/fired and other player gets back his cooldown/munis.

To explain my point: Currently you can drive on the road at full speed past scripts, they cast and animation starts, and by the time they throw you are miles away and the football player script still throws. This is like a missile locking system. Maybe the "locking system" should cancel if you are far enough away (a distance further than the initial cast range but not more than a certain amount) by the time he tries to throw it (same applies to faust for ostheer).