Thunder at the Crossroads: The Battle of Gettysburg, July 1-3, 1863 (Second Edition)

About the game

What is Thunder at the Crossroads: The Battle of Gettysburg, July 1-3, 1863 (Second Edition)?

Thunder at the Crossroads: The Battle of Gettysburg July 1-3, 1863 (from the back of the box:) On the evening of July 1st. 1863, George Gordon Meade mounted his horse for the short ride north to the small Pennsylvania town of Gettysburg. Fighting had broken out early that morning. Meade had shifted the assorted corps of the Army of the Potomac northward to that town. General Reynolds was reported down. Hancock had the field in hand (he hoped) and Meade was now moving his headquarters to that fateful field. In the few days since being thrust into command of the Army of the Potomac, Meade had gained full control and would now direct it toward what was to be its single most important battle. Turning back R.E. Lee's second invasion of the North, Meade would end the Southern general's significant offensive capabilities. For the North. it was the beginning of the march which would eventually win the war. David Powell has completely revised his earlier Thunder at the Crossroads. New scenarios allow more in-depth looks at particular actions of the battle (with smaller map and play times, too). Revised unit and leader ratings allow full integration with the Second Edition Series Rules. Graphics has been upgraded to the latest series standards. Game Scale: Turn: 30 minutes Hex: 200 yards Units: Brigade Game Inventory: Two 22" X 34" mapsheets Two countersheets (560 1/2" dual-side printed counters) One 32 page Civil War Brigade Series rules booklet Two 20 page game exclusive rule booklets Two dice Playing Time: 18 Hour Plus Complexity: Medium Solitaire Suitability: High

How it plays

Mechanics

On the shelf

Categories

Questions players ask

Questions to bring to BoardGameBrain

• How do setup and the first turn work in Thunder at the Crossroads: The Battle of Gettysburg, July 1-3, 1863 (Second Edition)?
• When does scoring happen and what ends the game?
• How should the table resolve an unusual timing or rules interaction?