Looking at the Spring engine I noticed that T.A. still only has 4 planes of movement. Lower (includes water), the standard plane. an upper plane (the cliffs and such), and the flight plane. even though the standard and upper planes are now much more flexable, there is still no changes in the sky and lower planes. (this is only determined through unit movement and behavior observations, I have no idea what your code actually does about altitudes so I may be entirely incorrect here).
My question is, why is there no support for the original ai files untill new one for the engine are created? The way I see it, the AI should behave just fine with the exception of lacking arcing fire, something that should be restricted to mortar fire only anyways.
BTW: it's about time someone gave TA a proper 3d engine. Looks Sweet.
Why can't the original AI files be used?
Moderators: hoijui, Moderators
- [K.B.] Napalm Cobra
- Posts: 1222
- Joined: 16 Aug 2004, 06:15
It should be easy...
MUAHHAHA
Couldn't resist :D
Code: Select all
while (opponent.IsAlive)
{
this.BuildStuff();
this.Attack(opponent);
}
Couldn't resist :D
- BlackLiger
- Posts: 1371
- Joined: 05 Oct 2004, 21:58
1) Spring can't use OTA Ais cause of compatability and 3d issues
2) Who the hell wants to play an OTA AI? Even Queller was easy enough. It still rushed you head on and then attacked from all directions WITH AIRCRAFT ONLY.
So basicly, a good net of MTs and the flank the AI base is on covered by ur heavy stuff (allowing for altered paths due to terrain) Would defeat even queller.
3) The objective here is a NONE CHEATING AI.
2) Who the hell wants to play an OTA AI? Even Queller was easy enough. It still rushed you head on and then attacked from all directions WITH AIRCRAFT ONLY.
So basicly, a good net of MTs and the flank the AI base is on covered by ur heavy stuff (allowing for altered paths due to terrain) Would defeat even queller.
3) The objective here is a NONE CHEATING AI.
-
- Posts: 327
- Joined: 09 Apr 2005, 11:40
One of the problems with the TA ai was that it had certain hard-coded overriding behaviours that limited it and eventually made cheating UNITS necessary for it to be competitive. For instance, it would call back all its units if metal got too low and start building meta makers and moho metal makers..... but it didn't check power, so the metal makers wouldn't work, metal would stay low, and it would build EVEN MORE, all while refusing to attack no matter what numerical advantage it had. These features couldn't be edited or turned off.
So many "ai enhancements" ended up including units for the ai only to build; both discount units and metal makers that didn't need power are examples I think I remember people talking about.
So many "ai enhancements" ended up including units for the ai only to build; both discount units and metal makers that didn't need power are examples I think I remember people talking about.