Bugs in release 2.1

[KWo]

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.

[sPlOrYgOn]

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
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]

[KWo]

Originally Posted by sPlOrYgOn

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

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?

Originally Posted by sPlOrYgOn

btw if soulfather ever reads this...
your todo list is outdated

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 ) - 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 .
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.

[Pierre-Marie Baty]

Originally Posted by KWo

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?

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.

[KWo]

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!


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

[sPlOrYgOn]

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...

[KWo]

Originally Posted by sPlOrYgOn

first off...
test 1 and 2 are invalid..
SEEN_SHOOTTHRU MUST be last...

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.

Originally Posted by sPlOrYgOn

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???

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

[sPlOrYgOn]

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..

[KWo]

Originally Posted by sPlOrYgOn

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..

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.

[sPlOrYgOn]

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]