-
Notifications
You must be signed in to change notification settings - Fork 762
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
Yawgmoth Demon not working #1918
Comments
…f no artifact was sacrificed (#1918).
Sorry adidn't check the Assignee . |
Thanks LevelX2, but I'm confused by this fix. |
Hmm, the boolean is set to false on init and only set to true, if an artifact was sacrificed. Where do you see a problem? |
I have tested this on master and it's still not working. If I control an artifact and answer “yes”, Yawgmoth Demon becomes tapped and deals damage. If I answer “no”, I have to choose an artifact to sacrifice. |
the if I coded was checking if there were no artifacts (<1), so it wouldn't be possible to sacrifice any (inside the if), but the boolean was inside the if. Here is how I thought about it originally: Count how many artifacts, if there isn't any, the IF would be true (short-circuit the choice) and damage would be caused. Anyways, yours solution plus Fenhl last tweak basically inverted that IF (meaning, you guys coded the "else" clause from before inside the if, and "my" if now is the else clause.. in case you wanna remove the boolean altogether :)). What I believe was happening was the call to: .. was always returning false, since the choice was short-circuited by having no artifacts to choose from (so there was nothing to sacrifice or filter). Then the other IF(where the damage was applied), never got a change to happen. It seems correct now tho : ) thanks guys. |
Yep, logical change. Sometimes your routine-blinded. |
Yawgmoth Demon's upkeep ability doesn't do anything, at least if you control no artifacts.
The text was updated successfully, but these errors were encountered: