|
Post by Baldie on Aug 11, 2018 17:55:11 GMT
Hi All
For clarity I bloomin love DBA 3.0 and seem to enjoy it more and more as I get games in.
Def can't see me stopping anytime soon which for those who take points off me can only be a good thing.
|
|
|
Post by lkmjbc on Aug 11, 2018 18:17:32 GMT
Before giving up DBA3.0 I looked at doing my own version by cutting and pasting here and there, the intention being that as far as possible all information was in one place. I gave it up when I realised it was going to be huge and problematical.
DBA is going down with 6th symptoms, having seen it played, people were going to different parts for answers to the problem.
Still, stay in there, it might become a good game if enough corrections/amendments/suggestions are used.
David Constable
David... Aren't you being a bit pessimistic?
Since 2014, I have run 7 (at least) DBA 3 tournaments, several campaigns, and countless club games without much, if any controversy.
Further, DBA 2.2 produced a 70+ book clarifying how to play. DBA 3 has produced a 5 page FAQ... and some of that consists of reminders to folks of differences from earlier versions.
Finally, DBA 3 renders excellent results when playing historical scenarios, something that DBA 2.2 could not do in many circumstances. I produced an entire book with the help of many on this board to showcase this.
DBA 3 seems to have led to a revival of the tournament circuit in England.
Where are these huge and problematical problems? How are they manifesting? How is DBA "going down"?
It seems on the rise here.
We will probably address the shooting issue in the next FAQ. That is a good thing as the FAQ updates have been reduced to only one per year due to the lack of questions.
Joe Collins
|
|
|
Post by davidjconstable on Aug 11, 2018 20:50:44 GMT
Hello Joe
I am being a pessimist, but it is what I have seen going on for years.
Practically all the WRG rules have gone the same way, new version after new version, each adding complication.
But now is the time to do something about it, not ten years time, and not just over shooting or wrong army lists. Make the rules understandable by a twelve year old, everything has a place, everything in its place.
Change it or loose it.
David Constable
P.S. - Where are the future players coming from, what will they be interested in?
|
|
|
Post by wjhupp on Aug 11, 2018 21:27:56 GMT
If you think a change is inevitable to clarify, I would vote for simplifying the process. I can't see any historical based argument that would decide the issue.
Would it hurt anything to just do it sequentially to make it the same as close combat?
Just elimnate the ability of the non-bound player to change the bound player's initiative. You could still have the bounding player who fires at a shooting element have to to direct it's defending fire at anything shooting at it.
Per the example (which does not have anybody in a shooters TZ) a) the Red Bw 1 (who’s bound it is) picks a target, and decides on the Blue Cv; Roll the die; keep the die roll for Bw 1, Blue Cv reacts to the shooting; b) the Blue Bows (which must shoot at something) can pick either the Red Kn or the Red Bw... c) if one of the Blue Bows shoots at the Red Bw, use the die roll that Bw 1 used in a) d) if Red Bw 1 (who’s bound it is) picks a Red Bw, then Red Bw must reply with support
The non-bound player can see the impact of Red Bw 1 when he makes his choice in b). IMHO that is equal to or offsets the advantage of the bound player deciding the order.
I might just make this our house rule or what I teach new players, as trying to coach someone on the current situation would be a negative in getting someone to like the game. (Don't shoot me :-) ...Just speaking from experience teaching new players here.)
Bill
|
|
|
Post by bob on Aug 11, 2018 23:41:34 GMT
Now I will make my shot at it (no pun intended of course). I told Phil that this third-party shooting rule was too complicated but he really wanted it because he was upset with situations where A would shoot at B but then C wanted to shoot a A. This called for a double Shooting situation.
So in 3, We have, “If a shooter whose target does not shoot back is shot at by a third party, this is resolved first, then it shoots using the same dice score.” shooter = Bw 1. Target = Cv. 3rd party = Bw 2 (with 3. if desired ). “it” = Bw 1
Bw 1 is ordered to shoot at Cv. Bw 2 player calls for “Third-party shooting“. A die is rolled for Bw 1 FOR DEFENSE ONLY. A die is rolled for Bw 2, with support from three if so desired. The outcomes are compared. Nothing bad happens to Bw 2. Bow 1 could have no effect, be recoiled, or be destroyed. If Bw is still there and in range, a die is rolled for the Cv And compared to the die rolled for Bw 1 verses Bw 2 (“using the same die score” ). Any outcome applied to the cavalry is now implemented.
So, Bw 1 shoots at a target that does not shoot back, is shot at by 3rd party, this is resolved first, and then Bw 1 shoots at original target with same die, if able.
|
|
|
Post by lkmjbc on Aug 12, 2018 0:39:59 GMT
Hello Joe
I am being a pessimist, but it is what I have seen going on for years.
Practically all the WRG rules have gone the same way, new version after new version, each adding complication.
But now is the time to do something about it, not ten years time, and not just over shooting or wrong army lists. Make the rules understandable by a twelve year old, everything has a place, everything in its place.
Change it or loose it.
David Constable
P.S. - Where are the future players coming from, what will they be interested in? Yes, I think you are too pessimistic. Your advice however is quite wise. To answer your last question...I think Tom has that puzzled out. Joe Collins
|
|
|
Post by stevie on Aug 12, 2018 0:54:53 GMT
NowI will make my shot at it (no pun intended of course). I told Phil that this third-party shooting rule was too complicated but he really wanted it because he was upset with situations where A would shoot at B but then C wanted to shoot a A. This called for a double Shooting situation. So in 3, We have, “If a shooter whose target does not shoot back is shot at by a third party, this is resolved first, then it shoots using the same dice score.” shooter = Bw 1. Target = Cv. 3rd party = Bw 2 (with 3. if desired ). “it” = Bw 1 Bw 1 is ordered to shoot at Cv. Bw 2 player calls for “Third-party shooting“. A die is rolled for Bw 1 FOR DEFENSE ONLY. A die is rolled for Bw 2, with support from three if so desired. The outcomes are compared. Nothing bad happens to Bw 2. Bow 1 could have no effect, be recoiled, or be destroyed. If Bw is still there and in range, a die is rolled for the Cv And compared to the die rolled for Bw 1 verses Bw 2 (“using the same die score” ). Any outcome applied to the cavalry is now implemented. So, Bw 1 shoots at a target that does not shoot back, is shot at by 3rd party, this is resolved first, and then Bw 1 shoots at original target with same die, if able. That is a plausible sequence of events Bob... ...but it does mean throwing out one of the shooting priorities given on page 10 paragraph 4, so that it reads:- “Bows and War Wagons must shoot at a target in their TZ. If there is none, they must shoot at a target that is shooting at them. Otherwise, they can choose any eligible target”. Or shall we instead play DBA 3.0 the way that Phil Barker intended, without leaving out chunks of his rules just because we find them inconvenient? Some potentially useful player aids can be found here, such as the “Quick Reference Sheets” from the Society of Ancients, and the new “Army List Corrections” file: fanaticus-dba.wikia.com/wiki/Category:Reference_sheets_and_epitomes And this is the latest January 2018 FAQ: fanaticus-dba.wikia.com/wiki/FAQ_2018
|
|
|
Post by bob on Aug 12, 2018 16:47:02 GMT
Phil intended the Third Party Rule to be played was written. In older versions, Bow 1 would shoot at the Cavalry, and then Bow 2 would shoot at Bow 1. Two different combats, each with its own die roll. This new rule eliminates that. Bow 1 chooses to shoot at the Cavalry. It could have shot at B2 which would have to shoot back. If it were the bound of Bow 2, it could target Bw 1, which would have to shoot back. The target of Bow 1 is the cavalry, so the target is not shooting back. Bow 1 is willing to gamble that it can withstand the +2 shooting of Bow 2 and even the -1 of Bow 3, , and then get a nice +4 vs Cavalry. Bow 1 shoots at Cavalry, Bow 2 player interrupts with the TPS, to shoot at Bow 1. Bow 1 can not shoot back as it is shooting at the Cavalry. This Bow 1 takes a shot, and rolls a defensive die. NO HARM CAN COME TO BOW 2. If Bow 1 is still there and in range, it finishes its shot at Cavalry, with the same die it rolled in defense against Bow 2. Once the Bow 1 player commits to shooting the cavalry, he cannot change his mind and take an offensive shot at Bow 2. This is again a clever rule by Phil. There is only 1 die roll for each player. Stevie, I know this is a difficult rule to understand, it took me a long time too, but please play the game as Phil intended, do not leave out the chunk of the Third Party Rule. I would like to, as I preferred the older double shot process, but I got over ruled By the way for people who are looking at Figure 15b, note that the FAQ has fixed the error there. "15b. The second sentence under “Third Party shooting:” should read, “If Bow A is still able to shoot after this has been resolved, Bow A may shoot at its original target.” The FAQ team understood, that the shooter takes a shot from the Third Party and after this is resolved, the shooter goes back to the original target.
|
|
|
Post by stevie on Aug 12, 2018 23:18:08 GMT
Actually Chaotic, “no harm can come to bow 2” is already written in the rules. It is under 'Combat Outcomes' on page 11 paragraph 4:- “An element shooting without being shot at disregards an unfavourable outcome”. And Bob, I do understand your point of view, but we (or at least I) may be talking at cross-purposes here. The issue is not with ‘Third Party Shooting’, but with ‘Shooting Priorities’. The Red Bow 1 may well like to shoot at the Blue Cv... ...but if the Blue Bow 2 decides to target Red Bow 1, then Red Bow 1 must shoot back at Blue Bow 2. Therefore, Red Bow 1 cannot shoot the Blue Cv. This is because of page 10 paragraph 4, which quite clearly states:- “ (Bw and WWg with no enemy in their TZ) must shoot at a target that is shooting at them.” I can actually see these words. We all can. No ifs...no buts...and no exceptions. When you are shot at, you must shoot back (if you can). To have Red Bow 1 shooting at the Blue Cv, while it is currently being shot at by Blue Bow 2, breaks this shooting priority rule. And the rules clearly say this is not allowed. (However, only if Red Bow 1 were unable to shoot back at Blue Bow 2, because it was not quite facing in the right direction, would that be a ‘Third Party Shooting’ situation as you described. But that is not the case in the picture on the first page of this thread. It CAN shoot back, and if targeted it MUST do so)
Some potentially useful player aids can be found here, such as the “Quick Reference Sheets” from the Society of Ancients, and the new “Army List Corrections” file: fanaticus-dba.wikia.com/wiki/Category:Reference_sheets_and_epitomes And this is the latest January 2018 FAQ: fanaticus-dba.wikia.com/wiki/FAQ_2018
|
|
|
Post by wjhupp on Aug 12, 2018 23:48:28 GMT
I agree with Bob and so it should be:
Per the example (which does not have anybody in a shooters TZ) a) the Red Bw 1 (who’s bound it is) picks a target, and decides on the Blue Cv; Roll the die; keep the die roll for Bw 1, Blue Cv reacts to the shooting but only if Blue Bw do not shoot Red Bw b) the Blue Bows (which must shoot at something) can pick either the Red Kn or the Red Bw... c) if one of the Blue Bows shoots at the Red Bw, use the die roll that Bw 1 used in a) and resolve this combat first as 'third party shooting'; d) Blue Cv reacts to the shooting if still applicable after c)
if Red Bw 1 (who’s bound it is) picks a Blue Bw, then Blue Bw must reply with support
Clarifying the interruption of third party shooting helped me there. It is still a bit complicated so I am not that sure about keeping the one die roll, but I can live with it. But if we forget it I am not too concerned.
Bill
|
|
|
Post by stevie on Aug 13, 2018 0:42:24 GMT
That is fine Wjhupp...but it’s not what the rules say:- So, Bw 1 shoots at a target that does not shoot back, is shot at by 3rd party, this is resolved first, and then Bw 1 shoots at original target with same die, if able. That is a plausible sequence of events Bob... ...but it does mean throwing out one of the shooting priorities given on page 10 paragraph 4, so that it reads:- “Bows and War Wagons must shoot at a target in their TZ. If there is none, they must shoot at a target that is shooting at them. Otherwise, they can choose any eligible target”. Or shall we instead play DBA 3.0 the way that Phil Barker intended, without leaving out chunks of his rules just because we find them inconvenient?
After all, the shooting priorities given in page 10 paragraph 4 are there for a reason... Anyway, it would be a bit harsh on the poor Red Bow 1 if they have to make their combat roll BEFORE the Blue player has decided who he want's to shoot at. (If the Red Payer rolled a low score, the Blue Player would get a pretty good idea that his Blue Cv will be safe, so knowing what the score is in advance he could go and target something else instead. Likewise, if Red gets a high score, the Blue Player could decide to draw their fire by shooting a bow at them, with support shooting if that would be enough to lower the final score to avoid being doubled.)Some potentially useful player aids can be found here, such as the “Quick Reference Sheets” from the Society of Ancients, and the new “Army List Corrections” file: fanaticus-dba.wikia.com/wiki/Category:Reference_sheets_and_epitomes And this is the latest January 2018 FAQ: fanaticus-dba.wikia.com/wiki/FAQ_2018
|
|
|
Post by bob on Aug 13, 2018 1:36:03 GMT
The whole purpose of the Third Party Shooting rule is to allow a shooter to shoot at an enemy of its own choice, when priorities are not in effect. And for that shooter to still be shot at by a third party.
The Bow 1 player chooses to shoot at the cavalry. It is not being shot at when that choice is made. The Bow 2 player trumps the Bow 1 by calling in the TPS rule, and takes a shot at the Bow 1. This does not change the target of Bow 1.
The Bow 2 player cannot stop Bow 1 from shooting at the Cavalry by shooting at it. Bow 1 gets to shoot at the cavalry but must defend against Bow 2.
In the older rules, Bow 1 would shoot at the Cavalry and then Bow 2 would shoot at Bow 1. Two combat rolls. No harm to Bow 2, as Bow 1 has "shot its wad," only one shot allowed. Phil wanted a player to be able to shoot at target of choosing, but face a penalty of being shot at first. And he wanted only one die roll for the original shooter.
when Bow 1 decides to shoot at the Cavalry, IT IS NOT BEING SHOT AT. It is only after it shoots at the cavalry, that it is shot at. It cannot shoot at two targets, and the Bow 2 player cannot change the target of Bow 1. "Hey I am shooting at you so you cannot shoot at the cavalry, you must shoot at me." No, 2 cannot make 1 change its target.
A shooter must shoot back at an element that IS shooting at it. Not at one that could shoot at it. Bow 1 does not need to shoot at Bow 2 just because it COULD shoot at it.
Bow 1 player declares it is shooting at Cavalry, the fact that Bow 2 player becomes a third party shooter cannot prevent Bow 1 from shooting at cavalry. To make things consistent, the applies in all situations of a shooter picking a target that cannot shoot back and then being shot at while shooting at original target.
|
|
|
Post by chaotic on Aug 13, 2018 1:45:49 GMT
Actually Chaotic, “no harm can come to bow 2” is already written in the rules. It is under 'Combat Outcomes' on page 11 paragraph 4:- “An element shooting without being shot at disregards an unfavourable outcome”. Some potentially useful player aids can be found here, such as the “Quick Reference Sheets” from the Society of Ancients, and the new “Army List Corrections” file: fanaticus-dba.wikia.com/wiki/Category:Reference_sheets_and_epitomes And this is the latest January 2018 FAQ: fanaticus-dba.wikia.com/wiki/FAQ_2018
Thanks! I missed that.
|
|
|
Post by bob on Aug 13, 2018 1:51:08 GMT
I agree with Bob and so it should be: Per the example (which does not have anybody in a shooters TZ) a) the Red Bw 1 (who’s bound it is) picks a target, and decides on the Blue Cv; Roll the die; keep the die roll for Bw 1, Blue Cv reacts to the shooting but only if Blue Bw do not shoot Red Bw b) the Blue Bows (which must shoot at something) can pick either the Red Kn or the Red Bw... c) if one of the Blue Bows shoots at the Red Bw, use the die roll that Bw 1 used in a) and resolve this combat first as 'third party shooting'; d) Blue Cv reacts to the shooting if still applicable after c) if Red Bw 1 (who’s bound it is) picks a Blue Bw, then Blue Bw must reply with support Clarifying the interruption of third party shooting helped me there. It is still a bit complicated so I am not that sure about keeping the one die roll, but I can live with it. But if we forget it I am not too concerned. Billd. Good Bill, but lets clarify. a. as you write, but roll no dice yet. b. Blue does not roll for Cavalry, but instead says he will shoot at Bow 1, using the TPS rule. 3 will assist. This is resolved first. c. Now roll dice. No effect on Bow 2 as Bow 1 is just defending, just as if the target were a Blade, no return shooting d. If Bow 1 is still there and still in range, then Blue rolls for the cavalry and Red uses the same die it rolled for the defending against Blue bows. The rule clearly says that the Red player must use the same die for both combats. "If a shooter whose target does not shoot back is shot at by a third party, this is resolved first, then it shoots using the same dice score." This was one of Phil's primary concerns for this rule. Only throw one die for each player. If Blue bound and Bow 2 shoots at Kn, then Red can claim TPS.
|
|
|
Post by stevie on Aug 13, 2018 4:28:43 GMT
Bob me old matey, I have found the solution to this shooting dilemma! ...but you are not going to like it I’m afraid. Figure 15b: Distant Shooting dialogue, paragraph 2:-“Although Pike X presents a target of less than ½ BW, Bow A can shoot at all of one edge and must do so because targets within the shooters TZ always take priority.” (Not relevant in Tony Aguilar’s picture, as the Blue Cv is outside of the Red Bow 1 Threat Zone)Figure 15b: Distant Shooting dialogue, paragraph 3:-“If Pike X was a little further away outside the TZ, Bow A would (i.e. must) shoot at Bow Y because a target that shoots back takes priority over one that does not.” (This is relevant...the Blue Cv is not shooting at Red Bow 1, but Blue Bow 2 is, and that takes priority. So Red Bow 1 cannot shoot at the Blue Cv but must shoot back at Blue Bow 2, even if the Red Player had announced his intention to shoot at the Cv. In other words, the Red Player’s choice of target has been vetoed by the need to shoot back at the Blue Bow, but only if a Blue bow does announce it's intention to shoot at Red Bow 1)Figure 15b: Third Party Shooting, last paragraph:-“In the above diagram Bow A shoots at Pike X (compulsory, it’s in the TZ) but, before that is resolved, Bow Y must first shoot at Bow A as a third party shot.” (In other words, Bow A is unable to shoot back at Bow Y because the Pike in it’s TZ takes priority...that’s why it’s a Third Party Shot. Third Party Shots are forced on players that are unable to reply, not by choice)Lastly, at the very bottom, “This sequence is followed regardless of whose bound it is.” (So the bounding player cannot use the ‘Third Party mechanism’ to bypass, override, or ignore the ‘Shooting Priorities’)Some potentially useful player aids can be found here, such as the “Quick Reference Sheets” from the Society of Ancients, and the new “Army List Corrections” file: fanaticus-dba.wikia.com/wiki/Category:Reference_sheets_and_epitomes And this is the latest January 2018 FAQ: fanaticus-dba.wikia.com/wiki/FAQ_2018
|
|