Topic: News about AI
Nordfriese |
Posted at: 2017-09-03, 09:18
I pushed the new aihint values to the branch now. I got rid of nearly all forced_after; very basic buildings have no more prohibited_till flags. I´ll watch how AI performs with the new flags during training rounds and adjust them according to my observations; when it works well, this can be merged into trunk. The metalworkshop problem has already been improved by training. It appears only under certain circumstances: There must be lots of space (often on Big Eden, never on Dolomites); this only starts after several hours of gametime; and even then, AI doesn´t always build that many metalworkshops. I think now that probably this issue can be solved with more training and no coding changes needed. Other issues such as "gamekeeper but no hunter" surface less often as well now. The only major AI problem that can´t be solved by training now is road building. Top Quote |
Tibor Topic Opener |
Posted at: 2017-09-03, 09:28
Great. In fact forced_after flags are too conflicting to basic economy stuff, e.g. when building is not a basic building, basic economy was not established yet, but the building is being forced by the flag...
OK, I will do nothing then, I am glad it settled down....
OK, I will keep it in my virtual TODO list.. Top Quote |
Nordfriese |
Posted at: 2017-09-04, 17:21
I held some more training rounds and the results are very promising. With the new prohibited_till/forced_after values, the AI performs slightly worse on …unusual… maps like Archipelago Sea (hardly any building space) and No Metal Challenge (players 2-7, because so much building space is unreachable). Its risk of getting stuck without space has increased a bit for such maps. On normal maps, it performs better now. For Empire the change is particularly noticeable. It used to do lots of stupid things like build two farms, a tavern and a vineyard before anything else; this is no longer the case. It rarely gets stuck anymore. Barbarians and Atlanteans start training their soldiers a bit later now, but after they start, it´s slightly faster/more efficient than before. There are a few behaviour changes that look a bit stupid, but they never do any harm as far as I can see. For example, AI now often waits a long time before building a quarry, but it always does it in time so it doesn´t run out of granite/marble. I think the branch is ready for merging into trunk now. Top Quote |
WorldSavior |
Posted at: 2017-09-04, 17:29
What's stupid about that? Wanted to save the world, then I got widetracked Top Quote |
Nordfriese |
Posted at: 2017-09-04, 17:54
Do you usually start a game by building two farms? It often caused the AI to get deadlocked with no space to build military buildings. What I mean to say is that the AI built too many buildings before it had enough space to afford them. And if it didn´t run out of space, it ran out of logs before it finished building a forester. Top Quote |
WorldSavior |
Posted at: 2017-09-04, 18:48
No, I don't do that. You're clearly right when you communicate that this is suboptimal. I just wouldn't call it stupid, as it is still no big mistake and the AI is able to do things which are really stupid Wanted to save the world, then I got widetracked Top Quote |
Tibor Topic Opener |
Posted at: 2017-09-04, 21:11
From my point of view, your branch looks good. If anybody is willing to test it - just go on. Top Quote |
Tibor Topic Opener |
Posted at: 2017-09-07, 07:40
Nobody to test it? This is significant improvement and should merged without unnecessary delay... Top Quote |
Nordfriese |
Posted at: 2017-09-07, 16:27
In the last training session, I noticed two things.
A Question as I´m not familiar with launchpad: Can I just push the new wai files to the branch or will the open merge request make this more difficult? Top Quote |
Tibor Topic Opener |
Posted at: 2017-09-07, 20:08
Yes, you can push new commit any time, even now. No consequences... I did it many times during merge review.... Top Quote |