TF2 Bot Class Problem, They like being engineers Options

[Spacetech]

I have an exec file with

CODE

sv_cheats 1
rcbotd addbot 1 2 Scout
rcbotd addbot 2 2 Sniper
rcbotd addbot 3 2 Soldier
rcbotd addbot 4 2 Demoman
rcbotd addbot 6 2 Heavy
rcbotd addbot 8 2 Spy
rcbotd addbot 9 2 Engineer
sv_cheats 0

Everytime I run it all the bots spawn as the correct class, but then not even a second later they all change to engineer.
Heres a log of it

L 10/19/2009 - 20:04:46: "Scout<16><BOT><Unassigned>" joined team "Spectator"
L 10/19/2009 - 20:04:46: "Scout<16><BOT><Spectator>" joined team "Red"
L 10/19/2009 - 20:04:46: "Scout<16><BOT><Red>" changed role to "soldier"
L 10/19/2009 - 20:04:46: "Scout<16><BOT><Red>" changed role to "engineer"

Any reason why it would be doing this?
I'm running the latest RCBot 0.52 beta.

[Fillmore]

I have an exec file with

CODE

sv_cheats 1
rcbotd addbot 1 2 Scout
rcbotd addbot 2 2 Sniper
rcbotd addbot 3 2 Soldier
rcbotd addbot 4 2 Demoman
rcbotd addbot 6 2 Heavy
rcbotd addbot 8 2 Spy
rcbotd addbot 9 2 Engineer
sv_cheats 0

Everytime I run it all the bots spawn as the correct class, but then not even a second later they all change to engineer.
Heres a log of it

Any reason why it would be doing this?
I'm running the latest RCBot 0.52 beta.

have you tried adding a delay between addbots?

[Cheeseh]

have you tried adding a delay between addbots?

because the way bots are added at the moment (because of the Valve / Steam / game Engine problem!) .. there needs to be a little time before each bot is added before it goes to the right class etc,

They are probably going engineer because the last bot that is added is an engi and it has overidden the desired class for the next bot to join

[NightHawk]

because the way bots are added at the moment (because of the Valve / Steam / game Engine problem!) .. there needs to be a little time before each bot is added before it goes to the right class etc,

They are probably going engineer because the last bot that is added is an engi and it has overidden the desired class for the next bot to join

For whatever reason, when I tried that, I had similar results.
When I ran across this solution it made no sense as to why it works but it does:

I have a fle called bots.cfg in the cfg folder and execute it as needed


sv_cheats 1
alias "redbotScout" "rcbot addbot 1 2 Speedy"
alias "redbotSniper" "rcbot addbot 2 2 EagleEye"
alias "redbotSoldier" "rcbot addbot 3 2 SgtRock"
alias "redbotDemo" "rcbot addbot 4 2 KaBOOM"
alias "redbotHeavy" "rcbot addbot 6 2 Ivan"
alias "redbotPyro" "rcbot addbot 7 2 Pyro"
alias "redbotSpy" "rcbot addbot 8 2 James"
alias "redbotEng" "rcbot addbot 9 2 Engy"
alias "bluebotScout" "rcbot addbot 1 3 Quicky"
alias "bluebotSniper" "rcbot addbot 2 3 DeadEye"
alias "bluebotSoldier" "rcbot addbot 3 3 Rambo"
alias "bluebotDemo" "rcbot addbot 4 3 Bomber"
alias "bluebotHeavy" "rcbot addbot 6 3 Igor"
alias "bluebotPyro" "rcbot addbot 7 3 FireBug"
alias "bluebotSpy" "rcbot addbot 8 3 Bond"
alias "bluebotEng" "rcbot addbot 9 3 Scotty"
alias "botloadscript" "wait 300; redbotScout; wait 50; bluebotScout; wait 50; redbotDemo; wait 50; bluebotDemo; wait 50; redbotPyro; wait 50; bluebotPyro; wait 50; redbotEng; wait 50; bluebotEng; wait 50; redbotSpy; wait 50; bluebotSpy"
botloadscript


[I meant to add - that if I did not do it by using ALIAS, even with the WAITs in place, I got weird results. Can someone explain why that would matter?]