Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Headshot rate for RB bots are too high #9

Closed
stefanhendriks opened this issue Aug 27, 2018 · 4 comments
Closed

Headshot rate for RB bots are too high #9

stefanhendriks opened this issue Aug 27, 2018 · 4 comments
Labels

Comments

@stefanhendriks
Copy link
Collaborator

Looks like bots have a very high rate of headshots.

See also: http://forums.bots-united.com/showthread.php?p=67217

@stefanhendriks stefanhendriks changed the title Headshot for RB bots are too high Headshot rate for RB bots are too high Aug 27, 2018
stefanhendriks added a commit that referenced this issue Sep 2, 2018
@stefanhendriks
Copy link
Collaborator Author

I tuned it down a bit

@stefanhendriks
Copy link
Collaborator Author

still too much. Need to check skills system and aiming.

@stefanhendriks
Copy link
Collaborator Author

Comment from forums:

One of favourite bots, would be the best if to fix all bugs. I didn't test this latest version, but in old there is a bug which has noticed still long ago.
If change bot config
[SKILL]
XOffset=1.90221
YOffset=1.9022
ZOffset=1.9022
to Offset = 100 for example 
in the first round bots behave as it is necessary on a config, at once it is visible on imitation of jolting of hands, and in a next round headshots already again. 
Please fix this bug, bot config works only for the first round.

something about loading config not properly? (related to #11 ?)

@stefanhendriks
Copy link
Collaborator Author

interestingly, I found after adding debug statements that in the first round reaction time is:

'ReactionTime()']-[Team TERROR] : minReactTime 0.050000, maxReactTime 0.105113, skill 2, results into 100.057075

(the 100 is added manually by myself so bots don't shoot me)

But the next round:

'ReactionTime()']-[Team TERROR] : minReactTime 0.000000, maxReactTime 0.000000, skill 2, results into 100.000000

notice the min / max react time got to zero...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant