Mapchange Error (CS v1.5)
 

Heyyo,

I looked at some threat titles, and I havn't seen this posted yet, so I wanted to post it just to be safe. But whenever I changelevel, and the server's filled with bots, on the next map that has a smaller amount of players-per-side spawn zones (I normally go from maps like de_dust and de_dust2, into my mapcycled 1st map which is de_survivor), and I use the kickbot command and allova sudden, all the bots in spectator leap onto the T's side! so then my chances of not dying from spawnkill is like, 1/15...

So maybe make it so if they can't join teams after like 30 seconds they just get booted... cause it's hella annoying.

I'm using:
-metamod (something like v1.17..)
-statsme v2.7.1
-CS v1.5
-PODbot v2.6mm R2.40

Re: Mapchange Error (CS v1.5)
 

We know the changelevel is a big problem for bots now. But we will fix this issue probably this week (depanding of sPlOrYgOn's time). And yes, we were writting something about this in last posts of that thread ;):

http://forums.bots-united.com/showthread.php?t=2544

Re: Mapchange Error (CS v1.5)
 

Heyyo,

But uhh... I'm not even using min/max bots, and I commented out the addbot lines in the podbot.cfg, it does save the bots from the previous round though... it's just when I go to kick the bots that are spectating does it randomly add them all to the Terrorist team... I'll take some screenies if it helps?

Re: Mapchange Error (CS v1.5)
 

Wait , please, for the next beta (I hope this weekend can be possible - depanding of sPlOrYgOn's time). First we have to look what we can solve but this tip we were talking about that another thread. Then we will ask You to test again this what You see now (these spectating bots). Because this Your problem is concerning also to the "changelevel" command, we have to do this in this way.

Re: Mapchange Error (CS v1.5)
 

Heyyo,

Ok, I'll wait, no worries aboot having to tell me when it's out, I tend to check these forums on a regular basis, I'll figure out when the next beta's out. ;)

Re: Mapchange Error (CS v1.5)
 

Heyyo,

Ok, I did some tests, and it doesn't occur after mapchange... it just does...

I just finished waypointing de_aztec2 (wasn't in the 1st PODbot v2.6mm custom waypoint pack as planned, so I made some for the next one that twrecks is workin' on... guess I should say that in his thread for it... :P ) n' played with bots, my maxplayers was set to 40, so as usual filled the server n' started playing, I got spawnkilled (crappy worldspawn node things...... I'll eventually make my own) n' decided to boot a CT so it won't happen again... n' what do you know, all the bots in spectator leap onto the CT team... so here's a few screenies:

before kicking a CT bot:
http://www.freewebs.com/mard_lltd/de_aztec20003.JPG

After kicking a CT bot:
http://www.freewebs.com/mard_lltd/de_aztec20004.JPG

A new test, before kicking a T bot:
http://www.freewebs.com/mard_lltd/de_aztec20005.JPG

after kicking a T bot:
http://www.freewebs.com/mard_lltd/de_aztec20006.JPG

BTW, if it makes a diff, I used the ingame podbotmenu to kick T and CT bot, autokick's the same deal, just whatever side the bot's booted from, the rest of the spectating bots leap on there...

Re: Mapchange Error (CS v1.5)
 

Why exactly do You use maxplayers 40? There is a possibility to play only 32 players...;)
OK - this odd behavior sPlOrYgOn also confirmed, but for now we don't have any explanation what can be a cause of this. :(

Re: Mapchange Error (CS v1.5)
 

Heyyo,

I dunno, it's an' old habbit to put it at something rediculously high. I used to think HL could handle 60.. but then I found out it was 32, so I, for some reason, just kept puttin' 40... you never know when someone might wanna spectate... yeah, that must be why... lol. :P

Ok, well, hopefully it's not that hard of a fix... I'll just lay back n' await future releases. ;)

Re: Mapchange Error (CS v1.5)
 

OK - this problem still happens - also in CS1.6 and also with latest pb mm. Just experienced it last days and I couldn't remind where did I read before about it. Just found this topic. :)
Seems - the problem is still not solved yet.