Helo Bibim, it was who had the problem with AI, as MrArcher said before.
Startscript looks like this
Code: Select all
[GAME]
{
Mapname=Conversation;
Gametype=Balanced Annihilation V7.31;
startpostype=0;
AutohostPort=8454;
HostPort=8452;
AutoHostName=Pisces;
AutoHostCountryCode=CZ;
AutoHostRank=0;
AutoHostAccountId=190710;
IsHost=1;
NumPlayers=1;
NumTeams=2;
NumAllyTeams=2;
[PLAYER0]
{
Name=[CZ]Pavouk106;
Password=<some hash here>;
Spectator=0;
Team=0;
CountryCode=CZ;
Rank=4;
AccountId=170192;
}
[AI0]
{
Name=Bot1;
ShortName=RAI|0.601;
Team=1;
Host=0;
}
[TEAM0]
{
RgbColor=0.54118 1.00000 0.00000;
TeamLeader=0;
Side=ARM;
Handicap=0;
AllyTeam=0;
}
[TEAM1]
{
RgbColor=0.00000 0.00000 1.00000;
TeamLeader=0;
Side=ARM;
Handicap=0;
AllyTeam=1;
}
I set the startpostype to 0 (should be fixed or random, AI should have no problem with both of them). AI is RAI, but AAI, KAIK and E323 does the same. They all dies right after game starts (counting goes to zero and you gain control of your comm). When the game is counting (3 -> 0), there is written "AI-bot" in player list and right after it, there is "dead team".
SPADS is running on mITX Atom based motherboard, I (Pavouk) am connecting from Core i5 (in the same subnet as host) machine and it's me who added the bot (is it my PC which computes bots actions or SPADS autoost PC does this?).
I have no problem with running all types of bots on my Core i5 machine when I host the game on it.