Close Combat – Last Stand Arnhem is a highly enhanced new release of Close Combat, using the latest Close Combat engine with many additional improvements. Its design is based on the critically acclaimed Close Combat – A Bridge Too Far, originally developed by Atomic Games, as well as the more recent Close Combat: The Longest Day. This is the most ambitious and most improved of the new Close Combat releases, but along with all the enhancements it retains the same addicting tactical action found in the original titles! Close Combat – Last Stand Arnhem comes with expanded force pools, reserve & static battlegroups, a troop point buying system, ferry and assault crossings, destructible bridges, static forces and much more! Also included in this rebuild are 60+ battles, operations and campaigns including a new enhanced Grand Campaign!
my opponent and i want to work out some house rules. basically i had been attacking from the south last turn, and took the ground around those allied icons. then next turn i also moved a unit in from the north. but now, i can only deploy in 2 little squares down south, and up north i can deploy everywhere; my opponent is confined to little squares surrounded by my land. do you just basically make an agreement to deploy in the area you would have had?
I think most people play with the VL rule in effect (you can only deploy in areas that is connected to VL, so no "pockets" behind the lines without VL deployment). Some also play with a 50 meter rule in situations like the case above. Check out Closecombatseries.net for more ideas. They have a GC guide that might.
"To you, we are deeply grateful, and release what little hold we might, as Durandal, have had on your soul.
Go."
- Final Terminal Message Marathon Infinity
I'll have Steve respond but I'm pretty sure this isn't a bug. It's been part of how CC works since prior to the rebuilds. I know there's been discussion on it and pros and cons presented for both ways of doing it. i.e. connecting controlled VL's to your deploy or leaving them as is. There's another thread where this same thing is being discussed.
For as long as I can remember one rule that's been applied for people who don't like the "VL's being awarded in morale victories" is that you may only deploy in areas either as Dundradal said have a VL in them or are connected to your main area of deploy.
Ok, maybe there is some misccomunication here. I understand when the battle ends due to morale the winning force will be awarded a certain amount of VLs based on the difference in force morale between the losing and winning force and this is by design.
However, something else not normal is occuring here.
In my case, when the battle ended the allies took took the objectives as marked similiar in the picture posted by Das Hoff as above, with the germans controlling the other VLs and all the map area north of the church, ie pretty much all the area between the german vls . The allies had not taken all the areas around the German VLs.
The next time this map was played, for some reason the Germans deployment zone was reduced to strictly the areas around the their VLs, while all the area in between that they had controlled at the end of the previous battle was taken away from their control. If you look at the pic above specifically the map inset in the lower left, the area that the Allies have for deployment around the German VLs is what the Germans controlled in the previous battle, while the area in gray in the South that the Allies controlled at the end of the previous battle is now a no mans land where no one can delploy.
Basically it took the german deployment area around the German VLs and awarded it the Allied player, while taking the area around the Allied VLs and making it non deployable.
I have played CC4, CC5, WaR, and TLD, and have not seen this happen before.
I have seen this happen on the map posted above by Das Hoff, and Eindhoven, possibly one other
I have seen the same bug several times. I call it 'checkerboard VLs' - it seems to happen when the attacking side changes its attack BG and the map entry VL thru which it attacks. The defending side gets screwed out of all the map territory it had controlled at the end of the previous battle except for square deploy areas (3x3 deploy tiles) around the VLs it controlled (as shown above).
I have seen the same bug several times. I call it 'checkerboard VLs' - it seems to happen when the attacking side changes its attack BG and the map entry VL thru which it attacks. The defending side gets screwed out of all the map territory it had controlled at the end of the previous battle except for square deploy areas (3x3 deploy tiles) around the VLs it controlled (as shown above).
Left side of pic below shows map control after end of turn 1 battle on Schjindel map between KG Chill & 501/101 (Hells Highway Campaign). Right side of pic shows map control at start of turn 2 battle on Schjindel between KG Chill and 501/101 after 1/501 moves onto Schjindel from Veghel to support 501/101's continuing attack.
In effect, 501/101 has been heavily penalized in map territory controlled (not VLs) for receiving support in its attack from 1/501.
Understood. Steve didn't have time to respond but he did ask me to make a bug report so he can look at it closer. If you could give what Andrew suggested a try that might help provide some more information. Every bit of info helps. Thanks.
"...1/501 moves onto Schjindel from Veghel to support 501/101's continuing attack." AI is playing Allied side anyway.
Granted, I did play 3 battles in my first GC before discovering BGs had a right click context menu in the start movement phase.
Save file of the campaign attached (rename from .txt to .zip). Click on Schjindel in the strat screen to see post-turn one map control, then start battle to see effect of 1/501 moving in to support.
That is definitely a bug and definitely has not been around since the original CC series. I've had all sorts of very questionable deployment zones(mainly Axis Creep) from one battle to the next with this release and I've never had any of these bugs on previous versions of CC.
