ZK Graph-Based AI (ZKGBAI)

quote: It now builds pylons somewhat earlier and with higher priority so that grids are built much faster and more reliably.

That's worrying.

The AI interface does not have good support for teams atm. It's difficult even to detect if the ai is playing on teams or not, and there are no events for things like allyCreated, allyDestroyed etc so no ability to defend, repair or whatever as far as allies are concerned. And yes, it also builds n times redundant porc for each kgb in the game. :| I'll probably start hacking at the ai interface upstream soonish, but it'll be a while before any of that hits ZK. (assuming I get all that done before spring 101 is released) Even then teams is complicated for lots of reasons, including resource constraints.

The lag spike issue is real but I'm not really sure what causes it. It seems to be related to units retreating or something along those lines, and it's fairly rare and not easily tracked down.

Before array threatmap we had a nice debug window that showed all maps that the AI had, so you could use this and your usual error logging / debugprint :)

I'll get the window going this week i think.

Observation based on a few games:

ZKGBAI even at +60 metal/second does not seem to build anything interesting like a strider or a superweapon, and just keeps spamming small units?

Seems pretty boring.

ZKGBAI 0.6
the AI does no do anything. in zK playerlist it shows as <waiting> and if it is the only player on its team then it is instantly game over. If there is another AI on its team then only the other AI spawns a com and plays.

[f=0000000] Skirmish AI "Bot1" (ID:0, Short-Name:"CircuitAI", Version:"0.7.9.2") took over control of team 0
[f=0000000] Skirmish AI "Bot3" (ID:2, Short-Name:"CAI", Version:"<not-versioned>") took over control of team 2
...
[f=0000000] Skirmish AI "Bot2" (ID:1), which controlled team 1 is now dead

http://pastebin.com/ZcCRnS6b

quote: [f=0000000] Error: Initializing AI Interface library from file "G:\Spiele\SpringLobby\engine\100.0\AI\Interfaces\Java\0.1\AIInterface.dll". The call to initStatic() returned unsuccessfuly.

Something broke your Java AI interface.

Of interest: i'm observing exactly this failure mode on Mac build of Spring. Possibly it is, thus, not exclusively Mac-related.

all my spring versions were downloaded with springlobby by joining autohosts

Version 8 Update 66 (latest), just the user runtime thing, not the JDK, nothing configured, other java based software works

Ah that's probably it. I think on windows spring requires the 32 bit JVM, which most people would not think to install on a 64 bit machine.

There's no such thing as "not threatened". All it takes is one flea, glaive, dart etc to kill an undefended mex. Also, the official version of kgb does not have any sense about teams, and by default builds defenses before it builds a mex. That basically leads to slow expansion, double porc and other inefficient nonsense. The current dev version knows not to build porc before mexes on teams, but still builds way too many defenders, doesn't team build big energy or anything else, and generally is not efficient in teams. The AI interface also doesn't provide events for allies so kgb cannot defend its allies when they're attacked, nor send AA when its allies are attacked by air, which are central parts of kgb's current strength. As a result, team games are not very interesting for testing KGB's behavior or making design decisions, at least for now, and probably until spring 101.0 is released.