Spring RTS Engine

Kloot wrote:The 2.02 source still does not compile without intervention. (Due to the Command.h alias command.h and FileHandler.h inclusion issues, and because g++ doesn't like the extra UNIT:: qualification in UNIT.h for some reason.)

Kloot wrote:More importantly though, QAI still seems to hang on Green Comet Basic and The Cold Place, or rather, on any map with OTA-style metalspots (that I've tried), which is somewhat befuddling since all the necessary directories are created now AFAICT and there is no platform-specific code in the metal class...

Kloot wrote:What I mean is, Command.h (which you include twice) isn't found by the preprocessor because the actual filename is command.h and Linux is case-sensitive, thus making compilation a minor problem.

General Ai water/ map behaviour wrote: IMO some AI's are kinda like "if water is more then land, built a army of ships", instead they should be like "theres water, let's build ships to assist my land army". But then you would have a problem with maps which have isles, so either the AI makes use of transport units or just let them build ships when there are no land connections between them and their enemys.

I don't know if any AI does this, but maybe also mapsize should be taken into account when deciding if it is "water map only", let's make an overrated guess: We got a mapsize of 80x80 (yeye, not possible for now). so 90% of it is water, but still the land would be huge enough for Massive unit armys.

I dont know if the game distinguishes between land and water, if yes you could try to calculate the space of land and water, comparing it with the mapsize and maybe using a 6x6 pattern (for example so a goliath can pass).

So if this part calculates that the smallest part is enough for 6 goliaths it's considered a "land army" map, if water size is even bigger, it adds "water army" map.

However fiddling around and writing this code may actually take longer than it's worth in the end.

Engine Of Darkness wrote:What I don't like about this Ai is, that it trys to build shipyards only on Supreme Battlefield. The first thing it does is building a shipyard, which leads to 100% looose afterwards (It just builds on water, nearly nothing on land).

The quote below is just a generall though about AI, nothing specific about your AI, it just came into my mind while writing this.

General Ai water/ map behaviour wrote: IMO some AI's are kinda like "if water is more then land, built a army of ships", instead they should be like "theres water, let's build ships to assist my land army". But then you would have a problem with maps which have isles, so either the AI makes use of transport units or just let them build ships when there are no land connections between them and their enemys.

I don't know if any AI does this, but maybe also mapsize should be taken into account when deciding if it is "water map only", let's make an overrated guess: We got a mapsize of 80x80 (yeye, not possible for now). so 90% of it is water, but still the land would be huge enough for Massive unit armys.

I dont know if the game distinguishes between land and water, if yes you could try to calculate the space of land and water, comparing it with the mapsize and maybe using a 6x6 pattern (for example so a goliath can pass).

So if this part calculates that the smallest part is enough for 6 goliaths it's considered a "land army" map, if water size is even bigger, it adds "water army" map.

However fiddling around and writing this code may actually take longer than it's worth in the end.

I'm not saying this AI is bad, it just needs improvement in this section.