Matrix Games Forums

I have trouble orchestrating my operations..

It seems that leg infantry often doesn't attack simultaneously with panzers even when the phase count would suggest they should?

Static attacks also seem to throw off my timings resulting in two panzer corps attacking piecemeal and getting repulsed while a concentrated attack would probably result in a hole in their battle line..

I have the same problem sometimes. For example, 2 panzer korpses are ordered to advance by 4 hexes and attack on the last pulse. Everything is ok except of they are attacking one after other

Originally posted by ollittm:
I have trouble orchestrating my operations..

It seems that leg infantry often doesn't attack simultaneously with panzers even when the phase count would suggest they should?

Static attacks also seem to throw off my timings resulting in two panzer corps attacking piecemeal and getting repulsed while a concentrated attack would probably result in a hole in their battle line..

I haven't checked this in a long time but have been using the convention of counting each position of the plot as a time pulse. For example two German korps want to attack two Soviet armies. If a German infantry korp is adjacent to the two Soviet armies and a German panzer korp is adjacent to only one of the Soviet armies, the German infantry korp could plot 'XsYs' and not move while the panzer korp could plot 'X0Y' and advance into the Soviet X location and Y location with two plots left. The X and Y are plot directions for the units in those locations, I don't remember the exact plot numbers.

This only works if the first attack causes the Soviet army in location X to retreat on the first pulse. Continuation attacks will destroy the timing and can occur when the defender is in a swamp or city.

Finally, both the example plots could have a zero added to the plots to delay the first attack by one time pulse but there are only five plot positions so adding two zeros to to plot would require the static plot to be left off the infantry korp plot but the panzer korp should move first anyway so the effect should be the same.

Hope this helps.

Svar

Originally posted by Svar:
I haven't checked this in a long time but have been using the convention of counting each position of the plot as a time pulse.

Hmm..

So a static attack actually takes twice as long as a regular one? Not really intuitive but sounds like that's what has gone wrong for me.

I thought 's' "belongs" to the attack pulse.. If it counts as a pulse, leg infantry should take an entire turn for a single static attack..

Originally posted by ollittm:
Hmm..

So a static attack actually takes twice as long as a regular one? Not really intuitive but sounds like that's what has gone wrong for me.

I thought 's' "belongs" to the attack pulse.. If it counts as a pulse, leg infantry should take an entire turn for a single static attack..

Both panzer and infantry korps can use all five time pulses but only panzer korps can actually move in all five time pulses. Infantry korps can only move or attack twice per turn but can do so in any two of the five time pulses.

In War in Russia a static attack takes two pulses (in all versions). So an infantry corps can attack 3 times in a turn, two static attacks and a regular one.

Originally posted by Christian:
In War in Russia a static attack takes two pulses (in all versions). So an infantry corps can attack 3 times in a turn, two static attacks and a regular one.

I just tried that and could only plot the two static attacks. Version 3.0 of WIR didn't let me plot the third attack. How do you manage the three attacks by an infantry korp.

Originally posted by Svar:
I just tried that and could only plot the two static attacks. Version 3.0 of WIR didn't let me plot the third attack. How do you manage the three attacks by an infantry korp.

Movement == Combat

Combat is an attempt to move into an occupied square, so infantry corps can only attack twice in a turn because they can only move twice in a turn.

At least that's my theory anyway.

Sorry my mistake.