I'm currently hugely annoyed at myself for not being a java programmer. And anyway, the developers don't need to do anything for me, but fixing or not fixing or even paying attention to what I'm talking about here has major concequences.
Hexproof - a creature can't be target of spells or abilities your opponents control. There is none on that card, and there is supposed to BE none, it's powerful enough as it is. But the way the game treats it is as if it effectively has hexproof, since the AI won't target it even if it's alone on the board and even if the AI has
Seal of Doom. Multiple ones. I've won two drafts simply due to this. So the implemented card, in fact, has hexproof for you, and if the AI would be using it then it doesn't as you'd target it.
Now if the AI can ignore Lin Sivvi, who is top removal priority in any match she's in, it means that something about her stats makes a creature have "effective hexproof", meaning it will be passed over for removal. Since the vast majority of creatures, agressive ones especially, have 2 power, getting rid of something with 3-4-5 toughness requires removal, otherwise the AI won't attack is you have enough total power on the board to kill any one of it's weenies.
So it's not counting such cards as problems it can remove, even if they're gamebreaking stupidities like that one, but it's counting them as reasons not to attack. Which then makes it behave more stupidly than it needs to and breaks a bunch of cards by making them all basicaly hexproof. Which then makes it misuse creatures, misuse removal and makes cards do stuff which isn't written on them for the player.
It's not a minor thing, or a personal gripe, if this is happening with any 1/3 or 1/4 creature then the AI isn't "working ok-ish" or "stupid but what can you do", it's a huge ass script/code/whatever flaw, which possibly can be fixed, and really should be fixed because if the AI wasn't playing it like this the game would play very differently and much, much closer to how it's supposed to.
My tone is due to the fact that it looked to me like noone noticed it. If I were a MtG engine dev, volunteer or payed, and saw this happening, I'd drop whatever I was doing and get on it right away. And if I noticed this kind of thing happening I certainly wouldn't put cards affected by it on the "implemented" list, because they've been horribly missimplemented (possibly due to a bug or oversight or whatever). I'm just mortified that noone noticed for all this time. If this is working the way it is now, how can you even test the game at all?