AI issues & possible solutions?

by **Aswan jaguar** » 24 Aug 2014, 10:08

We all know that AI doesn't understand Double strike but after the recode of double strike or work made to it in last few patches double strike works better in general but AI is even worse at it because AI doesn't realise that a double striker has first strike.Before we had the first strike value for AI set for double strikers and at least AI recognised them as first strikers.
The latest changes made AI for instance not to attack with a 2/2,2/1 double striker against a 2/2,2/1 creature.Can the AI value for first strike be set or somehow give only AI hint that creature has first strike (which in fact has, as double strike is first strike + normal damage after all) without of course messing the double strike code?

by **Aswan jaguar** » 23 Oct 2018, 16:50

With a card like Decoction Module we usually select for AI to activate it after blockers have been assigned so it can protect a creature from it's blocker or possibly AI's blocker from the attacker though I have never seen AI use the latter ever so possibly AI is unable of doing such a move.(assign a blocker and then remove it).
The big problem is that AI will often remove from combat an unblocked attacker so it won't assign damage to player especially if AI has enough mana to cast it again. Will do that too often if the creature has etb that AI values greatly like Cloublazer.
What can be done? Select AI also to activate it in 2nd main so AI can see it can do combat damage and then return the unblocked attacker to hand in 2nd main(at least be able to do that sometimes) and then a code hint to AI to not return attackers back to hand if they are unblocked and not being targeted of course and return them to hand if blocked and would die.