Ol' Choctaw wrote:I saw something odd in a single player game. I had cut the rail and moved on but during the turn two trains passed the spot carrying reinforcements .
It must not become effective until the turn after the cut is made.
Any idea why?
I am the opponant in the PBM game he is talking about.
It was my contention that since the turns are simultanious as long as the rails were good when you plotted your turn you get to use them. In other words I am willing to live with the game play aspect that the cut does not take place until the following turn and that seems to be the way it is.
However my opponant is right regarding Magruder moving much faster than he should have been able to. He did not move farther in the turn than he was able to; just that he was arriving at his particular way points 3 days early along the route I had plotted allowing battles to take place much earlier. This could conceivably have a major impact in a far more critical situation where one, or both sides are sending reenforcements to a major engagement. It can change the tide of battle allowing one sides reenforcements to get there much earlier than they should have been able to.
My opponant insists the game engine is programmed in such a way that it takes a full day to travel an entire region no matter what, but in this case even though when I plotted the move the brown circle in Shenedoah said (6) days to reach it from Richmond the in-game log said I arrived and had a battle in Shenendoah with his troops on day 3.
Magruder then went on to carry out his assault order all the way to Harpers Ferry which he should have arrived at on Day 15 based on my movmemt plot, but the log again said he arrived and had a second battle at Harpers on day 12.
Somehow the movement log where it tells you who gets where and when listed the events with a 3 day earlier discrepency between what my movement order plot said it would be before we ran the turn.
My opponant is concerned one, or both of us may have corrupted files; while I am of the opinion that is is just merely an abstract discrepency working as designed having to do with the way the program was written in order to make things work without causing a fault error, or something like that.
I am OK with the abstract aspect and dealing with movement orders not neccessarily corresponding exactly with the timing your orders phase suggests. Bad weather and Good weather as well as other abstract factors could conceivably account for these kinds of unknowns.
However, it would be nice to know and hear what other more experienced players have to say about these issues.