Reinforcement Hex
Posted: Thu Feb 15, 2018 1:19 pm
Settlement with a flag is reinforcement hex. Purchased units could be placed in it or adjacent to it during battle if no permanent deployment zone is envisioned by design.
In good old Panzer General for DOS one could make purchase and deployment there as soon as hex was captured. This was changed when PG was ported to Windows platform. A 3 turn delay before deployment could be done was added. OOB enhanced this even more by adding graphical marker during delay period, the rising flag over the settlement.
But Panzer General also had another rule regarding reinforcements. If enemy unit was adjacent to settlement deployment of reinforcements was prohibitive. This rule was very important during campaign play because AI used generic, not scripted, behaviour and relied on purchases. This days enemy units are preplaced and scripted so this rule would have no significant impact on campaign play. But it would have significant impact on Multiplayer if implemented.
Point is the following, in MP player strives to capture reinforcement hexes as soon as possible. When front line is established game usually evolves into battle of attrition (assuming there are two skilled and experienced opponents).
Defender has the advantage because it can replace loses at higher rate while the attacker needs to travel to front from nearest reinforcement hex. In order to disloge defender attacker has to have several strong units adjacent to settlement which implies that defenses in front of it were already overcome. Since such investment takes time and considerable number of troops it is not uncomon for MP games to be overly static in nature until attrition kicks in.
If old rule of prohibitive deployment in case of adjacent enemy unit is used this would make conquest more easier and possibly front line more dynamic with game experience being more enjoyable and dramatic.
In good old Panzer General for DOS one could make purchase and deployment there as soon as hex was captured. This was changed when PG was ported to Windows platform. A 3 turn delay before deployment could be done was added. OOB enhanced this even more by adding graphical marker during delay period, the rising flag over the settlement.
But Panzer General also had another rule regarding reinforcements. If enemy unit was adjacent to settlement deployment of reinforcements was prohibitive. This rule was very important during campaign play because AI used generic, not scripted, behaviour and relied on purchases. This days enemy units are preplaced and scripted so this rule would have no significant impact on campaign play. But it would have significant impact on Multiplayer if implemented.
Point is the following, in MP player strives to capture reinforcement hexes as soon as possible. When front line is established game usually evolves into battle of attrition (assuming there are two skilled and experienced opponents).
Defender has the advantage because it can replace loses at higher rate while the attacker needs to travel to front from nearest reinforcement hex. In order to disloge defender attacker has to have several strong units adjacent to settlement which implies that defenses in front of it were already overcome. Since such investment takes time and considerable number of troops it is not uncomon for MP games to be overly static in nature until attrition kicks in.
If old rule of prohibitive deployment in case of adjacent enemy unit is used this would make conquest more easier and possibly front line more dynamic with game experience being more enjoyable and dramatic.