-
2 Votes6 Posts2k Views
-
2 Votes21 Posts152 Views
-
4 Votes2 Posts25 Views
-
0 Votes20 Posts366 Views
-
1 Votes3 Posts56 Views
-
5 Votes22 Posts2k Views
-
1 Votes15 Posts536 Views
-
4 Votes26 Posts760 Views
-
2 Votes41 Posts962 Views
-
1 Votes4 Posts85 Views
-
4 Votes19 Posts399 Views
-
2 Votes8 Posts226 Views
-
2 Votes7 Posts409 Views
-
2 Votes22 Posts3k Views
-
1 Votes4 Posts482 Views
-
3 Votes5 Posts670 Views
-
0 Votes2 Posts1k Views
-
3 Votes5 Posts1k Views
-
2 Votes1 Posts549 Views
-
2
1 Votes10 Posts2k Views
Recent Posts
-
@iratoric which North Africa game? AFAIK some of the variations are mutually exclusive. I think the first task it is to identify which variations should be plausibly supported. Once done, I would like a full spec identified. Following, we can then look at the plan for how that would be encoded into XML. Doing so iteratively and not all-at-once is perfectly fine. Though, I think we should know beforehand which retreat variations we are likely to want (and also in which maps).
-
Thanks everyone for your opinions. I have thought about this a lot, and it is probably best if we start with implementing one set of rules and branch out from there. Otherwise there are simply too many possible combinations to do all at once. Since the North Africa game is the “official” ruleset and an already existing game that needs this rule, I think that whatever I implement should support that first. I will code it in such a way that it still leaves room for more variations later. Thoughts?
I instead think that the baseline should be some version of what you/we can devise as the simplest retreat system, have that done and tested, then adding properties and/or options for each element adding complexity.
For example, in the basic system you retreat to the same zone. Next step, with property, is retreating to an other zone. Next step, with property, is limiting retreat only to zones not under attack by land units. And so on.
-
Thanks everyone for your opinions. I have thought about this a lot, and it is probably best if we start with implementing one set of rules and branch out from there. Otherwise there are simply too many possible combinations to do all at once. Since the North Africa game is the “official” ruleset and an already existing game that needs this rule, I think that whatever I implement should support that first. I will code it in such a way that it still leaves room for more variations later. Thoughts?
-
Thinking on this some more and to add what I previously posted,
Defender retreats.
Next turn, Defender attacks and retreats after 1 rd. They can only retreat from a TTy where they started, assuming no units from other TTys attacked, they would have to retreat/remain where they started.
Original Attacker still has units in the TTy.
Their next turn they can either attack with some or all of their units, including units from other TTys, as per current rules.
Remain in place, no combat takes place and they retain control of the TTy. Can be reinforced in NCM, even if all units at turn start have moved out.
Can move some or all of units out of the TTy and either attack or NCM. They would still retain control of the TTy even with no units present.
The retreated units would have to attack the empty TTy on their turn to take control of it. Blitzing allowed.
I may have misunderstood what @iratoric was originally proposing. I thought it was basically to work like submerging Subs.
At any rate, Good Luck with whatever you decide
