It is currently 07 Jul 2021, 11:55
   
Text Size

Shandalar - Program Bugs

AI did not block a 'must attack each turn' creature. (new)

 

OK, we know about the problem where the AI does not realize that these creatures can block, but this was also weird:

Block fail.jpg


AI did not block my Goblin Brigand, even though a potential blocker had First Strike and Protection from red.

Comments

Posted by Aswan jaguar » 22 Jun 2015, 03:59

This seems like the bug with suicidal attacks I reported.It seems that if the creature has both first or double strike and protection from the colour of the attacker/blocker AI will not block with such a creature (your case) or will attack the opponent no matter that opponent has such a creature.
Last edited by Aswan jaguar on 22 Jun 2015, 13:31, edited 1 time in total.
Reason: clarity

Posted by Korath » 21 Jul 2015, 06:51

It's very possible that this only affects Juggernaut and Erg Raiders (and not even cards functionally identical to them). They're special-cased in the combat AI. (Special-cased to do what, exactly, is unclear.) Cockatrice and Lure (but not Thicket Basilisk) are special-cased to do something else.

Posted by Korath » 01 Aug 2015, 03:06

#598 related.

Posted by Aswan jaguar » 29 Sep 2015, 14:59

I have more info on this behaviour.I attacked with
Guul Draz Vampire ( Card Text:
As long as an opponent has 10 or less life, Guul Draz Vampire gets +2/+1 and has intimidate.)which had no intimidate as AI had 17 life but AI didn't block it with Mirran Crusader.Was AI too afraid of me casting Wake Dancer and gain the 2/2 token from Guul Draz Vampire dying?
2015-09-28_201000.I attacked both pro black no block.jpg


More frustrating is the following scenario which still is in the same game as above few turns later.I make a suicide attack as AI will win next turn.AI fails to block 3 out of 5 attacking creatures with and blocks only 1 and looses the game.Only Guul Draz Vampire was unblockable =intimidate at the time AI at 5 life.
2015-09-28_201523.jpg
AI's 3 creatures that didn't block would have killed my 3 attackers if they blocked them.
2015-09-28_201505.jpg

Posted by Korath » 18 Oct 2015, 13:55

I'm starting to think this is another manifestation of the Giant Growth targeting bug, #531, instead. I'm fairly sure that's caused by the AI at replay time getting out of sync with the choices it recorded while speculating; and I was seeing similar blocking blunders quite consistently after playing a card that desyncs the AI (as the target-a-card-in-a-graveyard cards did for a while, including, in extreme cases, the AI blocking non-existent cards off to the right of the actual attackers.

Ticket details

  • Ticket ID: 633
  • Project: Shandalar
  • Status: New
  • Component: Duel AI
  • Project version: Loremaster's Tower 2
  • Priority: Normal
  • Severity: Normal
  • Assigned to: (unassigned)
  • Reported by: jiansonz
  • Reporter's tickets: List all tickets
  • Reported on: 21 Jun 2015, 20:05
  • Last visited by Korath » 01 Mar 2016, 18:09.
 
cron

Login Form