New perspectives and cast out [Devs Aware]

James13
James13 Posts: 665 Critical Contributor
I see in my log that "new perspectives triggered" when I drew cast out, however it did not receive any mana.

//Edited Title -Brigby

Comments

  • James13
    James13 Posts: 665 Critical Contributor
    Just an update to this.  When CASTING new perspectives if cast out is in hand it gains mana.  Just not when drawn when new perspectives is in play.
  • wereotter
    wereotter Posts: 2,070 Chairperson of the Boards
    However, of you attempt to cycle Cast Out after drawing it to this glitch, the card acts as though it didn't gain any mana. 
  • Hefty
    Hefty Posts: 9 Just Dropped In
    +1,
    but it also affects the cycle lands (atleast fetid and farmlands).
    So i guess this might be true for all supports?
    Behavior is as described:
    Cast new perspective->Draw Support with cycling->no mana gain.
    Cast new perspective->Support with cycling already in hanf -> mana gain as exspected.


  • Avacyn
    Avacyn Posts: 89 Match Maker
    Hefty said:
    +1,
    but it also affects the cycle lands (atleast fetid and farmlands).
    So i guess this might be true for all supports?
    Behavior is as described:
    Cast new perspective->Draw Support with cycling->no mana gain.
    Cast new perspective->Support with cycling already in hanf -> mana gain as exspected.


    I confirm this. Cycle lands don't get any mana while New Perspective is on board.
  • obsidianpeanut
    obsidianpeanut Posts: 25 Just Dropped In
    Hefty said:

    Behavior is as described:
    Cast new perspective->Draw Support with cycling->no mana gain.
    Cast new perspective->Support with cycling already in hanf -> mana gain as exspected.



    +1
    I'm seeing this behavior too, specifically with New Perspective and Cast Out.
  • Smash666
    Smash666 Posts: 37 Just Dropped In
    Hi all, I've found a bug with Hixus Prison Warden and Cast Out, when Hixus is destroyed all creatures that are disabled by Cast become active again. That's not right....
  • wereotter
    wereotter Posts: 2,070 Chairperson of the Boards
    Smash666 said:
    Hi all, I've found a bug with Hixus Prison Warden and Cast Out, when Hixus is destroyed all creatures that are disabled by Cast become active again. That's not right....
    No. That's right. Read Hixus again.

    When Hixus is destroyed, enable all your opponent's creatures. 
  • Smash666
    Smash666 Posts: 37 Just Dropped In
    wereotter said:
    Smash666 said:
    Hi all, I've found a bug with Hixus Prison Warden and Cast Out, when Hixus is destroyed all creatures that are disabled by Cast become active again. That's not right....
    No. That's right. Read Hixus again.

    When Hixus is destroyed, enable all your opponent's creatures. 
    Oh ok thank you 
  • Hefty
    Hefty Posts: 9 Just Dropped In
    @Brigby: Any news on this?
    Devs aware should be an easy one as it is fast to reproduce.
    Fixing solely depends on the code, and as a dev myself i can´t even imagine how cycling or perspective is coded if it has to look at the subtype of the card drawn and not only if it has cycling... (That would not pass our QA for sure  B) )
  • Pcell777
    Pcell777 Posts: 51 Match Maker
    Hefty said:
    @Brigby: Any news on this?
    Devs aware should be an easy one as it is fast to reproduce.
    Fixing solely depends on the code, and as a dev myself i can´t even imagine how cycling or perspective is coded if it has to look at the subtype of the card drawn and not only if it has cycling... (That would not pass our QA for sure  B) )
    What r u talking about.  We are the QA.
  • Hefty
    Hefty Posts: 9 Just Dropped In
    Pcell777 said:
    Hefty said:
    @Brigby: Any news on this?
    Devs aware should be an easy one as it is fast to reproduce.
    Fixing solely depends on the code, and as a dev myself i can´t even imagine how cycling or perspective is coded if it has to look at the subtype of the card drawn and not only if it has cycling... (That would not pass our QA for sure  B) )
    What r u talking about.  We are the QA.
    Well, it sure did not get past us ;)
    Problem at hand is: Our QA knows the way to get to the dev responsible...