Bugs in release 2.1
 

I just tryied a little time this latest version of PB2.6mm rel.2.1 made by sPlOrYgOn and what I can see:
If addbot command should work exactly like this line for console commands (line from versionhistory.txt)

pb addbot [skill [personality [team [model [name]]]]]

it doesn't work exactly like this.

Here You have some lines of my podbot.cfg file

detailnames on

addbot 100 1 2 2 Ryback
addbot 100 2 1 1 Roger
addbot 100 3 2 3 James_Bond
addbot 100 1 1 2 Szakal
addbot 100 2 2 2 Rambo
addbot 100 3 1 4 Android
addbot 100 1 1 2 Ivan
addbot 100 2 1 3 Terminator

For example - the personality of James_Bond and Android should be the same, but they aren't (what exactly range - I hope 1-3, but there is nowhere exactly described...). You can see this at my screenshot.

The second thing - I don't know exactly why, but bots are running on the map still looking down, so they can see nobody - the result after 4 rounds You can see at my picture, too.

Tested on listenserver CS1.5 under Win98SE, Metamod 1.17, ClanMod 1.82betat1 , StatsMe 2.8.0 beta7.
For sure podbot_mm.dll (229376 bytes, created 2004.05.11 17:22, why there isn't as a message at game start the version number...) with botskill.cfg and botweapons.cfg and podbot.cfg included in this latest release.

Re: Bugs in release 2.1
 

Sorry for double posting (I know how to use "Edit", but I need a separation for screenshots).

Next tests - after changelevel commands - the same configs like my post above - I didn't added new bots manualy during game, but one bot was added by it self at new map start. Next changelevel and this new bot has changed team (!!!), but second bot was not added by it self (OK). Here is something to do...
You can see results at these two next screenshots.

About this bot's look down - If You don't understand what I mean, the third screenshot should help, I hope...

This is enough for this moment, I think. I don't want to "be nagging" somebody...http://forums.bots-united.com/images/icons/icon10.gif

EDIT

I forgot add, that I use botaim plugin v1.5 , but without this plugin bot play normaly - without looking down. Why nobody said this before, that for this new version of podbot_mm26 we should not load this botaim plugin? >:( Maybe some people like this plugin, too?

/EDIT

Re: Bugs in release 2.1
 

maybe i shoulda posted better instructions..
or change a few things..
so far the personality thing goes from 0-2...
sorry its not 1-3 maybe i can change that later...

Re: Bugs in release 2.1
 

About the bots looking down problem, this is probably a problem with the BotAim plugin configuration.
There is a CVAR that BotAim uses that reverts the X angle (vertical angle) of the bots. I implemented this CVAR because some bots have different ways of handling their aiming code, some of them invert their angles before processing and revert them back after, and some others don't.

Try changing the value of the bot_aim_fix CVAR (or dunno how it's called). Look in the botaim plugin readme file. Your problem is explained here.

Re: Bugs in release 2.1
 

Maybe once again I was not exactly in my description. I wanted say that I use this plugin a long time without any configuration files (all CVAR's by defaults) with all previous version of PODBOT26_mm (except this sPlOrYgOn release 2.0 - I didn't tryied that one) and I never saw this situation. Last update (maybe this previous - I have not tested it) somebody changed something in code. Probably somebody wanted fix this vertical x axis problem in Botman's original aiming code (I remember some posts about this). Maybe this is correct to fix this issue in podbot26mm source - why not? But for me is only one problem - why did noboday say nothing about this change? I didn't found something about this in versionhistory.txt - so for me this bot's behavior was a big unnice surprise...???:(

I'm agree with You - if there is something simple to fix - do this - why not? But please - write something for people and write what result is possible to see after some fix and what should we do to not be unnice surprised...:)

BTW - is this latest version 1.5 of this nice plugin or maybe You have some newer version? :)
I will try change this CVAR tomorrow...

Re: Bugs in release 2.1
 

dude, if I was to put a line in the changelog for every single thing I changed in the bot code, the changelog would be 40 megabytes large as now :)

I didn't thought about the botaim plugin at all when I did it. But I'll try to think about it next time :)

Re: Bugs in release 2.1
 

OK - I 've just tested botaim plugin with this setting:

bot_aim_fix 0

I 've put this line above in podbot.cfg (I hope this is correct place...).

What I saw? Now bots are looking up. So - there is some incompatiblity between podbot2.6mm_rel2.1 and botaim plugin (without this plugin bots behavior is correct), but it's impossible for this moment fix this issue (bot looking up/down) by this parameter written above.
Maybe some another suggestion for possibility use both these files (podbot26mm_rel2.1 and botaim)...:(

Re: Bugs in release 2.1
 

I know this is not what you want, but I'm just wondering: With so many improvements included right in the bot dll now, is the BotAim plugin still necessary at all?
I had it running before, but when I was trying out later PB 2.6mm releases, I kicked it out to make sure any bugs I spotted would be PB bugs and not BotAim-related ones. And I think bots aim just fine without it.

But of course, the ideal case would be that it's possible to run both plugins together without problems... or officially declare that BotAim no longer be used for PB2.6mm because it's obsolete from now on?

Re: Bugs in release 2.1
 

This problem is probably directed to sPlOrYgOn. I tryied if skill parameters are really affected by bot's behavior.
In my podbot.cfg I wrote these lines:

addbot 20 1 2 2 Ryback
addbot 10 2 1 1 Roger
addbot 40 0 2 3 James_Bond
addbot 20 1 1 2 Szakal
addbot 60 2 2 2 Rambo
addbot 40 0 1 4 Android
addbot 60 1 1 2 Ivan
addbot 80 2 1 3 Terminator
addbot 100 0 2 4 Nikita
addbot 100 1 1 3 Luis

I played 30 min. During this time I supposed to see bots with bigger skill at the top of the scoreboard and bots with less skill at bottom of the list. But I was unnice surpriced by killing me many times by bots with skill 20 by headshot (I use StatsMe, so I triggered this). OK - I can say this - I didn't see the differnece between bot (20) and bot (100). They was shooting and killing them many times by headshot. I have a log , but I translated StatsMe to polish, so I can't show this log, because this will be for You not-understanding. But I made one screenshot more for show the scoreboard. I think my test was disinterested. I think You go back to the problem of podbot2.0 (old CountFloyd bot's problem corresponding to taking parameters from botskill.cfg and using their correctly) and this is still not fixed.:(

EDIT
I forgot to add - this test was made of course without botaim plugin - look to another post - impossible now use both simultaneously.

/EDIT

Re: Bugs in release 2.1
 

KWo it actually is "fixed"..
at least the botskill.cfg is fully taken in instead of only a few values..
You should change the values to your liking until you find a good value for each skill level.
Personality also affects how good they do.
because personality affects which weapons they like..
and not all the weapons are the same so if certain bots like a strong rifle better then they probably have a good chance to be very good.
also their attack movement is VERY messed up..
they love hopping up and down while shooting with a very inaccurate gun.. which can sometimes lead to a lot of headshots even tho they were aiming at their enemy's body.
I'm not sure what to do with the attack movement until i get more ideas about how stupid / godlike bots are supposed to move..
also i'm a little preoccupied with the NUM_FOR_EDICT bug I can't seem to fix :(

Re: Bugs in release 2.1
 

OK - now I see my mistake - I should put bots to the game with the same personality and different skill - in this case maybe I can see something, but if there is some extra aiming code added - I can't see the differences. So as result I can see this is not fixed (because I don't know if this is skill level problem or extra aiming code problem - how can I check this?). AIM_OFFSET should work like propability of hit in the range specyfied in AIM_OFFSET - this means if bot is trying to hit me it should try shoot to this range. But if I see it shoot me and kill me by headhot much more oftenn than I suppose this - for me this is not working. OK - don't forget about SF priority TO_DO_LIST and some bugs making server unstable - like this NUM_FOR_EDICT. This is much more important and we can go back to tests with botskills parameters in the future - when You have a time and other much more problems will be fixed.
Thanks for Your patience for me.http://forums.bots-united.com/images/icons/icon5.gif

Re: Bugs in release 2.1
 

try putting all the AIM_OFFSETs at 1000...
you WILL see the difference...
in previous versions the AIM_OFFSET was ignored completely.
probably even in 2.5

also play around with the turning speeds...
the stupid bots seem to turn "smoother" because they got such a low turn speed..
if you increased them all to 50 or so it would seem like they turn around in an instant.

[edit]
btw if soulfather ever reads this...
your todo list is outdated :D
a few of those things are already done.
such as the weapon restrictions not working..
except jasonmode still has that bug where they might use a pistol.
that grenade throwing bug fix was already applied by pmb but thats not the problem that makes them throw it in the wrong direction.
botskill.cfg not working is fixed...
min/max bot works...
and i think thats it..
[/edit]

Re: Bugs in release 2.1
 

I said only "I can't see the differences between bot 20 and 100". I believe You that You load the value from botskill.cfg correctly, but I'm not sure if this is loaded correctly to different bots (one with skill 10 another with skill 100) - for me they was shooting me and them-self without differences. Maybe some other part of code is responsible for this result that I can see. Maybe I should really incrase the AIM_OFFSET for stupid bots to see the difference. OK , this evening I'll try this - after I'll write the results once again.

BTW - it was me - I was found this AIM_OFFSET ignored completly in PB26. In PB25 it was loaded but for sure was not working correctly whole parameters from botskill.cfg .

About this turning - yes I know this - it was me I posted this 2 years ago at nuclearbox how to interprate this parameter. Because of this I tryied low value for example 1.2 - if fps_max is 50 , in this case during one second bot can turn 60 degrees. But now I'm not sure about this "frame" in CountFlyd's description:

MIN/MAX_TURNSPEED is the number of Degrees allowed to turn in 1 Frame.

Maybe the frame is meaning frame of data send to bot-client from server? Or maybe however this is according to fps for screen? Who knows this?


Yes - there are some ideas accepted even by PMB, some of their are now even made by You (for example this kicking bot from selected team - it's working OK http://forums.bots-united.com/images/icons/icon8.gif) - but this post-thread is not updated. OK - maybe he is now busy - he made big work for testing new dll and re-waypointing standard maps and probably for non-standard now he do the same. OK - don't stress him now. For this only me - I have a license . http://forums.bots-united.com/images/icons/icon8.gifhttp://forums.bots-united.com/images/icons/icon10.gif
He asked coders to write in this his post what is fixed. I don't know exactly how can You change his post? Additionally the thread is closed...Maybe simply write to PMB post-message with list what is fixed and what is new to fix and ask PMB to update this list by him - he probably can do this.

Re: Bugs in release 2.1
 

A frame is one pass of the game loop cycle. It is how often the server "thinks". On a listen server it corresponds to a video frame on the server. On a dedicated server it corresponds to the fps value that is displayed in the server console.

Re: Bugs in release 2.1
 

Like I promised before - I tryied these parameters from botskill.cfg. Tests duration time - about 6h. I 've tryied reversed and normal order of parameters in this botskill.cfg.

The first attachement is a screenshot after 2h tests.
The bostkill.cfg in that time (1 test) was following:

# Settings for Bots Skill 0-19
SEEN_SHOOTTHRU 25
HEAR_SHOOTTHRU 20
HEADSHOT_ALLOW 0
AIM_OFFS_Z 600.0
AIM_OFFS_Y 500.0
AIM_OFFS_X 500.0
MAX_TURNSPEED 1.2
MIN_TURNSPEED 0.8
MAX_DELAY 1.3
MIN_DELAY 1.0

# Settings for Bots Skill 20-39
SEEN_SHOOTTHRU 40
HEAR_SHOOTTHRU 30
HEADSHOT_ALLOW 10
AIM_OFFS_Z 420.0
AIM_OFFS_Y 300.0
AIM_OFFS_X 300.0
MAX_TURNSPEED 1.6
MIN_TURNSPEED 1.2
MAX_DELAY 1.0
MIN_DELAY 0.7

# Settings for Bots Skill 40-59
SEEN_SHOOTTHRU 55
HEAR_SHOOTTHRU 40
HEADSHOT_ALLOW 30
AIM_OFFS_Z 320.0
AIM_OFFS_Y 200.0
AIM_OFFS_X 200.0
MAX_TURNSPEED 2.0
MIN_TURNSPEED 1.6
MAX_DELAY 0.7
MIN_DELAY 0.5

# Settings for Bots Skill 60-79
SEEN_SHOOTTHRU 70
HEAR_SHOOTTHRU 50
HEADSHOT_ALLOW 60
AIM_OFFS_Z 180.0
AIM_OFFS_Y 100.0
AIM_OFFS_X 100.0
MAX_TURNSPEED 2.4
MIN_TURNSPEED 2.0
MAX_DELAY 0.5
MIN_DELAY 0.3

# Settings for Bots Skill 80-99
SEEN_SHOOTTHRU 85
HEAR_SHOOTTHRU 60
HEADSHOT_ALLOW 80
AIM_OFFS_Z 100.0
AIM_OFFS_Y 50.0
AIM_OFFS_X 50.0
MAX_TURNSPEED 3.6
MIN_TURNSPEED 2.4
MAX_DELAY 0.3
MIN_DELAY 0.1

# Settings for Bots Skill 100
SEEN_SHOOTTHRU 100
HEAR_SHOOTTHRU 70
HEADSHOT_ALLOW 100
AIM_OFFS_Z 0.0
AIM_OFFS_Y 0.0
AIM_OFFS_X 0.0
MAX_TURNSPEED 3.6
MIN_TURNSPEED 3.4
MAX_DELAY 0.1
MIN_DELAY 0.0

==============================================

Because the min/max trurnspeed I slowed too much down, I made second test and there is a second screenshot with results. Here is the botskill.cfg used by me in this second test:


# Settings for Bots Skill 0-19
SEEN_SHOOTTHRU 25
HEAR_SHOOTTHRU 20
HEADSHOT_ALLOW 0
AIM_OFFS_Z 640.0
AIM_OFFS_Y 500.0
AIM_OFFS_X 500.0
MAX_TURNSPEED 1.8
MIN_TURNSPEED 1.2
MAX_DELAY 1.3
MIN_DELAY 1.0

# Settings for Bots Skill 20-39
SEEN_SHOOTTHRU 40
HEAR_SHOOTTHRU 30
HEADSHOT_ALLOW 10
AIM_OFFS_Z 420.0
AIM_OFFS_Y 300.0
AIM_OFFS_X 300.0
MAX_TURNSPEED 2.4
MIN_TURNSPEED 1.8
MAX_DELAY 1.0
MIN_DELAY 0.7

# Settings for Bots Skill 40-59
SEEN_SHOOTTHRU 55
HEAR_SHOOTTHRU 40
HEADSHOT_ALLOW 30
AIM_OFFS_Z 320.0
AIM_OFFS_Y 200.0
AIM_OFFS_X 200.0
MAX_TURNSPEED 3.6
MIN_TURNSPEED 2.4
MAX_DELAY 0.7
MIN_DELAY 0.5

# Settings for Bots Skill 60-79
SEEN_SHOOTTHRU 70
HEAR_SHOOTTHRU 50
HEADSHOT_ALLOW 60
AIM_OFFS_Z 180.0
AIM_OFFS_Y 100.0
AIM_OFFS_X 100.0
MAX_TURNSPEED 5.4
MIN_TURNSPEED 3.6
MAX_DELAY 0.5
MIN_DELAY 0.3

# Settings for Bots Skill 80-99
SEEN_SHOOTTHRU 85
HEAR_SHOOTTHRU 60
HEADSHOT_ALLOW 80
AIM_OFFS_Z 100.0
AIM_OFFS_Y 50.0
AIM_OFFS_X 50.0
MAX_TURNSPEED 7.2
MIN_TURNSPEED 5.4
MAX_DELAY 0.3
MIN_DELAY 0.1

# Settings for Bots Skill 100
SEEN_SHOOTTHRU 100
HEAR_SHOOTTHRU 70
HEADSHOT_ALLOW 100
AIM_OFFS_Z 0.0
AIM_OFFS_Y 0.0
AIM_OFFS_X 0.0
MAX_TURNSPEED 7.2
MIN_TURNSPEED 7.0
MAX_DELAY 0.1
MIN_DELAY 0.0

=======================================


Because I saw that in this reversed order bots with skill 10 have almost the same behavior like bots with skill 100 (almost the same results at scoreboard), I changed the order of parameters to normal (like in original file from sPlOrYgOn - only value are different) - and it was test number 3 and You can see the cfg here and there is a third screenshot after this test.

# Settings for Bots Skill 0-19
MIN_DELAY 1.0
MAX_DELAY 1.3
MIN_TURNSPEED 1.2
MAX_TURNSPEED 1.8
AIM_OFFS_X 500.0
AIM_OFFS_Y 500.0
AIM_OFFS_Z 640.0
HEADSHOT_ALLOW 0
HEAR_SHOOTTHRU 20
SEEN_SHOOTTHRU 25

# Settings for Bots Skill 20-39
MIN_DELAY 0.7
MAX_DELAY 1.0
MIN_TURNSPEED 1.8
MAX_TURNSPEED 2.4
AIM_OFFS_X 300.0
AIM_OFFS_Y 300.0
AIM_OFFS_Z 420.0
HEADSHOT_ALLOW 10
HEAR_SHOOTTHRU 30
SEEN_SHOOTTHRU 40

# Settings for Bots Skill 40-59
MIN_DELAY 0.5
MAX_DELAY 0.7
MIN_TURNSPEED 2.4
MAX_TURNSPEED 3.6
AIM_OFFS_X 200.0
AIM_OFFS_Y 200.0
AIM_OFFS_Z 320.0
HEADSHOT_ALLOW 30
HEAR_SHOOTTHRU 40
SEEN_SHOOTTHRU 55

# Settings for Bots Skill 60-79
MIN_DELAY 0.3
MAX_DELAY 0.5
MIN_TURNSPEED 3.6
MAX_TURNSPEED 5.4
AIM_OFFS_X 100.0
AIM_OFFS_Y 100.0
AIM_OFFS_Z 180.0
HEADSHOT_ALLOW 60
HEAR_SHOOTTHRU 50
SEEN_SHOOTTHRU 70

# Settings for Bots Skill 80-99
MIN_DELAY 0.1
MAX_DELAY 0.3
MIN_TURNSPEED 5.4
MAX_TURNSPEED 7.2
AIM_OFFS_X 50.0
AIM_OFFS_Y 50.0
AIM_OFFS_Z 90.0
HEADSHOT_ALLOW 80
HEAR_SHOOTTHRU 60
SEEN_SHOOTTHRU 85

# Settings for Bots Skill 100
MIN_DELAY 0.0
MAX_DELAY 0.1
MIN_TURNSPEED 7.0
MAX_TURNSPEED 7.2
AIM_OFFS_X 0.0
AIM_OFFS_Y 0.0
AIM_OFFS_Z 0.0
HEADSHOT_ALLOW 100
HEAR_SHOOTTHRU 70
SEEN_SHOOTTHRU 100

============================================

Because bots with skill 100 and 90 have almost the same behavior (almost the same frags' results) - I 've changed for bots with skill 100 the min_max trurnspeed like in original sPlOrYgOn file. This was without any tests but You can try now at Your computers (if You have time). Don't forget to change min/max botskill parameters in podbot.cfg file if You want to compare for example bots with skill 30 to bot with skill 85.

Here is my recommend to use botskill.cfg file:

# Settings for Bots Skill 0-19
MIN_DELAY 1.0
MAX_DELAY 1.3
MIN_TURNSPEED 1.2
MAX_TURNSPEED 1.8
AIM_OFFS_X 500.0
AIM_OFFS_Y 500.0
AIM_OFFS_Z 640.0
HEADSHOT_ALLOW 0
HEAR_SHOOTTHRU 20
SEEN_SHOOTTHRU 25

# Settings for Bots Skill 20-39
MIN_DELAY 0.7
MAX_DELAY 1.0
MIN_TURNSPEED 1.8
MAX_TURNSPEED 2.4
AIM_OFFS_X 300.0
AIM_OFFS_Y 300.0
AIM_OFFS_Z 420.0
HEADSHOT_ALLOW 10
HEAR_SHOOTTHRU 30
SEEN_SHOOTTHRU 40

# Settings for Bots Skill 40-59
MIN_DELAY 0.5
MAX_DELAY 0.7
MIN_TURNSPEED 2.4
MAX_TURNSPEED 3.6
AIM_OFFS_X 200.0
AIM_OFFS_Y 200.0
AIM_OFFS_Z 320.0
HEADSHOT_ALLOW 30
HEAR_SHOOTTHRU 40
SEEN_SHOOTTHRU 55

# Settings for Bots Skill 60-79
MIN_DELAY 0.3
MAX_DELAY 0.5
MIN_TURNSPEED 3.6
MAX_TURNSPEED 5.4
AIM_OFFS_X 100.0
AIM_OFFS_Y 100.0
AIM_OFFS_Z 180.0
HEADSHOT_ALLOW 60
HEAR_SHOOTTHRU 50
SEEN_SHOOTTHRU 70

# Settings for Bots Skill 80-99
MIN_DELAY 0.1
MAX_DELAY 0.3
MIN_TURNSPEED 5.4
MAX_TURNSPEED 7.2
AIM_OFFS_X 50.0
AIM_OFFS_Y 50.0
AIM_OFFS_Z 100.0
HEADSHOT_ALLOW 80
HEAR_SHOOTTHRU 60
SEEN_SHOOTTHRU 85

# Settings for Bots Skill 100
MIN_DELAY 0.0
MAX_DELAY 0.1
MIN_TURNSPEED 10.0
MAX_TURNSPEED 12.0
AIM_OFFS_X 0.0
AIM_OFFS_Y 0.0
AIM_OFFS_Z 0.0
HEADSHOT_ALLOW 100
HEAR_SHOOTTHRU 70
SEEN_SHOOTTHRU 100


============================================


Try this and say if this is working for all - if now all people can see the differences between all ranges of botskill , maybe I will ask to sPlOrYgOn to include this cfg to the next release.
sPlOrYgOn,these parameters are really working!!! :)

Nice game for all! http://forums.bots-united.com/images/icons/icon5.gif


BTW - It's 2:33AM and it's big time for sleep . I'm realy tired now. 8)

Re: Bugs in release 2.1
 

first off...
test 1 and 2 are invalid..
SEEN_SHOOTTHRU MUST be last...
and that final config's aim offsets are too huge...
you must have a headache after looking at them aiming...
they higher the values the more they "shake".
and how slow do normal people turn???
thats way too slow...
You'll end up with a lot of bots facing the wrong way when rushing out...
once again the AIM OFFSETS are too big..
have you seen them trying to aim long range?
even with an AIMOFFSET of 80 each they will almost never hit the other person from one side of the underpass in de_dust to the other side...

thats about all i have to say...

Re: Bugs in release 2.1
 

OK - forget about these two tests - i ve tryied according to order of parameters found by me in Your podbot_mm.dll . If You said that this is incorrect - OK. Never use the reversed order of these parameters.

Botskill 0-19 have to be for begginers, so this one have to be really slowly and with very bad aim. The next skills are bit better until to perfect (godlike) bot with skill 100. Like I said before - playing with Your botskill.cfg file I didn't see the difference between bot 20 and bot 100 after half hour of game with them. And because of this I made all these tests and I show the results. I know - now You are a godlike player in this game, so You don't care about begginers, but You want the bot have to be perfect with skill 100. But for beginners this bot have to be really slowly and with really bad aim.

OK - wait for reply from other users.;)

EDIT

BTW - have You looked at these screenshots? There is an answer if these value are really too big for all botskill ranges.;)

/EDIT

Re: Bugs in release 2.1
 

I don't think you understand how badly they aim with over 100 offset...
It's really really horrible..
you can almost expect not to be hurt..

Re: Bugs in release 2.1
 

Try to understand one thing - the game it's not only a camping from long distance. The game is trying to hit an enemy in the movement from low distance, too. And for this these big values are OK - for beginners and for people wanted change their skill step by step - not from beginners directly to almost godlike.
Maybe is better when You try as a spectator the game with my parameters?

OK - this is Your point of view - I'm waiting for reply of users.;)

Re: Bugs in release 2.1
 

Who ever said you had to camp to be at long range???
have you tried these settings with awp_map?

[edit]
my baby brother plays better than the bots with 80-99 skill level with you cfg...
[/edit]

Re: Bugs in release 2.1
 

Ok, ok - in order to fulfill KWo's request for feedback from others, I'm gonna test this config. I might be a good test subject because I hardly play CS any more - most of what I do currently is waypointing and spectating my bots to see how the waypoints turned out... 9_9
So from a good bot I'd expect that top skill bots would be really tough enemies. We shall see... more on this tomorrow.

Re: Bugs in release 2.1
 

I was tired last night and I forgot to add some results of observation:

1. Bots don't use zoom when they have aug or SG-552 (they never used zoom during 6h of my tests).

2. Many times bots T had problem with planting bomb - I heard clicking of weapon (AK-47 or other) - like after finishing of ammo and they coudn't start the sequence of arming the bomb.

EDIT

3. Many times I saw the situation - bot was walking and looking at the wall (in this case he didn't see an enemy at its back - behind it). Bot remember the direction of last visible enemy and it is walking and looking still in this direction (regardless of its skill). I think - it should much more look around to better see the situation.

/EDIT

Re: Bugs in release 2.1
 

i play with random bots skilled 95-99 (as i knew there was a bug with 100 from early versions of 2.5 n stuff)

95-99 is pretty good i can't get to the top of the ranks :( coz i always die...
but when i play on a human server i can get in to the top3 of my team easy on anymap but with bots i get killed :'(

Re: Bugs in release 2.1
 

Have You tryied my recomended botskill.cfg posted few posts above in this thread? If yes - try lower botskill - for example 80-85. If You use the original botskill.cfg (made by sPlOrYgOn) - I noticed this above, too - for me there is not difference play with bot (100) or bot (50) - they kill me by a headshot almost everytime and this can make some frustration. Because of this I re-edited this botskill.cfg file.

Re: Bugs in release 2.1
 

known about all 3 above..
1. it only checks for sniper rifles right now...
2. I don't know whats wrong. It checks if it's got the c4 out...
3. They're looking at either some sound, dangerous waypoint, or last enemy.

and my baby bro is owning the bots with 80-99 skill level with your configs KWo... and he's only 5 years old..

Re: Bugs in release 2.1
 

OK...- try at begining to divide all my AIM_OFFS by 2 (if there I put 100 - try put 50 etc...) and give some feedback here - if after this he should change down the skill of bot to play with them or still not. And try first on standard map , for example de_dust2 (for now not on awp).

BTW - how long time is your brother playing this game (how old was he when he started play)?:)

[EDIT]
You probably have another problem - with MIN/MAX TURNSPEED
Look here:

http://forums.bots-united.com/showpo...4&postcount=14

What I mean? If Your brother is playing on listenserver P2 400MHz with 30fps , the real turnspeed of bots are slower than these mines (I have 50fps). So - You have to multiple all my MIN/MAX TURNSPEED by the value x=50/30 - to see the same what I see on my computer.
This is strange - for the future - mybe will be better define these parameters basic not at "frame" but at the time (for example 1 second - I mean this for example 30 degree for 1s).8)

[/EDIT]