AMAI 2.2

Hello AMAI developers!

I think Blizzard missed this: There is a custom game option "Random Heroes", where the game starts with a random hero (even if the Altar is not yet there, I recall), and it is in these kinds of games where the Blizzard AI malfunctions.

Will there be future support for the "Random Heroes" option? I would like to try that out in Custom Games so that there will be more variety in playing Warcraft III vs Computer. I am just hoping that with the architecture of AMAI, it should be relatively easy to adjust the AI for this type of scenario.

Thanks!

Have you tried it out? Because I did enter some code so AMAI uses this random hero as first hero in that game mode. But I think I never tested it so tell me if it works.

Hello AIAndy! Last weekend I tried AMAI with the "Random Heroes" option (I can only play at weekends), and the result -- I'm very impressed! That time I was not yet aware that you made special programming for it, and deducted that maybe your "Auto-Build Order" algorithm naturally fits "Random Heroes" option. :-D

You said that you made some code; is it something like an early hero harrassment? In a Random Hero game I played vs Undead, I was immediately attacked by the Death Knight and the first ghoul. I suggest that the Undead should avoid using the first ghould to protect its lumber economy. Another game versus NE, the result is a challenging play. Sort of around mid-game, it's like a normal (non-Random Hero) game, which I think, is the AMAI common strategy system working.
___

BTW, we're waiting for the final AMAI for patch 1.15. :-) I've read that NE uses the Staff of Preservation. More power to you guys!

Well some profiles are aggressive and will probably attack like that. :)
We will fix some bugs and maybe add some more feature and then release a new AMAI for 1.15 in the weekend.

Thank you for your work on improving AMAI.

another reason for me to wake up this weekend ;)

@thenonhacker: The special code only makes sure that he uses the right hero (it bypasses the first hero choice). So the rest are effects of the "Auto-Build-Order".
The effect that he uses the first ghoul comes from the setting that for the first attack all ghouls may be used as usually at that point there is already a creation of new ghouls. Of course in the random hero case that does not make sense so I will change that.

AMAI Team, thanks again for the future fix! I'll check out your site for the new AMAI soon. :-)

Could It work well with the Final 1.15 patch

Could It work well with the Final 1.15 patch


Could It work well with the Final 1.15 patch


Could It work well with the Final 1.15 patch


Could It work well with the Final 1.15 patch


Could It work well with the Final 1.15 patch


Could It work well with the Final 1.15 patch


?

Plz don't post the same question so many times. Once is enough. If you accidently did it, there is an edit button to remove the ones that are too much.
And I don't get the question. What do you refer to with it ?

If you mean 2.015 for 1.15 beta so yes it probably works just as well with the final 1.15 patch bt still it's a bit unoptimized and buggy.

AMAI 2.1 will be here soon.

Hello AMAI Team! Some things to bring up:

1. The AMAI website pages are "gone" and the default Apache page appeared instead.

2. So I tried using AMAI for patch 1.14b. I can hire the Goblin Tinker in the Tavern three times. I do not know if this may already been fixed in the AMAI for 1.15 beta.

3. Will AMAI have a mirror server? :-)

I'm using the 2.015 AMAI with the 1.15 Blizzard patch and it works just fine. I don't think it lets you buy three Tinkers, and I haven't seen any other issues.

Thanks MurphGuitar for the heads up!

BTW, the site is up again, just checked today. I downloaded the AMAI beta

Question to the AMAI Team: Does the "15" in "2.015" denotes that it is for the Patch 1.15? Or does AMAI version numbers not directly associated with the Warcraft Patch versions?

The 15 in 2.015 was for the 1.15 beta patch but the version names are not always named like that.
The bug you mentioned is not fixed there though. It is due to the Commander using the old Blizzard.j which does not have the restriction to one tinker. It will be fixed with new version that should be available soon.

Thanks AI! BTW, you forgot -- it's Blizzard "Soonâ„¢" :D