SUGGESTION: AI castle building algorithm

[tinkthank]

Wow, I dont understand a damn thing about programming and whatnot, but you definately are the man.
(Um hoping you are male, here.)
Um: wow, thanks. That sounds great. Imagine, real AI enemies!
yum....

[Arralen]

Originally posted by Norfleet:
Your castle building policy may also be dictated by your castle choice:..
If ... Wizard tower,...becomes simpler:

IF PROVINCE DOES NOT HAVE CASTLE
BUILD CASTLE

I think
Build castle IF money=1.2*(castle cost)
will take care of this very well, but only testing in a "real life" will show. Any takers?

Can't do much testing myself, as time is limited and there's so much to do ...

[Norfleet]

Originally posted by Arralen:
Build castle IF money=1.2*(castle cost)
will take care of this very well, but only testing in a "real life" will show. Any takers?

I think the underlying problem is that the AI never has any money because it has blown all of its cash hiring garbage. Your troop hiring formulas might improve that, although it still wouldn't stop the AI from squandering most of its money on troops it wastes in futile attacks. For instance, human players tend to win attacks on provinces, unless the attack is anticipated by the defender: In contrast, the AI will often lose attacks even when you did not specifically anticipate it.

[Arralen]

I can't do a thing about how the AI fights, but I did put in a "moneysaving turn" now and than so the AI will have the money available from time to time to build a castle. Check out.

[Gandalf Parker]

Sounds good. I like the logic so far. Seems to take into account everyones favorite tactics (except chokepoints but the logic on that would be difficult)


I wonder how much "thinking" this would take. I usually comment that it doesnt matter how long it takes a turn to process because its a "pass turn file to host" type game. But AI improvements mostly affect solo players and improving the AI would do any good if it changes the game to something too slow to hold their attention.

[Arralen]

"thinking costs":
I'm concerned about the needed cpu time to re-calculate the "desirability" for each province each turn.

Maybe I can come up with a simple solution that generalizes most cases when you can barely build a castle but prefer to do so over building troops.


choke points
d) has 4 land neighbours, of which 2 are not owned AND not neighbouring owned provinces

.. doesn't this qualify?

[ April 16, 2004, 14:35: Message edited by: Arralen ]

[Daynarr]

Originally posted by Arralen:
Build castle
IF money=1.2*(castle cost) OR desirabilty>7
CHOOSE prov with highest "desirability points"

It's not bad idea, but I was thinking about something a little different here.

1) Limit amount of gold spent on non-castle provinces (relative value, maybe 30% or even less). That way if AI has enough gold income and too few castles he will generate surplus in gold and wont spent it all on weak easy-to-lose units (Militia, LI). That will allow him to build as much national units as he can and still be able to generate some surplus to build new castles. If AI spends all money on national troops and can’t afford new castle, then he doesn't build new one anyway at least with his current income.

I believe Jasper proposed something like this in LI thread and I like this idea better simply because it will maximize production of national troops without going too deep into unit production scripting.

2) When AI has enough gold to build castle he should decide where to do it. Your proposal is quite good, so I would add only 1 thing there. When deciding for where to build castle AI should take into account ALL neighbors, not only the ones he controls. That way he will be building forts on bordering provinces if they are good, without need for special algorithms.

As for slowdowns, I don't think they should be significant since AI revalue his provinces only when he has enough gold to build castle, not every turn.

[ April 16, 2004, 15:23: Message edited by: Daynarr ]