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 eagerly casts Entomb into active graveyard hate #5245

Open
jumpinjackie opened this issue May 15, 2024 · 0 comments
Open

AI eagerly casts Entomb into active graveyard hate #5245

jumpinjackie opened this issue May 15, 2024 · 0 comments

Comments

@jumpinjackie
Copy link
Contributor

Describe the bug

Observed in a game against AI opponent today. AI casts Entomb twice on the same turn with an active Leyline of the Void in play sending their tutored cards straight to exile (see screenshot below).

A card like Entomb is so narrow in scope (unlike other cards that can send cards to the GY like a looting spell/effect) that such a play just sounds nonsensical. At least with a looting effect you still get to draw cards, so I can understand an AI playing a looting spell/effect in the presence of active GY hate.

To Reproduce
Steps to reproduce the behavior:

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. See error

Expected behavior

Seeing that a Leyline of the Void (or any other active graveyard hate of its kind) on the battlefield, I would expect the AI to hold back on playing cards like Entomb in the general case.

Screenshots

2024-05-16 01_25_58-Window

Desktop (please complete the following information):

  • OS: Windows 10
  • Browser [e.g. chrome, safari]
  • Version: 1.6.63-SNAPSHOT-05-14

Smartphone (please complete the following information):

  • Device: [e.g. iPhone6]
  • OS: [e.g. iOS8.1]
  • Browser [e.g. stock browser, safari]
  • Version [e.g. 22]

Additional context
Add any other context about the problem here.

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

1 participant