Skip to content

/ mage

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

Jump to bottom

Card brought into play with Nightveil Specter does sometimes ask wrong player for decisions (e.g. comes into play effects like shocklands). #552

Closed
LevelX2 opened this issue Aug 29, 2014 · 1 comment
Closed

Card brought into play with Nightveil Specter does sometimes ask wrong player for decisions (e.g. comes into play effects like shocklands). #552

LevelX2 opened this issue Aug 29, 2014 · 1 comment
Labels
bug duplicate

Comments

@LevelX2
Copy link
Contributor

@LevelX2 LevelX2 commented Aug 29, 2014

http://www.slightlymagic.net/forum/viewtopic.php?f=70&t=15076&p=159052&sid=4f4ec4dbbc075528c11e8ca5f78837ed#p158972
I was unable to play a shockland of Nighveil Specter untapped, even though i had enough life to pay. I clicked the land in exile and it straight came into play tapped.

http://www.slightlymagic.net/forum/viewtopic.php?f=70&t=15076&p=159052&sid=4f4ec4dbbc075528c11e8ca5f78837ed#p159052
Also someone earlier mentioned not being able to pay life for an untapped shockland they played off a Nightveil Specter. Probably related: my opponent got a Godless Shrine off of my libray with his Nightveil, and it asked ME if I wanted to pay the two life for it to come into play untapped.
@LevelX2 LevelX2 changed the title Card brought into play with Nightveil Specter does sometimes ask wrong player for decisions (e.g. comes into play effects like painlands). Card brought into play with Nightveil Specter does sometimes ask wrong player for decisions (e.g. comes into play effects like shocklands). Aug 29, 2014
@LevelX2 LevelX2 added the bug label Aug 29, 2014
@LevelX2 LevelX2 mentioned this issue Oct 15, 2014
Closed
@LevelX2
Copy link
Contributor Author

@LevelX2 LevelX2 commented Jan 4, 2015

Seems this was fixed with the changes made in November.
@LevelX2 LevelX2 closed this Jan 4, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug duplicate
Projects
None yet
Milestone
No milestone
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant
@LevelX2