GraniteStater wrote:Not in the Divisional representations. Granted, I had nothing open, but look at your screenshot. How many times have you seen eighteen icons on the row? Me? Never.
And I've never seen arty or cav integrated as part of a bde shown as an icon. I rarely see artillery icons in Divisional rows and God knows, I try to put arty in my toothpaste: I often have individual atrillery batteries in Divs and rarely see an arty icon.
If you are asserting there is a one-to-one mapping of all elements to all icons, I must beg to differ.
Also, probably getting way OT, just the last few Turns, out inthe West Texas town of El Paso (well, it's environs) - I had engaged Sibley; won; go to scope the map out and he is nowhere to be found. No "Also here," nuttin'. Not in the neighborhood. I attack Baylor and Sibley shows up.
GraniteStater wrote:RY took 'em PoW, apparently. So be warned again.
Look, I love the design, I love the game, but letting things like 'drop-off' parts of the display just go uncorrected...
it's hard to know just what the heck happened sometimes. I don't mind odd results, losing 'cuz I make bad moves, or getting pummeled outta nowhere so much - I just want a decent report.
I didn't expect the AACW screen again, but things like range - useful. Why was that dropped?
And again, yes, I know the Posture icon is displayed in the BR, but an indicator of who started the battle, who was the ostensible 'attacker' is something that's never been done. Some people might like it.
And seriously, the user community shouldn't have to be ACG to have some things displayed in a clear and informative manner.
Gray Fox wrote:If a stack crosses a major river and fights a battle, its like an amphibious assault, win or be totally destroyed.
If a stack has no retreat, then it is also totally destroyed.
The failure to cross the river and no line of retreat may be treated as cases involving movement and thus are not listed on a battle report.
A naval stack destroyed by shore battery fire while moving certainly would be this case.
If a leader is with a stack that is destroyed, sometimes the leader survives and ends up locked in the nearest friendly city for several turns until his wounds heal. This may be the case with Sibley.
I'm starting to think for real scouting, you need to take some risks and use Cav detachments - ya gotta stick the ponies in there, or at least next to. I have been, for a little while, now - I've almost given up on so-called scouting by integrated Cav.
I have, regretfully, crossed navigable rivers and been defeated and not destroyed. Darn near, but not wiped out.
Jim-NC wrote:As to the Mobile situation, I would hazard a guess that it was 100% CSA MC. If that is the case, your troops will auto switch to offensive to attempt to gain MC. I think this may even happen if you are in passive.
As to the Baton Rouge situation, the redoubt is different from the trenches within the city. In certain instances, you can get a set of level 8 trenches. So even though the fort walls are breached, the troops inside have built trenches around the breach. The surrender roll is complex (to say the least), and independent of the level of trenches of the defender. It depends on the number of breaches, supply units (or lack thereof), and the quality? of the defenders. I think it's the quality.
Note - Below is from my experiences with PON.
Siege surrender - both sides roll a die, then add modifiers. If the attacker has a higher roll, +1 breach, if the defender has a higher roll, -1 breach (if tie, nothing happens). If enough breaches, and something else happens, surrender is a possibility. The surrender roll is against the defending troops ?quality? I think it is. A supply wagon ?with supplies? prevents the surrender, but forces another roll. So if you have a wagon, you get 2 rolls to surrender (you have to fail both rolls). Without a wagon, the defender only gets 1 roll.
I think it's the same (or at least very similar) for CW 2.
As to the Mobile situation, I would hazard a guess that it was 100% CSA MC. If that is the case, your troops will auto switch to offensive to attempt to gain MC. I think this may even happen if you are in passive.
Captain_Orso wrote:If your stack is in Passive Posture it will never automatically change to Offensive Posture when entering a region, even if that region has 100% enemy MC. You will also never gain any MC from a stack in PP in any region, regardless of enemy presence.
If there is a garrison inside a location (city/fort) within a region, you can only attack that garrison by going to Assault Posture. If you are moving you will only ever assault the garrison in the last region you are plotted to enter.
I'm not sure what happens if you plot a stack to move for more than one turn and your stack coincidentally ends it's first turn of movement in a region with a garrison inside that region's location, but I assume in that case you would also not assault the garrison as your stack is still moving, but I'm not sure.
You can "retreat" through any region regardless of the enemy MC, but "retreat" is only caused by losing a battle or through overwhelming enemy presence. You cannot voluntarily "retreat". If you plot a move, even if you are in PP it is a move and not "retreat" in game terms.
If you start a turn with a stack in a region with an enemy stack, you can set your stack to PP in order to not go to OP and attack the enemy stack(s), but it will not prevent the enemy from attack your stack.
A stack in PP will fight but at a disadvantage, but with a greater chance at breaking off a battle and being able to move away.
If you are trying to get out of a region with an enemy stack it is advisable to use the Avoid Combat Special Order, but you can only use this SO if the leader of your stack is activated (does not have a brownie).
RebelYell wrote:My theory what happened.
The auto garrison militias, bad dicipline and no supply wagon, surrendered.
I did not take them in my division, I did not need them even but they keep popping up if you include them in your division.
So I left them in a separate stack, mistake, should have kept them in the division stack.
If this is what happened it is a design oversight, a bug or my installation.
Users browsing this forum: No registered users and 3 guests