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

Quest mode: AI gets damage from tapped mana vaults with no mana vaults in play #6693

Closed
Goddfrey opened this issue Dec 16, 2024 · 6 comments
Closed

Comments

@Goddfrey
Copy link

Goddfrey commented Dec 16, 2024

Describe the bug
At the beginning of it's turn AI sometimes out of nowhere starts getting damage instances from tapped Mana Vault(s) while having no Mana Vaults in play anywhere. Sometimes up to four instances at a time. My guess is the game checks for Mana Vaults in their libraries or hands.

Edit: happens to the player as well if they have Mana Vault(s) in deck.

To Reproduce
Quest mode, occurs randomly

Desktop (please complete the following information):

  • OS: Windows 10
  • Version 1.6.64 (according to help -> about) or v2 according to GUI :)
Copy link

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

@Jetz72
Copy link
Contributor

Jetz72 commented Jan 15, 2025

Do you have any screenshots or other indication of what else was played prior to this happening? At minimum, a deck list might help.

I notice Mana Vault's damage trigger doesn't check if it's in the battlefield. That shouldn't matter since it should never be possible for it to be tapped if it's not in play... But I'm also not seeing any sanity check in Card.tap or Card.canTap to prevent this. TapEffect can tap cards outside the battlefield if the ETB param is set, but that's presumably only meant to be used on cards that are about to enter. I wonder if there's some card effect or interaction that's causing lands/permanents/Mana Vaults to become "tapped" while not in play.

@Goddfrey
Copy link
Author

Goddfrey commented Jan 18, 2025

Do you have any screenshots or other indication of what else was played prior to this happening? At minimum, a deck list might help.

Sure, I can make you one. I'm not sure how relevant decklist is since I've seen this happening to different AIs with different decklists too.

AI:

Image

Player:
Image

My decklist that the screenshot was taken with

[Main]
2 Ancestral Recall|2ED|1
4 Black Lotus|2ED|1
1 Blightsteel Colossus|2XM|1
1 Bolas's Citadel|WAR|1
1 Brainstorm|2XM|1
1 Dark Ritual|USG|1
2 Demonic Tutor|2ED|1
1 Demonic Tutor|3ED|1
1 Demonic Tutor|LEB|1
1 Goblin Charbelcher|MB1|1
2 Lotus Petal|MB1|1
2 Mana Vault|2ED|1
1 Mana Vault|4ED|1
1 Mana Vault|5ED|1
1 Manifold Key|M20|1
1 Merchant Scroll|HML|1
4 Mox Emerald|2ED|1
4 Mox Jet|2ED|1
1 Mox Opal|SOM|1
2 Mox Pearl|2ED|1
1 Mox Ruby|2ED|1
4 Mox Sapphire|2ED|1
1 Mox Tantalite|MH1|1
1 Mystical Tutor|MIR|1
1 Paradoxical Outcome|KLD|1
2 Paradoxical Outcome|KLR|1
1 Ponder|WHO|2
1 Sensei's Divining Top|EMA|1
1 Snapcaster Mage|UMA|1
1 Sol Ring|PIP|4
1 Swiftfoot Boots|A25|1
1 Tendrils of Agony|SCG|1
1 Time Vault|2ED|1
1 Time Walk|2ED|1
1 Timetwister|2ED|1
4 Tinker|ULG|1
1 Tolarian Academy|USG|1
1 Vampiric Tutor|CMR|1
1 Yawgmoth's Will|USG|1
[Sideboard]

@Jetz72
Copy link
Contributor

Jetz72 commented Jan 19, 2025

Version 1.6.64 (according to help -> about) or v2 according to GUI :)

Just noticed, that doesn't sound correct. I think the latest should say 2.0.02... Screenshot also doesn't indicate the recent change to the zone tabs. Have you been updating by merging new installations atop old ones?

@Goddfrey
Copy link
Author

Version 1.6.64 (according to help -> about) or v2 according to GUI :)

Just noticed, that doesn't sound correct. I think the latest should say 2.0.02... Screenshot also doesn't indicate the recent change to the zone tabs. Have you been updating by merging new installations atop old ones?

Oh yeah, I was overwriting it. And I've been using the old shortcut pointing to the old executable, which it turns out does not even exist in the new version, now that I did a clean install 😅 I will let you know if these bugs still exist now that I've installed it properly.

@Goddfrey
Copy link
Author

It seems it no longer happens with proper install.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants