2.2.1

[Marrhault]

Cast out now works properly?

Any idea where it was failing seemed fine to me?

[ElfNeedsFood]

Not sure either. They’ve gone back and forth about whether this should auto cast given that it’s a support and all other supports do whether there is a valid target or not. Perhaps it’s back to auto casting?

[Marrhault]

Only other odd thing I’ve seen is if the disable is cancelled for one turn it doesn’t go back to disabled

[Brigby]

Hi Everyone. Please check out the official 2.2.1 Release Notes HERE

To answer your question though, the bug was that Cast Out would automatically cast with no creatures on the field. This is now fixed.

[stikxs]

@Marrhault

Only other odd thing I’ve seen is if the disable is cancelled for one turn it doesn’t go back to disabled

This is because the disable from cast out is a one-time effect during casting that lasts until the disable is removed (e.g. the exert part of combat celebrant), or the support is destroyed. It isn’t a persistently applied disable like claustrophobia which has to reapply by nature of it affecting the first creature rather than target creature.

[Sorin81]

But shouldn’t the creature return to disabled? The card text says disable target creature until this support is destroyed. Removing the disable effect for one turn does not destroy the support.

[babar3355]

I am pretty sure cast out still hits autocasts when no creatures are on the board. 95% sure I had this happen to me today.

[fiirst]

@Sorin81

Unfortunately, combat celebrant did not recover only for one turn from cast out

[madwren]

@Sorin81

But shouldn’t the creature return to disabled? The card text says disable target creature until this support is destroyed. Removing the disable effect for one turn does not destroy the support.

Cards which say “enable”, such as Act of Heroism and Hixus, remove the disable keyword without specifying a duration; i.e., permanently. Thus, even if Cast Out remains on the board, it has been overwritten.

[Sorin81]

@madwren

@Sorin81

But shouldn’t the creature return to disabled? The card text says disable target creature until this support is destroyed. Removing the disable effect for one turn does not destroy the support.

Cards which say “enable”, such as Act of Heroism and Hixus, remove the disable keyword without specifying a duration; i.e., permanently. Thus, even if Cast Out remains on the board, it has been overwritten.

I really didn’t think about it like that but yeah that makes sense.

[Brigby]

@babar3355

I am pretty sure cast out still hits autocasts when no creatures are on the board. 95% sure I had this happen to me today.

Hmm that’s peculiar. Thanks for the feedback. I’ll relay this information to the developers.

[Sorin81]

@Brigby

Just happened to me as well. Playing a match in Training Grounds against a Koth deck. First card in my hand and the first played on either side. Auto cast with no creatures on field.

[losdamianos]

@Brigby

Hi Everyone. Please check out the official 2.2.1 Release Notes HERE

To answer your question though, the bug was that Cast Out would automatically cast with no creatures on the field. This is now fixed.

Cast out in 2.2.1 is bugged it auto casted before
strangely enough I didnt have this issue on 2.2

[rafalele]

You can see here it has been reported in 2.2 version.

https://forums.505go.com/discussion/66775/cast-out-oath-of-liliana#latest