Bug Report: Kentucky permanent state is not...
Posted: Mon Sep 01, 2008 2:53 am
Hi,
Playing a PBEM game started under 1.020 as the Union. I invade Kentucky in August 1861, and it becomes a Confederate permanent state at the end of the turn, when the game is saved. Everything is okay at this point. During subsequent turns, Confederate militia are spawned, and my garrison requirements are as per any true Southern state. I am not able to use the Confederate factories. The only oddity is that I am accumulating population in Kentucky, but it is not being moved to a Union state as per rule 15.2.2. By mid-1862, during a post-draft phase, I notice that I am up to 13 population in the state, but since militia are more expensive than this, none have been generated.
During the Confederate's reaction phase in May 1862, I win a Strategic battle, and declare EP/BE in June 1862. Here is where something screwy happens...
In June 1862, I move a small corps into an otherwise empty London, which other than Knott and Pike is the last Confederate owned region of Kentucky. I didn't bother to check at that time to see if I could overrun the region, since I was expecting the militia spawn to prohibit it. Also, I don't recall if I did this move before or after I declared the EP/BE.
When I get the July 1862 turn back, and I check out the replay, I notice that no militia spawned in London, the battle was resolved with no casualties to either side. I then notice when checking out the Political Screen that Kentucky is now a Union-aligned state.
It was my impression that a permanent state could never switch back. My suspicion at this point is that 1.020's code fix for solving the problem of the EP/BE kicking Kentucky into permanent state status has broken something else, namely erroneously changing an already permanent state back into a neutral state, which is then converted to an aligned state, upon my capture of the last population region.
I can provide saved games upon request.
Playing a PBEM game started under 1.020 as the Union. I invade Kentucky in August 1861, and it becomes a Confederate permanent state at the end of the turn, when the game is saved. Everything is okay at this point. During subsequent turns, Confederate militia are spawned, and my garrison requirements are as per any true Southern state. I am not able to use the Confederate factories. The only oddity is that I am accumulating population in Kentucky, but it is not being moved to a Union state as per rule 15.2.2. By mid-1862, during a post-draft phase, I notice that I am up to 13 population in the state, but since militia are more expensive than this, none have been generated.
During the Confederate's reaction phase in May 1862, I win a Strategic battle, and declare EP/BE in June 1862. Here is where something screwy happens...
In June 1862, I move a small corps into an otherwise empty London, which other than Knott and Pike is the last Confederate owned region of Kentucky. I didn't bother to check at that time to see if I could overrun the region, since I was expecting the militia spawn to prohibit it. Also, I don't recall if I did this move before or after I declared the EP/BE.
When I get the July 1862 turn back, and I check out the replay, I notice that no militia spawned in London, the battle was resolved with no casualties to either side. I then notice when checking out the Political Screen that Kentucky is now a Union-aligned state.
It was my impression that a permanent state could never switch back. My suspicion at this point is that 1.020's code fix for solving the problem of the EP/BE kicking Kentucky into permanent state status has broken something else, namely erroneously changing an already permanent state back into a neutral state, which is then converted to an aligned state, upon my capture of the last population region.
I can provide saved games upon request.