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

AI does not account for commander damage when chosing blockers #6159

Closed
Nymra opened this issue Sep 16, 2024 · 3 comments
Closed

AI does not account for commander damage when chosing blockers #6159

Nymra opened this issue Sep 16, 2024 · 3 comments

Comments

@Nymra
Copy link

Nymra commented Sep 16, 2024

This is an old bug and I reported it before (and I was ignored and attacked for it) but it is still there.

  1. AI very often does not block my commander even if it could and dies from commander damage, even when it had legal blockers available (even cheap ones, like tokens). sometimes feels like the AI just gives up lol...
  2. issue seems to arise more often with commanders that have first strike or lot of buffs (+1/+1 tokens, auras/equipment).
  3. the AI seems to block more often when the damage would kill it by life going to 0, too.

In other words: Voltron commanders feel like a cheat vs AI since I can very often guess for the AI not to block it.

Tested with Thrun, the Last Troll, Licia, Sanguine Tribune and similar commander types.
If you try to reproduce, please read my post before thorougly...
Ironically, when the commander also has trample it gets blocked more often.

Feels odd that nobody else seems to have this issue, or maybe not many play commander vs. AI with voltron types?
I get this alot less ofc with my Bruna deck, but she gets to be unblockable fast anyway, so I would not notice it for example.

@Nymra
Copy link
Author

Nymra commented Sep 26, 2024

Is this still ignored?

It is a major issue.

Copy link

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

Copy link

This issue was closed because it has been stalled for 5 days with no activity.

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

No branches or pull requests

1 participant