-
Notifications
You must be signed in to change notification settings - Fork 574
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
Comments
Rules wise we need the following window:
|
This issue has not been updated in a while and has now been marked as stale. Stale messages will be auto closed. |
I think for now I might just skip those canPay checks before stack |
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 |
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.:
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.
The text was updated successfully, but these errors were encountered: