Quick question.

When Oberos does a 3-5 range move, then he does his 90 degree turn for stress. Can he still boost with afterburners? I suspect yes, but not 100% certain.

Thanks in advance.

14 minutes ago, Chudley said:

Quick question.

When Oberos does a 3-5 range move, then he does his 90 degree turn for stress. Can he still boost with afterburners? I suspect yes, but not 100% certain.

Thanks in advance.

Both have the same trigger, so yes.

Both effects happen in the same timing window, and Afterburners doesn't care whether you're stressed, so you can resolve them in whatever order you choose. You can boost then rotate, or rotate then boost.

FFG has been contacted regarding this since there are differing opinions about it. I haven't had a response yet. It should work according to the rules of the ability queue but I've avoided playing Dalan because there are players arguing against it.

Same trigger, same timing, can resolve in either order.

2 minutes ago, eRADicator67 said:

FFG has been contacted regarding this since there are differing opinions about it. I haven't had a response yet. It should work according to the rules of the ability queue but I've avoided playing Dalan because there are players arguing against it.

...What is the argument against it? They literally have the exact same trigger.

I thought that would be the case. Stoopid Scum. We weren’t sure about the order, we thought that maybe you must complete the entirety of the card before going onto afterburners, but I had an inkling that the window of opportunity was any order.

10 minutes ago, nexttwelveexits said:

...What is the argument against it? They literally have the exact same trigger.

Dalan Oberos executes a maneuver > use Afterburners > Afterburners is not a maneuver so Dalan cannot rotate 90 degrees. I have no issue with this logic and I was on this side of the argument before going over the ability queue again. The ability queue allows it but there are people who get upset when the rules do funky things like allow some really nice shenanigans.

I want clarification so I can point to an FAQ that says the ability queue works like this rather than having a silly argument. Guys get really loud over rules issues.

They both have the same trigger and come from the same ship, so they go on the ability queue at the same time. You choose the order to place them on the ability queue. They'll then resolve off the ability queue according to the normal rules.

Also note that they go on the queue whether you want them to or not. But, because they are both "may" abilities, you can choose to do nothing when they resolve. What this means is that you have to choose which order to do them in right away, but you don't have to choose to do the second one at all until after you complete the first one. This is handy if you land somewhere you don't expect.

Without any further complications messing about with your queue, the net effect is that you can do both things in any order you like and you get to see the result of the first one before you choose to do the second.

47 minutes ago, eRADicator67 said:

Dalan Oberos executes a maneuver > use Afterburners > Afterburners is not a maneuver so Dalan cannot rotate 90 degrees. I have no issue with this logic and I was on this side of the argument before going over the ability queue again. The ability queue allows it but there are people who get upset when the rules do funky things like allow some really nice shenanigans.

I want clarification so I can point to an FAQ that says the ability queue works like this rather than having a silly argument. Guys get really loud over rules issues.

The rules reference for the ability queue, on page 3:

Quote

2. If a player has multiple abilities that triggered from the same event, that player chooses the order that those abilities are added to the ability queue.

I'm really not sure how that could be made more clear. Dalan + Afterburners are two abilities (one pilot ability, one upgrade ability) triggered from the same event and added to the queue in whatever order the player wants and then resolved accordingly. Anyone who thinks it doesn't work that way isn't making an argument so much as they're having a tantrum.

Honestly, I'm not trying to put anyone down when I say that. I understand people having different interpretations of the same rule, but there's no wiggle room here. It's straightforward and clear.

In reading through these forums over the last few weeks, I get the sense that a lot of people are confused by the ability queue system. Not because it's unclear or imprecise in any way, but just because there's a lot there and it's not how the game usually "feels" like it's played. (Of course, everything actually goes through the ability queue, but we don't tend to think about it at all until it's relevant.)

I don't think it needs any more re-wording or clarification from FFG, but it might make sense for us -- as a community -- to add some more examples, diagrams, teaching aids, and what-have-you to the second edition Wikia or something. Just to help our fellow players (especially the new ones) get to grips with how the ability queue works.

If you’ve ever played Magic, think of the Ability Queue like the Stack. There is a timing window that triggers an ability (or abilities), you place them on the queue as you wish, they resolve.

1 minute ago, Innese said:

If you’ve ever played Magic, think of the Ability Queue like the Stack  .

And if you're a computer scientist, don't get confused by that fact that "queue" and "stack" are opposites. ?

Both are just a list of things that are going to happen at some point in the near future. With rules for where things get added to the list or removed from the list.

1 minute ago, jftanner said:

And if you're a computer scientist, don't get confused by that fact that "queue" and "stack" are opposites. ?

Both are just a list of things that are going to happen at some point in the near future. With rules for where things get added to the list or removed from the list.

Yep, and the "ability queue" adds new abilities to the front of the queue just like a stack and nothing like a queue. ?

Just now, joeshmoe554 said:

Yep, and the "ability queue" adds new abilities to the front of the queue just like a stack and nothing like a queue. ?

Except for sometimes, when it adds to the back of the queue like it's supposed to.

... and we wonder why the ability queue is confusing.