31-07-2002 04:06									#1
	A bug and an AI cheat Enter the AD-FREE zone

Hi folks,

I haven't posted or played for awhile so I thought this
would be a more appropriate place for possible already
discussed issues.

BUG

The AI cannot build tanks. The game that I discovered
this in, all Civs were into the modern era. Playing 1.21.
Most civs meet the requirements for building the tanks.
The only thing I did was add 'Iron' to the needed tank
resources. So there is Oil, rubber, Iron. I can't verify
this with 1.21 because somebody decided to store
the 'BIC' file with every SAVE. So I can't change the
BIC after I start the game. These are regular games.

Big AI Cheat

At Emperor level the AI knows were the resources are
going to appear before they show up on the map.

So you know why your neighbor starts charging across
your boundries with settlers about 10 moves before
lets say rubber appears.

The only way to stop this is declare war. Doesn't help
with your rep.

Help anybody,

Dennis

	31-07-2002 04:15									#2
	Support Apolyton, buy Civilization III: Complete

Get 1.29f. One of the AI tweaks is that it's supposed to build more Tanks.

	31-07-2002 11:55									#3
	Avatar Enlargement: We've got the solution

The reason the AI doesn't build tanks before 1.29f is that Mech Infantry were tagged as Offense and Defense. Since Mech Inf are a better all-round unit, the AI builds that as both it's Offensive and Defensive units, rather than building tanks for Offense.

The thing about knowing where the resources are is a well known cheat, and one of the few real cheats that the AI does get.

	31-07-2002 20:34									#4
	This doesn't make sense Support Apolyton, buy Civilization III: Complete

You are saying that 1.29 fixes this. And this problem
only occurred in 1.21. That makes sense.

Otherwise something else is wrong.

Dennis

	31-07-2002 20:52									#5
	Re: This doesn't make sense Support Apolyton buy from Amazon

quote: Originally posted by dennis_caver You are saying that 1.29 fixes this. And this problem only occurred in 1.21.

According to Soren, at least I believe it was him who mentioned it, yes it has been fixed. And the problem has no doubt existed since the first release.