Kaladesh MTGPQ Card Gallery (12/7/16)

Fiddler wrote:

The Torrential Gearhulk might need a tweak since it looks like it synergizes a bit too much with Deploy the Gatewatch.

My thoughts as well, but there's no blue white plains walker atm

Do note that Torrential Gearhulk works "On cast" and not "On enter battlefield", which is very significant in this case, as it will not trigger if it is not cast from hand. (Hence the "When you cast this creature").

There is also a little errata that slipped through - Torrential Gearhulk does not give full mana to the Returned cards anymore. The text will be fixed in an update coming very soon after the release.

I'm curious what changes have been made to color mastery. At the very least, a bigger overflow bucket [it's currently restricted to 1000] is required with this new set as it is now possible to get more than +1000 mastery in platinum with the addition of these cards. Are the requirements for the tiers different now? Is there an additional tier? Was this accounted for?

https://images1.mtggoldfish.com/uploads ... alkers.jpg

ZW2007- wrote:

Fiddler wrote:

The Torrential Gearhulk might need a tweak since it looks like it synergizes a bit too much with Deploy the Gatewatch.

If the cards play like they read, it shouldn't be a huge issue. Deploy fetches and the Gearhulk only triggers when cast. So Deploy into Gearhulk shouldn't trigger another deploy.

The problem is this "if" is a huge "if". Cards in this game very frequently don't work the way their text says. "Target" doesn't always target, "target creature" frequently can only target creatures on one side of the battlefield, many things that say "cast" trigger off tokens arriving. It's basically impossible to apply any methodical system to predict whether a combo will work or fail in this game; you just have to try it out.

It's a far cry from the rock-solid methodical Oracle templating of paper Magic, more's the pity.

alextfish wrote:

ZW2007- wrote:

Fiddler wrote:

The Torrential Gearhulk might need a tweak since it looks like it synergizes a bit too much with Deploy the Gatewatch.

If the cards play like they read, it shouldn't be a huge issue. Deploy fetches and the Gearhulk only triggers when cast. So Deploy into Gearhulk shouldn't trigger another deploy.

The problem is this "if" is a huge "if". Cards in this game very frequently don't work the way their text says. "Target" doesn't always target, "target creature" frequently can only target creatures on one side of the battlefield, many things that say "cast" trigger off tokens arriving. It's basically impossible to apply any methodical system to predict whether a combo will work or fail in this game; you just have to try it out.

It's a far cry from the rock-solid methodical Oracle templating of paper Magic, more's the pity.

Some errors might slip through once in a while, sadly, but we are working hard to ensure that card text is as accurate as can be.

In this case (and in the future), we are using "When this card enters the battlefield" (and other variants of this) to mean "When this card enters the battlefield from any location". Using "When you cast this card" (and other variants) means "When this card is played from your hand". The wording is meant to be specific so that it's clearer. Granted, as I said, sometimes there's mistakes, and there's an actual reason for that, when comparing the methodical Oracle templating - in our game, we have to match card text with what the card actually performs in the game internally, while in paper Magic there's no code running behind the card (obviously) so they can print what they like with no other types of repercussions. There's many, many cases where internally a card does a LOT of stuff, but the card text is a simple line of text, so we need to be very analytical when writing card text, and since it's a human process (we can't automate this, really. we've tried!) errors will slip through.

fox1342 wrote:

Are you going to back-edit this so that all previous sets have a distinction between cast and Enter? (please do this for all mechanics etc too - at they very least clues should be supports for origin trigger not just bfz)

Because if you don't standardise now you're going to get a lot (MORE) of confusion down the line!

It's in our task list! It takes a lot of time to rewrite entire sets however, so I wouldn't expect that soon.

Good job at nerfing a card into unplayable before it ever gets a chance to be played. 24 mana for an 8/8 defender is a lot to pay for an ability that's useless for the return on investment. Great job on making a card fight for WorldBreakers position on the POS mythic list. The ability was built in on casting the card which would have made it not work with deploy unless you drew one after the first deployment was cast. Maybe the card could reduce the cost of the cards it brings back or something. It's current build state will through it into the world breaker bin in most people's collection.