Search options (Page 1 of 4)

When you click on "Find users who need it," then it automatically fills in the "edition" tag wit the latest "core" printing (when there is one, or the latest edition period if it's only ever been printed in supplemental products like Containment Priest or Command Tower) but, and this is the important bit, doesn't actually use that as part of the search criteria. So it's finding all 21 users who say they want Containment Priest, regardless of edition.  But when you click "apply" then the "edition" tag is already filled in so it gets applied to the search results this time and only shows the six people who specifically want that edition.

This has got to be a bug, and I think it was alluded to in another recent thread but I'm not sure they saw exactly what was going on, either.  The solution is, of course, to either leave the "edition" tag blank when the page first loads, or to actually filter by the edition since it was selected.  Personally, I'd prefer the first option.  If you fill in an edition, you're limiting the search results to people who specify they want that edition, even if it's the only one there is.  With Containment Priest, for example, all 21 people who want it want the C14 version, because that's the only one there is, but if you only look for people who say they want the C14 version then you'll only hit six of them.  The other fifteen people are left out of the search, even though they should be perfectly valid hits.

This brings up another issue...if you search for people who need a particular card, and you fill in edition for the search, then it should return people who want "unknown edition" (i.e. they don't care what one it is) as well.  Most of the time you're not necessarily asking "who's looking for M10-edition Lightning Bolts, specifically?" for example, you're actually saying "I've got this Lightning Bolt for trade, it's from M10, who wants it?"  Those might seem like the same question, but if one guy wants "M10 edition Lightning Bolt" and another guy wants "any old Lightning Bolt you have", then they actually both want my Lightning Bolt from M10, even though the other guy didn't necessarily say so.  Limiting the search to people who want a specific edition, just because I filled in what edition my card was from (to avoid the third guy, who's only interested in ABU Lightning Bolts) isn't helping anyone find any trade partners.

The postmaster says they don't know where it is.  That's not the same as saying it wasn't delivered.  All that means is that they can't find it because they don't have it anymore.  One reason why they wouldn't have it might be because they delivered it already.  Considering that that's what the tracking info says they did with it, you can see why, as outsiders not directly involved in the dispute, we might presume that that's what actually happened.

Yeah it is.  You should just call it "deckbox market price" or "price index" or something.  But whatever it is, if it's not an "average" of anything (as in add them all up and divide by how many there are) then you shouldn't call it that.

The key things to remember about priority are:
- At the start of most* steps and phases, or after a spell or ability resolves, the active player (person whose turn it is) receives priority first.
- After casting a spell or activating an ability, then by the game rules**, the player who had priority before casting the spell or activating the ability receives it again.
- Costs of spells or abilities (including adding/removal of loyalty counters from Planeswalkers) are paid "up front," during the casting or activation of the spell or ability, and not later when it resolves.

* (No player receives priority during the untap step, ever, and usually not during the cleanup step either, unless an ability triggers or state-based actions are performed.  In that case, players do receive priority after, but then there will be another cleanup step following that step, and then another and another, if necessary, until eventually there is a "clean" cleanup step wherein nothing triggers and no state-based actions are performed.)
** (In tournament play, there is a shortcut whereby it is presumed that the player is passing priority at this point, unless he or she specifically states that they are retaining it.)

False.  There's nothing "unique" about how Planeswalkers are cast or how their abilities are activated.  They are normal permanents which are cast as normal spells and have normal activated abilities.  This is how it breaks down:

1. Active player (AP) gets priority during a main phase and announces Sarkhan, the Dragonspeaker.
2. AP puts Sarkhan on the stack as a spell and pays its cost using {3}{R}{R} obtained in an unspecified way.
3. AP gets priority and passes.
4. Non-active player (NAP) gets priority and passes.
5. The top object on the stack (the spell put there in step 2) resolves: Sarkhan, the Dragonspeaker enters the battlefield as a permanent with four loyalty counters.
6. AP gets priority and announces the first loyalty ability of Sarkhan.
7. AP puts the ability on the stack and pays the cost by adding one loyalty counter to Sarkhan.  Sarkhan now has five loyalty counters.
8. AP gets priority and passes.
9. NAP gets priority and announces Hero's Downfall.
10. NAP puts Hero's Downfall on the stack, chooses Sarkan, the Dragonspeaker as its target, and pays its cost using {1}{B}{B} obtained in an unspecified way.
11. NAP gets priority and passes.
12. AP gets priority and passes.
13. The top object on the stack (the spell put there in step 10) resolves: Sarkan is destroyed.
14. AP gets priority and passes.
15. NAP gets priority and passes.
16. The top object on the stack (the ability put there in step 7) resolves: the permanent referenced by the ability no longer exists, so it resolves with no effect.
17. AP gets priority and...

So here, NAP can kill Sarkhan with the Hero's Downfall because, at the time when Downfall resolves, Sarkhan is not yet indestructible since the ability which would make him so is still on the stack and has not yet resolved.  Now if it were Jace Beleren and Lightning Bolt instead of Sarkhan and Downfall, it would be a different story:

1. AP gets priority during a main phase and announces Jace Beleren.
2. AP puts Jace on the stack and pays its cost using {1}{U}{U} obtained in an unspecified way.
3. AP gets priority and passes.
4. NAP gets priority and passes.
5. The top object on the stack (the spell put there in step 2) resolves: Jace enters the battlefield as a permanent with three loyalty counters.
6. AP gets priority and announces the second loyalty ability of Jace.
7. AP puts the ability on the stack and pays its cost by adding two loyalty counters to Jace.  Jace now has five loyalty counters.
8. AP gets priority and passes.
9. NAP gets priority and announces Lightning Bolt.
10. NAP puts Lightning Bolt on the stack, chooses AP as its target, and pays its cost using {R} obtained in an unspecified way.
11. NAP gets priority and passes.
12. AP gets priority and passes.
13. The top object on the stack (the spell put there in step 10) resolves: Lightning Bolt would deal 3 damage to AP, but NAP chooses to have that damage dealt to Jace Beleren instead.  Three loyalty counters are removed from Jace.  Jace remains on the battlefield with two counters.
14. AP gets priority and passes.
15. NAP gets priority and passes.
16. The top object on the stack (the ability put there in step 7) resolves: each player draws a card.
17. AP gets priority and...

In this case, NAP can not kill Jace with the Lightning Bolt, because by the time he even gets to cast it, Jace already has five loyalty counters.  Remember that the counters are added as the cost of activating the ability, so they are there before NAP even gets to act.  Note that had AP simply passed priority, or done anything else other than immediately activate the +2 ability of Jace after he resolved, then NAP could cast the Bolt in response.   In that case, AP could not activate the +2 ability until the stack was again clear, but by that time Jace would already be long-dead (in terms of priority passes, anyway) to the Bolt.

Get on PayPal and "verify" your account there. PayPal verification FAQ: https://www.paypal.com/webapps/mpp/secu … cation-faq

Well, you've wrote the answer there, yourself, by quoting the rules.  It's right there in 702.2b.  Let me see if I can clarify for you, some.

You can't just "forget" that he has deathtouch.  The rule isn't "it can't assign combat damage to a creature that's blocking it unless ... each creature that precedes that blocking creature in its order is assigned damage equal to its toughness," which is how you seem to be interpreting it.  The actual rule is "it can't assign combat damage to a creature that's blocking it unless ... each creature that precedes that blocking creature in its order is assigned lethal damage."  The key, here, is rule 702.2b which states that "Any nonzero amount of damage assigned to a creature by a source with deathtouch is considered to be lethal damage, regardless of that creature's toughness."

So, the Ankle Shanker may not assign any combat damage to the second zombie, unless "lethal damage" has been assigned to the first one already.  But because it has deathtouch, any amount of damage Ankle Shanker assigns to a creature is considered "lethal damage."  Any amount that isn't zero, that is.  So, as long as it has assigned at least one damage to the first zombie, then it has assigned "lethal damage" and can then assign damage to the second zombie, as well.  Were it not for deathtouch, you would be correct, but since it has both deathtouch and first strike, your zombies are dead before they can hit back, and Ankle Shanker survives the combat unscathed.

How long is "quite some time"?  If your trade partner has failed to respond for more than seven days, you can open up a bad trade report.  You are referring to this trade, yes?  It looks like you've received your end already, and so there is no loss of cards or money, you just want the trade to be done and over with so it's not hanging over your head forever, right?  The deckbox team will contact the member, and if they don't respond to the report within another seven days, you will be allowed to close the trade and leave negative feedback.

Also, this broke one of my pending trades.  I have two FNM foil promo cards that were properly tagged with all the appropriate flags (FNM for the edition, with additional foil and promo tags because they are foil and they are promo cards) that had the promo tag forcibly removed, which meant the trade then included two "promo"-tagged cards that were no longer in my inventory.  I mean, it was easy enough to remedy, but you really should ask (or at least give a warning, and the option to export a collection as-is in case someone wants to keep a copy with the promo tags intact, for whatever reason) before you go mucking about with people's inventories like that.

Now, I've got the arduous task of going through all my "cards from weird-ass editions" (since they're not currently considered "promo" cards) and re-enabling the "promo" flag for all of them if I want my promo cards to actually say "promo."  Since, you know, they are.

You're not wrong.  Well, not entirely.  Technically the Deflecting Palm damage happens after the rest of the combat damage, but the game still ends in a draw.  Here's how the sequence of events breaks down:

- Attacking player declares attackers, gets priority, passes priority.

- Defending player gets priority, casts Deflecting Palm, gets priority again, passes priority.

- Attacking player gets priority, passes priority.

- Deflecting Palm resolves.
-- Defending player chooses 11/11 creature as the source to be prevented.

- Attacking player gets priority, passes priority.

- Defending player gets priority, passes priority.

- Game moves to declare blockers step.
-- Both players receive and pass priority, in order.

- Game moves to combat damage step.
-- 23 damage "would" be dealt to defending player, but 11 of that is prevented by Deflecting Palm's prevention effect.
  --- Only 12 damage is dealt to defending player.  Defending player's life total becomes -1.  GAME DOES NOT END.
-- Then, Deflecting Palm deals 11 damage to attacking player from the other part of its effect.
  --- Attacking player's life total becomes -6.  GAME STILL DOES NOT END.

- Just before attacking player would receive priority in the Combat Damage step, state-based actions are performed.
-- First, the game decides which state-based actions are to be performed:
  --- Attacking player's life total is zero or less and attacking player loses the game.
  --- Defending player's life total is zero or less and defending player loses the game.
-- Then, those actions occur at the same time:
  --- Both players lose the game simultaneously.

- Then, since all players remaining in the game have lost simultaneously, the game ends in a draw.

Source: CompRules at http://wizards.com/magic/rules; past experience as a former rules advisor (i.e. basically a "level zero" judge.)

In tournament play, a match win is worth 3 points, a tie is worth 1 point, and a loss is worth zero points so in this case, a tie is certainly better than a loss.  Tied games, on the other hand, do not count for anything, and are treated as if they never occurred.  Still, though, a tied game (or "non-game," if you will) is better than an actual loss, as far as winning the match is concerned.

If you do, please make it compatible with iPod Touch, as well.

Thanks