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

Solemnity does not prevent a player from paying tribute cost, but the creature won't get the +1/+1 counter #599

Open
vorpal-buildbot opened this issue Sep 20, 2018 · 0 comments

Comments

@vorpal-buildbot
Copy link
Contributor

@vorpal-buildbot vorpal-buildbot commented Sep 20, 2018

What should happened

  • Because Solemnity forbid counters to be put onto creature, no one should be able to pay the tribute cost

7/14/2017 | If a creature with tribute is entering the battlefield, the chosen opponent can’t pay tribute even if they want to.

What actually happened

  • The opponent can choose to pay the tribute cost, so the creature won't get the bonus, but the creature also won't get the +1/+1 counter

Screenshot
image

From Bug Blog.
Affects: [Solemnity]

Bug Blog Text: [Solemnity] does not prevent a player from paying tribute from cards such as [Oracle of Bones].

@vorpal-buildbot vorpal-buildbot changed the title [Solemnity] does not prevent a player from paying tribute from cards such as [Oracle of Bones]. Solemnity does not prevent a player from paying tribute from cards such as Oracle of Bones. Sep 20, 2018
@stash86 stash86 changed the title Solemnity does not prevent a player from paying tribute from cards such as Oracle of Bones. Solemnity does not prevent a player from paying tribute cost, but the creature won't get the +1/+1 counter Jun 4, 2020
@stash86 stash86 added Advantageous and removed Unclassified labels Jun 4, 2020
@stash86 stash86 added this to 3.4.114.4048 in Verification Jun 4, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Verification
  
3.4.114.4048
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants