|
Post by Simon on Dec 13, 2017 19:02:15 GMT
.. and we are back to the very question I asked when I started this thread. I am coming to the view held by Paul, Pete and Martin (amongst others) that an overlap against an element supporting from the rear does not count so, in your A4 example, the Warband fights at +4, not suffering the overlap.
regards
Simon
|
|
|
Post by stevie on Dec 13, 2017 19:40:03 GMT
I think that Ronald, and Bob for that matter, are absolutely right… …and the problem is we are all trying to bend the rules to give us the result that we want. I’d like to draw peoples attention to the second sentence of page 10 paragraph 8:- “Any enemies in any mutual flank-edge contact overlap each other whether in close combat or not.” What does the “whether in close combat or not” actually mean? I think Ronald’s diagram shows it well. In picture A2, Warband ‘A’ is in close combat, and in mutual edge contact, so is overlapped. In picture A4, Warband ‘B’ is not in close combat, but it is in mutual edge contact, so is overlapped. The meaning of this sentence is quite clear. So, what happens to a supporting element that is overlapped? For that we have to look at the last sentence of page 10 paragraph 7:- “A flank or rear contact on an element providing rear support is treated as if on the supported element.” Please note that the words “front-edge” do not appear anywhere in this line. Nor does it say “A flank or rear attack”…it just says “flank or rear contact”, meaning touching a flank or rear. The meaning of this sentence is also quite clear. Therefore, in order to protect the front warband from the ludicrous situation of having its combat factor reduced from 3 to 2 just because it's support has two flanks in mutual edge contact, we are trying to add words that are not there. By a) pretending that the words “front-edge” appear in the last sentence of page 10 paragraph 7, …or b) pretending that the words “a support factor cannot be less than zero” appear in page 10 paragraph 7. It's either that or accept that having warband support can sometimes become a hindrance and a drag on the front warband. Now this wouldn’t be the first time that it was discovered that some rules are missing from DBA 3.0. That is why we have the FAQ. So until an official or at least semi-official ruling is issued on this matter, I’m instructing my friends to adopt the following House Rule:- Support Contacts: when a supporting element is in mutual side-edge contact with an enemy, the supporting element suffers the combat penalty for being overlapped, and has it’s support factor reduced (see rules 10.7 and 10.8). A support factor of less than one is treated as zero support. Some potentially useful player aids can be found here, including the latest June 2017 FAQ and the Quick Reference Sheets from the Society of Ancients:- fanaticus-dba.wikia.com/wiki/Category:Reference_sheets_and_epitomes
|
|
|
Post by stevie on Dec 13, 2017 20:19:46 GMT
Oh, and one more thing. If anyone disagrees with the above House Rule and insists on taking the current rule literally, consider this. In good going a warband column with it’s support in two mutual edge contacts would suffer two overlaps. And a +1 for rear support with -2 for mutual edge overlaps would have the front warband fighting at 2 instead of 3. Now take the very same situation but put the warband column in rough or bad going. As it has no support in these terrains, the two mutual edge overlaps on it’s support element would have no effect. So the warbanhd column fights with a combat factor of 2 in good going, but as a 3 in rough or bad going. Try and justify that. Some potentially useful player aids can be found here, including the latest June 2017 FAQ and the Quick Reference Sheets from the Society of Ancients:- fanaticus-dba.wikia.com/wiki/Category:Reference_sheets_and_epitomes
|
|
|
Post by primuspilus on Dec 13, 2017 20:27:33 GMT
I have always had the view that the rear support was not neccesarily wave after wave. Pike phalangites are a case in point. I also think the rear support mechanism for LH, Wb and Pk in DBA was a mistake in a 12-element game, unless it applied equally for all elements, to give a commander the conundrum between depth and width of his deployment.
With that in mind, I remain unconvinced that Phil's intent was the the rear elements should cease to provide support upon being merely overlapped. I think the "whether in close combat or not" I believe to be a qualifier that refers to the overlapping element. That is to say, an overlapping element that is already in close combat to its front, continues to provide the overlap penalty/benefit. You can't "strip off" an overlap by simply moving another element to "distract" the overlappers...
I find it helps to have played thousands of games against dozens of different players. That said, I can see Stevie's point. If you are new to the game, you feel the rules should be entirely self-contained, and "uni-contextual"...
|
|
|
Post by stevie on Dec 13, 2017 22:12:55 GMT
You make a good point primuspilus. Perhaps the “whether in close combat or not” does refer to the overlapping element. (i.e. it doesn’t matter if the mutual edge overlapping element is in close combat or not, it still overlaps) However, that still doesn’t change the last sentence of page 10 paragraph 7:- “A flank or rear contact on an element providing rear support is treated as if on the supported element.” I’ll be honest…I’m trying to prevent the front warband element in a column from having its normal combat factor reduced just because it’s supporting element has two mutual edge overlaps/contacts in good going, but in rough or bad going the same column still fights at full strength. That House Rule has this effect, even if the wording does not match the exact wording of the current rules. I’m more interested in the final effect rather than how that effect is generated. Some potentially useful player aids can be found here, including the latest June 2017 FAQ and the Quick Reference Sheets from the Society of Ancients:- fanaticus-dba.wikia.com/wiki/Category:Reference_sheets_and_epitomes
|
|
|
Post by primuspilus on Dec 13, 2017 22:23:52 GMT
Again, I think a simple clarification may be required for the new-to-the-DBx-system gamer: the contact herein means "close combat contact". Mutual flank edge contact is (clearly) not close combat contact, or both elements would be required to turn and face each other automatically.
That is the way I have always seen it played, whether HotT, DBA 2.2, or even 2.2+... YMMV.
|
|
|
Post by stevie on Dec 13, 2017 22:54:29 GMT
Sorry primuspilus… …you may have been playing that way for years, but it is not how DBA 3.0 uses the word ‘contact’. (I know I’ve posted this before, but I’ll post it again in full)
The Times DBA 3.0 Uses The Word ‘Contact’ To Just Mean ‘Touching’:- Road Moves: Moving along a road until it contacts enemy or friends [8.6]. Dismounting: Troops cannot dismount while in any contact with enemy or in an enemy TZ [8.9]. Groups: Elements must be in both edge and corner-to-corner contact with another [8.10]. Columns: Elements must be in at least corner-to-corner contact if part of a wheeling column [8.10]. Making Contact: CP/Lit/CWg/Art/WWg cannot move into any contact with enemy [9.12]. Support Contact: A flank or rear contact on an element providing rear support affects the supported element [10.7]. Overlaps: in mutual right-to-right or left-to-left front corner contact with any enemy element [10.8]. Side-Edges: Any enemies in any mutual flank-edge contact overlap each other whether in close combat or not [10.8]. Table Edges: A front-corner 1 BW from the battlefield edge unless this is in contact with a friendly element [10.8]. Flank Support: Some troops +1 if in mutual side-edge and mutual front-corner contact with a friendly element [11.2]. Recoil Obstacles: An element already in such contact with any of these cannot recoil and is destroyed instead [12.5]. Fleeing Direction: If it contacts a battlefield side-edge, it pivots and continues the move along that edge [12.6].
The Times The Words ‘Front-Edge’ Have To Be Added To A Line Containing The Word ‘Contact’:- WWg: count the first edge in contact as their front-edge when in close combat [4.10]. Sequence of Play: elements of both sides whose front-edges are in suitable contact with enemy fight in close combat [8.4]. Moving into Contact: moving a front-edge into contact with enemy always results in combat [9.9]. Legal Contacts: front-to-front, front-to side, front-to-rear, with corners touching, and overlap positions [9.9]. BUA Contact: Other elements (except Scythed Chariots) can contact a city, fort or camp with their front edge [9.12]. Close Combat: when an element moves into both front-edge and front corner-to-corner contact with an enemy [10.6]. Assaults: A city, fort or camp can be in contact with the front-edges of up to 3 assaulting elements [10.9]. Flank/Rear Destruction: An element that has an enemy front-edge in contact with its side or rear-edge is destroyed [12.1]. Pursuers: If pursuing element’s front-edge contacts enemy or its front-corner contacts an enemy front-edge, [12.11].
Clearly DBA 3.0 uses the word ‘contact’ to simply mean any kind of touching, and then has to add the words ‘front-edge’ when only front-edge touching applies.
|
|
|
Post by primuspilus on Dec 14, 2017 4:31:08 GMT
But if you just add the words "close combat" in front of the word "contact" in your example, the problem is solved. No need to add two additional lines of rules, no?
K.I.S.S. ?
Occam's razor...
Sorry, that is just the applied financial engineer in me...
|
|
|
Post by stevie on Dec 14, 2017 7:59:34 GMT
Very well…I’ll rescind that House Rule and submit to peer pressure. Just as long as we all acknowledge that we are adding words and bending the written rules to get the result we want. Therefore, in order to protect the front warband from the ludicrous situation of having its combat factor reduced from 3 to 2 just because it's support has two flanks in mutual edge contact, we are trying to add words that are not there:- By a) pretending that the words “front-edge” or "close combat" appear in the last sentence of page 10 paragraph 7, …or b) pretending that the words “a support factor cannot be less than zero” appear in page 10 paragraph 7. It's either that or accept that having warband support can sometimes become a hindrance and a drag on the front warband.
I’ll just have to add this to my growing list of “DBA 3.0 rules that don’t mean what they say”…
|
|
|
Post by primuspilus on Dec 14, 2017 14:23:26 GMT
Well, whether or not you succumb to peer pressure, we are agreed that inserting the words as I suggested accomplishes the same thing as its more lengthy compatriot, no? And we are after succinct, short rules, aren't we?
And are you by any chance familiar with Goedel's Incompleteness Theorem? Knowing this theorem will save you decades of trying to perfect rulesets.
No matter how hard you work at ANY axiomatic system (for example, wargames rules), it will ALWAYS contain results not derivable from the statement of the axioms... That is to say, you will ALWAYS find instances of the rules not meaning what they say...
|
|
|
Post by stevie on Dec 14, 2017 17:06:29 GMT
Hmmm…that might be true up to a point primuspilus…but only up to a point. Simply changing a single word can sometimes do wonders to improve clarity:- “A flank or rear contact attack on an element providing rear support is treated as if on the supported element.” (Although including the words ‘front-edge’ or ‘close combat’ would be even clearer)
Another prime example is that old chestnut of mine, page 11 paragraph 4, last sentence, which says:- “A supporting element in close combat against an enemy element’s flank or rear recoils if the friendly element in combat with that enemy’s front recoils, flees or is destroyed.” And page 12 paragraph 9, “Pursuing”, last sentence, says:- “…an element whose close combat opponents recoil, flee or are destroyed must immediately pursue (if they’re right type).” So troops in front-edge contact with an enemy flank or rear are classed as being in close combat… …and some close combat troops will pursue!
But noooo I’ve been told…it might say that, but what it really means is the way we old-time players have been playing it for years, and we never have flanker’s pursuing (even if Phil Barker’s rules say they do).
Well, if that is the case, then perhaps page 11 paragraph 4, last sentence, should say:- “A supporting element in close combat front-edge contact against an enemy element’s flank or rear recoils if the friendly element in combat with that enemy’s front recoils, flees or is destroyed.”
(I strongly believe that if a problem exists in a DBA rule, we should at least try to fix it, rather than just pretend everything is fine)
|
|
|
Post by bob on Dec 15, 2017 18:26:45 GMT
While there may some wording issues it the situation that Stevie raises, again, there is no logical problem.
"When an element is in close combat both to front and to flank or rear or in close combat to its front and overlapped, only it and the enemy element in front fight each other. Others only provide tactical factors"
"A supporting element in close combat against an enemy element’s flank or rear recoils if the friendly element in combat with that enemy’s front recoils, flees or is destroyed."
So, in the context of the rules, only the front edge to front edge elements are fighting in close combat, the flanking or rearing element are supporting with tactical factors.
"Otherwise an element whose close combat opponents recoil, flee or are destroyed (and all elements in a column behind such an element) must immediately pursue," This rule does not say the "supporting elements" also pursue.
Come on now, Stevie, how is a element to the flank or rear of the destroyed element going to pursue? Do you suggest the front element which is in actual close combat is going to just run into the flank and rear elements that you suggest also pursue. A big traffic jam:)
|
|
|
Post by stevie on Dec 16, 2017 3:30:28 GMT
While there may some wording issues it the situation that Stevie raises.... ...and that is all I'm saying Bob..."When an element is in close combat both to front and to flank or rear or in close combat to its front and overlapped, only it and the enemy element in front fight each other. Others only provide tactical factors" ...no argument from me there..."A supporting element in close combat against an enemy element’s flank or rear recoils if the friendly element in combat with that enemy’s front recoils, flees or is destroyed." ...so the rules say that flank attacks are 'classed' as close combat... ...they don't actually fight, but they are 'classed' as being in close combat... So, in the context of the rules, only the front edge to front edge elements are fighting in close combat, the flanking or rearing element are supporting with tactical factors. ...still agreeing with you so far..."Otherwise an element whose close combat opponents recoil, flee or are destroyed (and all elements in a column behind such an element) must immediately pursue," This rule does not say the "supporting elements" also pursue. ...nope, you're right...it says those in close combat pursue...Come on now, Stevie, how is a element to the flank or rear of the destroyed element going to pursue? Do you suggest the front element which is in actual close combat is going to just run into the flank and rear elements that you suggest also pursue. A big traffic jam:) Bob, take the following rules (paraphrased in order to save space):- Close Combat: Close combat is when an element is in both front edge and front corner-to-corner contact with an enemy. [10.6] Flank/Rear Attacks: Troops in close combat against an enemy flank/rear also recoil if the friends in combat with the enemy’s front are defeated. [11.4] Pursuing: an element whose close combat opponents recoil, flee or are destroyed must immediately pursue. [12.9] You can’t say “We don’t want to change Phil Barker’s rules…but we don’t want to follow them either!” You and I both want the same thing: we both want to stop flank attackers from pursuing. The difference is you want to change people’s perception of what the word’s ‘close combat’ mean when it comes to pursuing. I want to change the written words to show what ‘close combat’ means when it comes to pursuing. But we both want to change the words as they are currently written in order to give us the effect that we want. Figure 19c gives us both what we desire, as the dialogue says:- “Auxilia A is in front-edge close combat with Cavalry X. Psiloi B is in flank contact with Cavalry X.” Note that it does not say “Psiloi B is in close combat with Cavalry X”…it just says it’s in “flank contact”. So if Psiloi B were of a type that likes to pursue, it wouldn’t do so, because it is in “flank contact” and not “ close combat”. Figure 19c is giving us the correct interpretation. Rules 10.6, 11.4, and 12.9 are giving a false misleading interpretation, if you take them literally. Therefore, the Pursuing rule 12.9 doesn’t mean what it says. Perhaps if Pursuing rule 12.9 were re-worded, it would mean what it says:- “...or whose pursuit move would cross a battlefield edge, or enter such bad going, or if they are attacking an enemy flank or rear, does not pursue.” That might be better than trying to justify why ‘close combat’ means one thing in rules 10.6 and 11.4, but means something completely different in rule 12.9.
|
|
|
Post by goragrad on Dec 16, 2017 4:07:46 GMT
And if 19c is the correct interpretation then how does that impact 10.3 -
"Shooting is not possible if shooters or target are in close combat or providing rear support, but is possible to or from elements that are overlapping and not in close combat."
Does that need to be re-interpreted to -
"Shooting is not possible if shooters or target are in close combat or flank contact or providing rear support, but is possible to or from elements that are overlapping and not in close combat."
|
|
|
Post by stevie on Dec 16, 2017 11:03:19 GMT
Well Goragrad, it’s Pursuing rule 12.9 that apparently doesn’t mean what it says (i.e. all close combat troops pursue).
So leave all references to ‘close combat’ as they are… …add the words “flank and rear attackers do not pursue” to rule 12.9… …then everything is perfectly clear and hunky dory.
(Of course, all this is assuming that is what Phil Barker’s actual intention is. I’ve never met him, and for all I know he might want all close combat troops to pursue. That's what his rules actually say. And that’s why he deliberately chose the words he did in the Pursuing 12.9 rule. If that is not his intention, then it’s an unfortunate choice of words, so let’s fix it.)
|
|