Deploy the Gatewatch

2

Comments

  • DAllofAbove
    DAllofAbove Posts: 20 Just Dropped In

    Leave Britney and Deploy ALONE!

  • gozmaster
    gozmaster Posts: 267 Mover and Shaker

    @Raistlin0309 well said my friend.

  • Khaalis
    Khaalis Posts: 17 Just Dropped In

    If you really wanted to "Fix" Deploy, simply change the wording from "Fetch" to "Summon".

  • camo
    camo Posts: 39 Just Dropped In

    Unfix Deploy the Gatewatch and Curse of Vitality, they are not bugged in the first place. Please focus your energy on fixing bug and makes better events for us.

    Great cards thats already work as the text dictate should be left alone, especially mythic and masterpiece, they are chase cards for a reason, if not, Webcore, you are sending message to us that no cards are worth chasing anymore, no need to spend any cash getting them since any great cards would be changed and destroyed in matter of time.

  • Stormcrow
    Stormcrow Posts: 462 Mover and Shaker

    Hi PQ Support, is the change to DtG so it's affected by Ashiok also going to be applied to the other "fetch" cards listed in my previous comment?

  • ArielSira
    ArielSira Posts: 524 Critical Contributor

    Thank you for the clarification @Magic:PQ Support Team

  • gozmaster
    gozmaster Posts: 267 Mover and Shaker

    Thank You for the fast response. It's a relief to hear one of our favorite cards is avoiding the nerf :smiley:

    @Magic:PQ Support Team thank you!

  • Scifibot
    Scifibot Posts: 25 Just Dropped In

    Aside from the obvious blunder of the PMA greed scandal this is by far the worst thing you've done since taking over the reigns. I realize you have no idea what is really happening yet but Deploy the Gatewatch and most of this community have been happy without incident for so many years. This is beyond rediculous.

    Ingame: Zander

  • BongoTheGrey
    BongoTheGrey Posts: 348 Mover and Shaker

    @Magic:PQ Support Team said:
    Greetings everyone.

    Thanks for bringing the discussion to the forums regarding the fix performed on the card Deploy the Gatewatch.
    For clarification, the changes made to this card should only affect its interaction with the effects that specifically restrict fetching a card, such as the one found on the Ashiok, Dream Render.

    The changes made to the card WILL NOT:

    • Cause the cards being fetched by Deploy the Gatewatch to interact with effects that care for summoning a creature.
    • Cause the cards being fetched by Deploy the Gatewatch to interact with objectives that care for summoning a creature.
    • Cause Deploy the Gatewatch to not work correctly if the player's hand is full. It will perform its effect regardless of the number of cards present in the player's hand.

    Please rest assured that the intended functionality of the card is still preserved. The card still is working as you all know (and some love). This was not a balancing change, and the card is not being nerfed.
    We understand that the information regarding this change present on the patch notes for version 6.3.1.64068 might have caused some confusion, and apologize for that. This text has been updated to better reflect this.

    As always, if you encounter new functionality issues with the cards, we encourage you to reach out to bring it to our attention on the MTGPQ BUGS & TECHNICAL ISSUES forum, or to report it directly to our customer support team by clicking here, or in-game by clicking on the "Help Center (FAQ)" button on the Setting screen in-game.
    Then, click any Help Topic and keep clicking until you see a "Was this helpful?" on the bottom of the screen.
    Click the "No" option and then you will find your way to "CONTACT US".

    Thanks once again for bringing the discussion to the forums. We wish you good luck and great battles in Magic: Puzzle Quest.

    This still feels wrong in so many ways.
    The problem is Deploy the Gatewatch's wording.
    I don't know if you guys know anything about this games history since you are the new devs on the block, but before Oktagon there was another company called Hibernum that developed the game and they used a different wording for the cards and mechanics. Deploy the Gatewatch is one of those. Instead of summon, which is clearly what Drag does, they used "Fetch to the battlefield". Just like how Jace's Sanctum says "At the beginning of your turn, your opponent loses 3 mana." Instead of "drain 3 mana" even though we all know that what it does is drain and it triggers all the drain mana effects on the game. They just had different terms for things.

    So now are now introducing a "fix" that makes no sense at all because you say that the card will still behave as always, so even if your hand is full it still summon the cards because they are not really being fetched to your hand, is just a simulation. So they are actually being summoned as if the card said "summon".
    But at the same time you want the Ashiok vanguard to discard them. But how can a card be discarded when it never goes to your hand? Cards can only be discarded from hand so why on earth should Ashiok's vanguard discard something that is never in your hand?

    You cannot have both things at the same time. If you want consistency you either make the cards go into your hand and kill Deploy the Gatewatch completely so it can interact with Ashiok's vanguard or you keep DtG as is and make it ignore Ashiok completely because what it does is actually summon creatures. So changing it's wording to reflect what it does would be nice.

  • Raistlin0309
    Raistlin0309 Posts: 27 Just Dropped In

    Thank you Webcore for the prompt response/clarification.

    Your interaction with us nerds is much appreciated.

  • wraszowixuXuxi
    wraszowixuXuxi Posts: 59 Match Maker

    If one is worried about facing Deploy, it is legacy, so in most cases you may face it (unless there is a Standard facing Legacy PvE), one does have the option to run stuff like Authority of the Consuls, or the original Thalia (though her Gitrog iteration works as well, that one has a few other hoops), and a larger array of flash kill or bounce spells. Those both being white, kinda led to me valueing walkers like Daxos and Kalemne and Tamiyo for all color combinations. And I guess Dakkon can run it too, but kinda have preferred his vanguard over running him, if possible.

    Disable Greg's creatures as they enter the battlefield, and then you can have a plan on how you want to deal with them after that.

  • Mainloop25
    Mainloop25 Posts: 1,959 Chairperson of the Boards

    Although I'm not really in favor of changing any staple cards just because of fringe interactions, if this is the result of them making an effort to go through the bug report and actually fixing things we report, overall it's a good thing. We'll just have to own the consequences of it a bit.

  • Metroplex78
    Metroplex78 Posts: 74 Match Maker

    There should be limits to how big the creatures fetched and cast are and how many times per turn this can happen, this would end those stupid loop decks, which is legalized cheating.

  • Opperstamper
    Opperstamper Posts: 159 Tile Toppler

    @BongoTheGrey said:

    @Magic:PQ Support Team said:
    Greetings everyone.

    Thanks for bringing the discussion to the forums regarding the fix performed on the card Deploy the Gatewatch.
    For clarification, the changes made to this card should only affect its interaction with the effects that specifically restrict fetching a card, such as the one found on the Ashiok, Dream Render.

    The changes made to the card WILL NOT:

    • Cause the cards being fetched by Deploy the Gatewatch to interact with effects that care for summoning a creature.
    • Cause the cards being fetched by Deploy the Gatewatch to interact with objectives that care for summoning a creature.
    • Cause Deploy the Gatewatch to not work correctly if the player's hand is full. It will perform its effect regardless of the number of cards present in the player's hand.

    Please rest assured that the intended functionality of the card is still preserved. The card still is working as you all know (and some love). This was not a balancing change, and the card is not being nerfed.
    We understand that the information regarding this change present on the patch notes for version 6.3.1.64068 might have caused some confusion, and apologize for that. This text has been updated to better reflect this.

    As always, if you encounter new functionality issues with the cards, we encourage you to reach out to bring it to our attention on the MTGPQ BUGS & TECHNICAL ISSUES forum, or to report it directly to our customer support team by clicking here, or in-game by clicking on the "Help Center (FAQ)" button on the Setting screen in-game.
    Then, click any Help Topic and keep clicking until you see a "Was this helpful?" on the bottom of the screen.
    Click the "No" option and then you will find your way to "CONTACT US".

    Thanks once again for bringing the discussion to the forums. We wish you good luck and great battles in Magic: Puzzle Quest.

    This still feels wrong in so many ways.
    The problem is Deploy the Gatewatch's wording.
    I don't know if you guys know anything about this games history since you are the new devs on the block, but before Oktagon there was another company called Hibernum that developed the game and they used a different wording for the cards and mechanics. Deploy the Gatewatch is one of those. Instead of summon, which is clearly what Drag does, they used "Fetch to the battlefield". Just like how Jace's Sanctum says "At the beginning of your turn, your opponent loses 3 mana." Instead of "drain 3 mana" even though we all know that what it does is drain and it triggers all the drain mana effects on the game. They just had different terms for things.

    So now are now introducing a "fix" that makes no sense at all because you say that the card will still behave as always, so even if your hand is full it still summon the cards because they are not really being fetched to your hand, is just a simulation. So they are actually being summoned as if the card said "summon".
    But at the same time you want the Ashiok vanguard to discard them. But how can a card be discarded when it never goes to your hand? Cards can only be discarded from hand so why on earth should Ashiok's vanguard discard something that is never in your hand?

    You cannot have both things at the same time. If you want consistency you either make the cards go into your hand and kill Deploy the Gatewatch completely so it can interact with Ashiok's vanguard or you keep DtG as is and make it ignore Ashiok completely because what it does is actually summon creatures. So changing it's wording to reflect what it does would be nice.

    I fully agree with this. Apparently Deploy does now (still) interact with Ashiok Vanguard, which it shouldn't. The fetch to battlefield mechanic never cared about the "hand" zone.

    I searched the rules and keywords database and there are not a lot of rules stated about these interactions. I can find some info on the discard rule; it specifically says that discard happens from hand, so it seems clear that a card not reaching the "hand" zone cannot be discarded.

    We do need a proper rule about the Fetching mechanic now. What will happen? Will the rules be written to comply with the Deploy decision? Then there are a lot of cards to go back to and give the same fix. Can we assume you have a list already?

  • Metroplex78
    Metroplex78 Posts: 74 Match Maker

    Please make DtG colourless and put it on sale so we can all 'Deploy' those stupid loop decks that are not fun.

Categories