I understand that if a prox mine is dropped on an opponent's ship it detonates immediately. I also know that if two ships are covered by the prox mine the player owning the mine has a choice of which ship is affected. Does this still apply if one of the ships affected by the mine belongs to the faction dropping the mine?
A funny thing happened when the prox mine dropped.
I want to say yes...
54 minutes ago, Innese said:I want to say yes...
You should, because it's the right answer. ![]()
Why wouldn't it?
1 hour ago, Stoneface said:I understand that if a prox mine is dropped on an opponent's ship it detonates immediately. I also know that if two ships are covered by the prox mine the player owning the mine has a choice of which ship is affected. Does this still apply if one of the ships affected by the mine belongs to the faction dropping the mine?
Yes, the reference card does not state what faction or ship the player belongs to. If you drop a proxy mine on two or more ships belonging to any player, the person dropping the mine decides which ship takes the dice roll.
31 minutes ago, Tritoxin said:Yes, the reference card does not state what faction or ship the player belongs to. If you drop a proxy mine on two or more ships belonging to any player, the person dropping the mine decides which ship takes the dice roll.
That kind of sucks. There should be some penalty for dropping a prox on one of you own. This wasn't a problem initially.
18 minutes ago, Stoneface said:That kind of sucks. There should be some penalty for dropping a prox on one of you own. This wasn't a problem initially.
You've got to remember that Proximity Mines are "dumb" weapons. They don't care what faction the ship that triggers them belongs to. They'll damage the first ship that comes along.
The fact that you get to choose the target when more than one ship is involved, is the problem. It should probably have been a dice roll to decide instead of player choice. But that's the rule.
28 minutes ago, Parravon said:The fact that you get to choose the target when more than one ship is involved, is the problem.
Even that isn't a problem since the maneuvers in x-wing represent the overall net change in position and not a specific, unvarying flight path. If you drop a mine template on two ships and you want it to have hit A and not B it just means you dropped it at a point during your maneuver when you were angled properly to hit A instead of B.
2 minutes ago, Forgottenlore said:Even that isn't a problem since the maneuvers in x-wing represent the overall net change in position and not a specific, unvarying flight path. If you drop a mine template on two ships and you want it to have hit A and not B it just means you dropped it at a point during your maneuver when you were angled properly to hit A instead of B.
Yeah, I suppose that's a pretty reasonable way to explain it.
The Prox mine and Conner are the only two bombs that offer the dropping player a choice. Everything else has a blast radius with the exception of the Cluster Mine and it doesn't have the option of choosing which ship to hit.
Forgottenlore's explanation seems like the best way to understand the effect.
3 minutes ago, Stoneface said:The Prox mine and Conner are the only two bombs that offer the dropping player a choice. Everything else has a blast radius with the exception of the Cluster Mine and it doesn't have the option of choosing which ship to hit.
Forgottenlore's explanation seems like the best way to understand the effect.
Nope, Cluster Mines do as well. If you manage to hit two ships with the same mine you'd decide which one triggered it.
Unless you've got a rules reference to suggest otherwise.
10 minutes ago, thespaceinvader said:Nope, Cluster Mines do as well. If you manage to hit two ships with the same mine you'd decide which one triggered it.
Unless you've got a rules reference to suggest otherwise.
So yor saying if I drop a cluster mine and two different ships are hit by two different segments of the mine, I get to choose which one actually detonates? Now that seems a little odd.
No.
If you drop a cluster mine and two (or more) different ships are hit by the same individual segment, you choose which one is hit.
18 minutes ago, thespaceinvader said:No.
If you drop a cluster mine and two (or more) different ships are hit by the same individual segment, you choose which one is hit.
Ok, gotcha. I was reading your response as the whole CM and not an individual segment. That makes sense now.
10 hours ago, Stoneface said:That kind of sucks. There should be some penalty for dropping a prox on one of you own. This wasn't a problem initially.
What wasn't a problem? You could have dropped a mine and had it land one one of your and one of theirs although I guess the question of which ship suffered the blast came down to which ship when next. It's better the way it is now.
1 minute ago, StevenO said:What wasn't a problem? You could have dropped a mine and had it land one one of your and one of theirs although I guess the question of which ship suffered the blast came down to which ship when next. It's better the way it is now.
I might be wrong but when prox mines first came out, they didn't detonate immediately when dropped on a ship., correct? It was based on movement. That was changed to fix some oddities in ship positions and movement when the mine was dropped on a ship.
Now there's no drawback to dropping a prox on your ship and an opponent's ship.
At the time I think I viewed "Yeah if you drop them on top of a ship they go off right away" as a clarification rather than a change. After all, they detonate as soon as a ship's base or maneuver template overlaps them (and if memory serves it was always worded that way), and hey look! It's already happening!
On 3/24/2017 at 11:30 AM, thespaceinvader said:Nope, Cluster Mines do as well. If you manage to hit two ships with the same mine you'd decide which one triggered it.
Unless you've got a rules reference to suggest otherwise.
Got into a discussion Thursday night about whether Cluster Mines detonate if dropped on a ship. My opponent said they didn't I thought they did and remembered this thread. I couldn't find an FAQ listing for it but did find the one for the Prox mine. Could you point me in the direction of your reference for future use?
There may not be one , but that doesn't stop it being the case.
It's a bomb that detonates on overlap, so if it drops onto a ship, it detonates. That's the rules for how bombs that detonate on overlap work.
6 hours ago, thespaceinvader said:There may not be one , but that doesn't stop it being the case.
It's a bomb that detonates on overlap, so if it drops onto a ship, it detonates. That's the rules for how bombs that detonate on overlap work.
That's gonna be a problem. If I'm to convince this guy it does, it's got to be in black and white. There are FAQ entries for the Conner Net and Prox Mine but nothing about CMs.
1 hour ago, Stoneface said:That's gonna be a problem. If I'm to convince this guy it does, it's got to be in black and white. There are FAQ entries for the Conner Net and Prox Mine but nothing about CMs.
The sections of the Cluster Mines and Proximity Mine upgrade cards that describe how the tokens detonate have exactly the same wording (after applying the Prox Mine errata, anyway). There is no reason to assume they mean them to operate differently, which is why Cluster Mines doesn't have its own FAQ entry.
Conner Net has its own FAQ entry specifically because overlap-detonate bomb tokens detonate immediately if dropped on a ship, which caused some timing problems with Conner Net's non-damage effects.
31 minutes ago, digitalbusker said:The sections of the Cluster Mines and Proximity Mine upgrade cards that describe how the tokens detonate have exactly the same wording (after applying the Prox Mine errata, anyway). There is no reason to assume they mean them to operate differently, which is why Cluster Mines doesn't have its own FAQ entry.
Conner Net has its own FAQ entry specifically because overlap-detonate bomb tokens detonate immediately if dropped on a ship, which caused some timing problems with Conner Net's non-damage effects.
I noticed the wording on the card. Hopefully this will be good enough.
Thanks!