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

Abilities with some unpayable costs must still be allowed to be put on the stack #112

Open
tool4ever opened this issue Apr 21, 2022 · 4 comments · May be fixed by #6700
Open

Abilities with some unpayable costs must still be allowed to be put on the stack #112

tool4ever opened this issue Apr 21, 2022 · 4 comments · May be fixed by #6700
Labels

Comments

@tool4ever
Copy link
Contributor

Activating mana abilities is done before paying costs when activating an ability. This means that if you control a creature which can be tapped for mana, such as Avacyn's Pilgrim, you may both tap it for mana and untap it to pay costs for Halo Fountain's activated abilities.

Currently Forge will not let you activate the ability without a tapped creature though, so you're forced to tap for mana first.

This matters because there might be triggers related to it that will then be on the stack before your ability, e.g.:

grafik

But you should be able to reach the opposite order as well if you so desire.

Another related example is Bond of Agony:
if you're at 1 life Forge will not let you choose X > 1. But maybe you want to cast it for X=2 because you can pay that part with The Great Henge.

@Hanmac
Copy link
Contributor

Hanmac commented Apr 25, 2022

Rules wise we need the following window:

  • Put Card on the Stack and choose stuff like X
  • Activate Mana Abilities (You would need to confirm that you are finished activating Mana Abilities)
  • Pay the Cost (and do stuff like Convoke, Improvise and Delve), At this point you can't activate Mana Abilities anymore

@github-actions
Copy link

github-actions bot commented Jul 5, 2023

This issue has not been updated in a while and has now been marked as stale. Stale messages will be auto closed.

@tool4ever
Copy link
Contributor Author

I think for now I might just skip those canPay checks before stack
But to not confuse newer players it's probably better something not enabled by default like Full Control

@Hanmac
Copy link
Contributor

Hanmac commented Jan 31, 2024

it also related to the problem with CostPayment that we currently don't differ between the two steps of:

activating Mana Abilities and paying the Costs

@tool4ever tool4ever linked a pull request Dec 17, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants