Traditionally in Sci-Fi when dealing with either no genders, or more then one, the proper pronouns to use is him or he, and the proper title is Sir.

Did anyone notice this:

"Echo"

When declaring a decloak, the player controlling

“Echo” must declare both the side and direction

of the decloak. If “Echo” can perform the

decloak, she must do so. If “Echo” cannot

perform the decloak, the player controlling

“Echo” may declare a decloak in any other

direction, or he may choose not to decloak.

Not only is Echo a "she", but this puts it to rest for Lorrir and Echo that direction and side constitute the movement.

Interesting that you were quick to point out 'she', but in the in the very next sentence it reverts to 'he'. Obvious typo, but which one is correct? I don't care which gender Echo is, but it would be nice to see a few more female pilots... What I do care about is consistency. Sort it out FFG!

Did anyone notice this:

"Echo"

When declaring a decloak, the player controlling

“Echo” must declare both the side and direction

of the decloak. If “Echo” can perform the

decloak, she must do so. If “Echo” cannot

perform the decloak, the player controlling

“Echo” may declare a decloak in any other

direction, or he may choose not to decloak.

Not only is Echo a "she", but this puts it to rest for Lorrir and Echo that direction and side constitute the movement.

Interesting that you were quick to point out 'she', but in the in the very next sentence it reverts to 'he'. Obvious typo, but which one is correct? I don't care which gender Echo is, but it would be nice to see a few more female pilots... What I do care about is consistency. Sort it out FFG!

The 'he' is the player controlling Echo, not Echo...

Did anyone notice this:

"Echo"

When declaring a decloak, the player controlling

“Echo” must declare both the side and direction

of the decloak. If “Echo” can perform the

decloak, she must do so. If “Echo” cannot

perform the decloak, the player controlling

“Echo” may declare a decloak in any other

direction, or he may choose not to decloak.

Not only is Echo a "she", but this puts it to rest for Lorrir and Echo that direction and side constitute the movement.

Interesting that you were quick to point out 'she', but in the in the very next sentence it reverts to 'he'. Obvious typo, but which one is correct? I don't care which gender Echo is, but it would be nice to see a few more female pilots... What I do care about is consistency. Sort it out FFG!

The 'he' is the player controlling Echo, not Echo...

Wait, so now you can only play echo if you're a dude?

The main point was both Advanced Sensors and Decloak use the word "immediately" when referring to the timing relative to revealing your dial so you can't perform an action and then do something else and then have the dial be "immediately" revealed after the action (as required by Adv Sens)

This is a very scary precedent to draw. You're basically saying that any trigger can only have one "immediately". That's both dangerous and completely unfounded to draw from such a specific ruling.

I can come up with at least three different possible underlying rules that would lead to this result. The fact that you preferred one of them and the ruling lined up with your expected result does not make your preferred underlying rule correct.

I understand correlation does not equal causation but that was just the only reasoning I came up with way back (before the AoIA events) and it wasn't as much of a "It has to be ruled this way" as much of a "it leaves them wiggle room if they want to rule it this way" and also as a justification for why Decloak, Cloak, Decloak again crap wouldn't work (yes I know there are other rules that would prohibit this but people still thought it would be doable for some weird reason) Of course this ruling also means we don't have to worry about that coming up either

Personally I would like to see what your reasons are because I can't really come up with any others off the top of my head quickly.

Would people stop saying the missiles magically didn't fire, that's ridiculous.

While it is a game, and a sci-fi game to boot, I don't think anybody really believes MF returns missiles to their tubes. The whole concept is patently impossible. But if we're going to try and figure it out beyond the in game effect that is generally very well received, it is nearest to either:

A) having never fired the missiles at all due to seeing the target ship effectively "shake" the target lock.

or

B) having fired them and there simply being more in the tubes to begin with since, in universe and real life, fighters carry more than a single warhead. Since coming up with a mechanic that reflected that but also avoided assigning multiple ordinance cards/new ordinance counter tokens to an already cluttered table would be cumbersome, FFG just made it one card. MF simply wraps the whole issue up in 1 card, allowing for presumed multiple secondaries but not infinite. As far as Flechette torpedoes go, I imagine it's just the stress of seeing the flak nearby. In WWII flak was just as much a psychological weapon as a material one. Seeing the explosion go off, which by definition meant it hadn't struck you, still told you that you were under fire with a projectile that 'shotgunned' damaging debris in the area -- an area you shared.

I agree and disagree here...

Yes there could still be more missiles in the tubes.. but then shouldn't ordnance be multi use?? This is where I feel the cart goes off the rails. Bombers have multiple slots for torps and missiles..

Missiles and torps are one use cards.. the shoot off all the missiles or torps to gain the damage... MF basically is saying if it doesn't hit.. well if it doesn't hit why would it stress your ship.. yes I understand about flak in WWII but as you said.. this is a sci fi game, but some rules don't make sense. To me, if an attack doesn't hit, you shouldn't suffer any effects. Like Assault missiles.. no hit, no splash...

Obviously I will follow the ruling on it, but it still seems wrong to me.. that's all.. we each see things differently, and I do see what you are getting at, but I also disagree with that view. A miss, is a miss.

The main point was both Advanced Sensors and Decloak use the word "immediately" when referring to the timing relative to revealing your dial so you can't perform an action and then do something else and then have the dial be "immediately" revealed after the action (as required by Adv Sens)

This is a very scary precedent to draw. You're basically saying that any trigger can only have one "immediately". That's both dangerous and completely unfounded to draw from such a specific ruling.

I can come up with at least three different possible underlying rules that would lead to this result. The fact that you preferred one of them and the ruling lined up with your expected result does not make your preferred underlying rule correct.

I understand correlation does not equal causation but that was just the only reasoning I came up with way back (before the AoIA events) and it wasn't as much of a "It has to be ruled this way" as much of a "it leaves them wiggle room if they want to rule it this way" and also as a justification for why Decloak, Cloak, Decloak again crap wouldn't work (yes I know there are other rules that would prohibit this but people still thought it would be doable for some weird reason) Of course this ruling also means we don't have to worry about that coming up either

Personally I would like to see what your reasons are because I can't really come up with any others off the top of my head quickly.

1. "Immediately" only allows a single effect (your idea)

2. Everything declares simultaneously based on the trigger, and must be valid at that time. When the trigger occurs you have no decloak token, so you can't decloak.

3. Can't cloak/decloak in the same phase

(1) and (2) both have implications outside the cloak ruling. (3) is limited to the cloaking ruling, but far less based in the rules.

1. "Immediately" only allows a single effect (your idea)

2. Everything declares simultaneously based on the trigger, and must be valid at that time. When the trigger occurs you have no decloak token, so you can't decloak.

3. Can't cloak/decloak in the same phase

(1) and (2) both have implications outside the cloak ruling. (3) is limited to the cloaking ruling, but far less based in the rules.

Hmm (3) I don't see in the Cloak/Decloak reference cards (if its in the FAQ i may have missed it). (2) Though would probably be the most likely reason and as for Implications outside of cloaking probably would probably make the most sense and be the easiest to make another ruling off of

So let me get this straight, after several lengthy forums about whether or not ships are considered range 1 of themselves and whether a ship considers itself friendly with itself, they didn’t clarify it in the FAQ?

Yes I am aware of the answer that was provided by Frank Brooks but it would have been good to have it in the FAQ rather than hidden in a forum post collecting dust in the Rules questions forum.

Edit: yet they felt the need to put an entire section in regarding a extremely narrow corner case where Coran Horn Kills Fel Wraith in the end phase.

So let me get this straight, after several lengthy forums about whether or not ships are considered range 1 of themselves and whether a ship considers itself friendly with itself, they didn’t clarify it in the FAQ?

Yes I am aware of the answer that was provided by Frank Brooks but it would have been good to have it in the FAQ rather than hidden in a forum post collecting dust in the Rules questions forum.

Edit: yet they felt the need to put an entire section in regarding a extremely narrow corner case where Coran Horn Kills Fel Wraith in the end phase.

I'm sure they will resolve that question in the first FAQ after Rebel Aces releases. They haven't FAQed unreleased cerds in the past and there is no reason to believe that the Jan crew questions won't get answered when the card is actually available.

1. "Immediately" only allows a single effect (your idea)

2. Everything declares simultaneously based on the trigger, and must be valid at that time. When the trigger occurs you have no decloak token, so you can't decloak.

3. Can't cloak/decloak in the same phase

(1) and (2) both have implications outside the cloak ruling. (3) is limited to the cloaking ruling, but far less based in the rules.

Hmm (3) I don't see in the Cloak/Decloak reference cards (if its in the FAQ i may have missed it). (2) Though would probably be the most likely reason and as for Implications outside of cloaking probably would probably make the most sense and be the easiest to make another ruling off of

Well, it's not in the cards. But neither (1) or (2) are printed anywhere either. That's kinda the point.

So let me get this straight, after several lengthy forums about whether or not ships are considered range 1 of themselves and whether a ship considers itself friendly with itself, they didn’t clarify it in the FAQ?

Yes I am aware of the answer that was provided by Frank Brooks but it would have been good to have it in the FAQ rather than hidden in a forum post collecting dust in the Rules questions forum.

Edit: yet they felt the need to put an entire section in regarding a extremely narrow corner case where Coran Horn Kills Fel Wraith in the end phase.

Two possible issues here...

Targeting Coordinator is our sole example for this, so it's kinda corner-case-y too. Jan isn't out yet, and they're very consistent in not ruling on unreleased cards (sadly).

But I think more than that, is a matter of timing. We got the email on this less than a week ago. It's entirely probable that it was too short notice to get into the production/editing/review cycle in time to release today, or at the very least wasn't considered important enough to risk pushing it.

Here's an interesting tidbit from the newest Standard Tournament rules:

"Note: Any new product released at Gen Con 2014 will not be legal for the

2014 North American Championship or Escalation tournament."

Would they have put that in there if there wasn't a new product being released at GenCon???

That's a reference to Rebel Aces. I predicted long ago that it would be available at GenCon.

So let me get this straight, after several lengthy forums about whether or not ships are considered range 1 of themselves and whether a ship considers itself friendly with itself, they didn’t clarify it in the FAQ?

Yes I am aware of the answer that was provided by Frank Brooks but it would have been good to have it in the FAQ rather than hidden in a forum post collecting dust in the Rules questions forum.

Edit: yet they felt the need to put an entire section in regarding a extremely narrow corner case where Coran Horn Kills Fel Wraith in the end phase.

Two possible issues here...

Targeting Coordinator is our sole example for this, so it's kinda corner-case-y too. Jan isn't out yet, and they're very consistent in not ruling on unreleased cards (sadly).

But I think more than that, is a matter of timing. We got the email on this less than a week ago. It's entirely probable that it was too short notice to get into the production/editing/review cycle in time to release today, or at the very least wasn't considered important enough to risk pushing it.

In regards to unreleased cards, to some extent this is possible but I don’t understand why they won't clarify these 2 issues outside of specific card rulings, these are fundamental clarifications of basic underlying rules of the game that really should just be a simple yes or no Answer.

In terms of timing I don’t buy it these 2 questions have been asked several times on both FFG forums and AFM forums at least 5-6 weeks ago with multiple vague answers from FFG so they have had ample time to clarify what I would have thought is a very simple clarification.

They clarified whether or not you can shoot at your own ships (No) why can't they tell us if a ship is range 1 of itself and friendly with itself, Simple stuff I would have thought.

Is a hermaphrodite a he or a she?

Yes.

Is a hermaphrodite a he or a she?

Yes.

:lol:

Golly...

And we've reached a new low...

Would people stop saying the missiles magically didn't fire, that's ridiculous.

While it is a game, and a sci-fi game to boot, I don't think anybody really believes MF returns missiles to their tubes. The whole concept is patently impossible. But if we're going to try and figure it out beyond the in game effect that is generally very well received, it is nearest to either:

A) having never fired the missiles at all due to seeing the target ship effectively "shake" the target lock.

or

B) having fired them and there simply being more in the tubes to begin with since, in universe and real life, fighters carry more than a single warhead. Since coming up with a mechanic that reflected that but also avoided assigning multiple ordinance cards/new ordinance counter tokens to an already cluttered table would be cumbersome, FFG just made it one card. MF simply wraps the whole issue up in 1 card, allowing for presumed multiple secondaries but not infinite. As far as Flechette torpedoes go, I imagine it's just the stress of seeing the flak nearby. In WWII flak was just as much a psychological weapon as a material one. Seeing the explosion go off, which by definition meant it hadn't struck you, still told you that you were under fire with a projectile that 'shotgunned' damaging debris in the area -- an area you shared.

I will also point out that every single missile and torpedo card is written as a plural. This means you are always firing multiple ordnance. In the case of Munitions failsafe, you didn't empty to whole rack. In the case of Flechette Torpedoes, enough went off to trigger stress, but no direct hit.

hmmm nothing about Whisper. So my belief that Whisper is a Hutt placed in the cockpit as a Huttling and grew up inside until it is to big to be removed STILL. HOLDS. WATER.

sunglasses

Did anyone notice this:

"Echo"

When declaring a decloak, the player controlling

“Echo” must declare both the side and direction

of the decloak. If “Echo” can perform the

decloak, she must do so. If “Echo” cannot

perform the decloak, the player controlling

“Echo” may declare a decloak in any other

direction, or he may choose not to decloak.

Not only is Echo a "she", but this puts it to rest for Lorrir and Echo that direction and side constitute the movement.

So, can the person decloaking measure before choosing the direction? Sounds like the answer is no.

So, can the person decloaking measure before choosing the direction? Sounds like the answer is no.

No premeasuring allowed. Declare how you wish to decloak and then see if it's possible to do so.

hmmm nothing about Whisper. So my belief that Whisper is a Hutt placed in the cockpit as a Huttling and grew up inside until it is to big to be removed STILL. HOLDS. WATER.

sunglasses

This?

http://starwars.wikia.com/wiki/Rotta

hmmm nothing about Whisper. So my belief that Whisper is a Hutt placed in the cockpit as a Huttling and grew up inside until it is to big to be removed STILL. HOLDS. WATER.

sunglasses

This?

http://starwars.wikia.com/wiki/Rotta

Exactly!!

Ive never been able to find the Resources link on this website, or where to get the FAQ or the Rules. Can someone point me that way?

I wanted to read the new rules today and found out that someones been duping my computer with bad website management.

Sorry if this has been asked already (haven't read entire thread), but does it seem strange to anyone that the rules about a huge ship's starting energy only applies to tournament games? Obviously, this can make quite a difference so why do huge ship's get an edge in tournament play but not in casual games?