Spring RTS Engine

You've just made one of my Agents obsolete SJ, how many more AI agents are there in my TAI stuff that are already in Spring is another form?!?!

Because most people have the bad habit of not understanding the language of glory and heroes (thats swedish if you wonder :) ).

Hey if you post in it, I _will_ learn, and if you code in it, chances are I could decifer it.

These ideas are tantalizing, SJ. What other prioritization can we automate? Can we tell artillary always to stay to the back when firing, or tell it always to fire from high elevations?

Since the ais is imported from DLLs (later a script language probably) that we let the user create themselves they can do just about anything in theory. Depends entirely on how much time the user want to spend programming them (and how good the user is at programming).

At the moment we only have this central build ai and a very simple formation ai. I think I will write a metal maker manager also that turn on/off mms at certain energy levels. But mostly we meant that the user community should create these.

Well why not release the ai'ing info to the public before springs released, so we can theoreticaly build up some nice little scripts for the big day? I'll be damned if I don't make atleast one contribution to this project, well I'll probably be damned anyway but thats something else entirely.

Yes he's right, I want to put out TAI through till I'm talkign about the actual code making it, and if you have a dll AI interface and several dll's already in existence then I want to know how this works as soon as possible and how it will effect my thought schema with regards to TAI, whatsmore I'd want to know exactly how to create such a dll immediatly, such information would place a skirmish AI almost certainly within the communities grasp given several changes on your behalf to the engine, which may already eb in place but havent been told

Ya, c'mon SY's, out with it!





Please?