Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Phasing does not phase out the attached enchantments properly #1829

Closed
drmDev opened this issue Apr 9, 2016 · 1 comment
Closed

Phasing does not phase out the attached enchantments properly #1829

drmDev opened this issue Apr 9, 2016 · 1 comment
Labels
refactoring Developers topics about code and programming

Comments

@drmDev
Copy link
Contributor

drmDev commented Apr 9, 2016

For instance with the recently implemented card Vanishing: right now when the enchanted creature phases out, the Enchantment card Vanishing just "lingers" on the battlefield where the creature used to be. Then when the creature phases back in, the Enchantment is re-attached to it. I'm not sure if this is an issue requiring a change in handling for Phasing, or a change in handling for the card I coded in.

Rulings I found on this card and phasing:
http://www.mtgsalvation.com/forums/magic-fundamentals/magic-rulings/magic-rulings-archives/279819-phase-out-more-specifically-vanishing

"Enchantments attached to the creature will "phase out indirectly," and stay attached to it, even though it is phased out."

"Enchantments and equipment phase in/out with the permanents they are associated with."

So it sounds like anything attached to the permanent should additionally phase out and then phase back in with it.

@drmDev drmDev added the refactoring Developers topics about code and programming label Apr 9, 2016
@Zerrisx
Copy link

Zerrisx commented May 18, 2020

Cannot reproduce; this appears to be fixed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
refactoring Developers topics about code and programming
Projects
None yet
Development

No branches or pull requests

2 participants