One direction in scripted AI's is one I have experience in from my mud. There was a client program (tintin++) for connecting to the MUD game which allowed you to create trigger/response commands and store them to a file. Its simplest use was to automate some actions such as low hitpoints causing you to remove backback, take heal potion from backpack, quaff potion, wear backpack. The "programming" done by Users got so extensive that we started having problems with "bot" (robot) players which would spend hours gaining experience or practicing skills while the person was off at work or asleep.
Eventually we started programming our own Version which became very popular. It had conversations, told jokes, had help files for the game which people could ask about, it sold certain useful items and cast spells for money, it did emergency summoning when people shouted for him to, identified common items, etc etc. It got to the point that it had to run from another machine (remember it ran as a player connecting from outside to the game). It used as much CPU as the game itself did when it was running and handling 100 Users.
Anyway, IF a game is written to send and receive info in a way which can be used (such as a text mode), then a program can be written (even one by a third party) to allow scripting all actions. IF I do a certain thing and get a certain response back THEN do this other thing. You could put alot of time and effort into creating a bot which plays Pangaea as sneaky armies, and Ulm making more use of its heavy armor, and Arcospale more defensive while researching/using major spells. Or even 9 different peoples concept of how the AI should best play Ulm.
I dont think that would be easy to do for this game.
So, an alternative..........
Creating a new text file for AI controls, and a new directory for AI modules. Programming AI modules which can be listed in the text file for setting wide parameters for an AI. Such as, a build priority list. A combat spells priority list. A global spells priority list. Items, summons, research,A preference/avoid list for which nations should be actively sought out and attacked in what order.
These can either be done by the programmer in tight programmed modules so that you start out only getting to choose 1 out of 3 different build-queue preferences. Or open text files. There are pros and cons to both.
Just from me personally:
The thing I like most about Version 2 is that its more open to randomization
And for a scripting language Id think that Basic would make sense. thats kindof what its for.