botskill.cfg interpreted wrong!

[sPlOrYgOn]

in botskill.cfg there's something like this:

MIN_DELAY 0.00
MAX_DELAY 0.00
MIN_TURNSPEED 0.6
MAX_TURNSPEED 0.8
AIM_OFFS_X 0.0
AIM_OFFS_Y 0.0
AIM_OFFS_Z 0.0
HEADSHOT_ALLOW 1
HEAR_SHOOTTHRU 100
SEEN_SHOOTTHRU 100

but the thing is...
only MIN_DELAY, MAX_DELAY, HEADSHOT_ALLOW, HEAR_SHOOTTHRU, and SEEN_SHOOTTHRU are interpreted.
more over...
HEADSHOT_ALLOW is being interpreted as the headshot frequency.
so according to my botskill.cfg bots with a skill level of 40 and up have 1 percent chance of headshot...

[>BKA< T Wrecks]

Originally Posted by sPlOrYgOn

HEADSHOT_ALLOW is being interpreted as the headshot frequency.
so according to my botskill.cfg bots with a skill level of 40 and up have 1 percent chance of headshot...

Did you see the link to the nukebox forum KWo posted in one of his threads? Because there he posted a corrected botskill.cfg. I'm using it, and those bots certainly headshot everything into pieces. Of course, this new cfg can't fix the problem that certain parameters aren't read and interpreted at all, but at least it helps to get around the headshot problem...
However, there's one thing I'd like to know about this headshot probability setting (for that's what it is, not headshot on/off) - does "100" (=100%) mean that the bot will score a headshot 100% of all intents? Or does this mean his chance to score a headshot is 100% the normal probability, without any penalty?

[SoUlFaThEr]

please post that fixed headshot set up that Kwo mae......would be cool to see.

[>BKA< T Wrecks]

Ah, I don't find it right now, so here's the corresponding text from the botskill I'm using right now (even better, cause KWo accidentally got 2 max- and min-values mixed up originally. He corrected that later, but didn't post all the stuff again just because of 2 corrected numbers.
Uhm... I guess I'm gonna mark this as "code", although it isn't...

# Settings for Bots Skill 0-19
SEEN_SHOOTTHRU 25
HEAR_SHOOTTHRU 20
HEADSHOT_ALLOW 0
AIM_OFFS_Z 40.0
AIM_OFFS_Y 50.0
AIM_OFFS_X 50.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 42.0
AIM_OFFS_Y 30.0
AIM_OFFS_X 30.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 32.0
AIM_OFFS_Y 20.0
AIM_OFFS_X 20.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 18.0
AIM_OFFS_Y 10.0
AIM_OFFS_X 10.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 10.0
AIM_OFFS_Y 5.0
AIM_OFFS_X 5.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

Play around with it and enjoy - credits to KWo...

[sPlOrYgOn]

Originally Posted by >BKA< T Wrecks

Did you see the link to the nukebox forum KWo posted in one of his threads? Because there he posted a corrected botskill.cfg. I'm using it, and those bots certainly headshot everything into pieces. Of course, this new cfg can't fix the problem that certain parameters aren't read and interpreted at all, but at least it helps to get around the headshot problem...
However, there's one thing I'd like to know about this headshot probability setting (for that's what it is, not headshot on/off) - does "100" (=100%) mean that the bot will score a headshot 100% of all intents? Or does this mean his chance to score a headshot is 100% the normal probability, without any penalty?

it means he'll aim for the head 100% of the time.
I know how to fix it but it changes a lot...
I'll even be changing HEADSHOT_ALLOW to HEADSHOT_FREQUENCY

also I'm editing how the bot aims.
I'm making it so that he recalculates his aim every 0.1 second and I added their aim offsets to their aim to make them aim like crap more....