-
Notifications
You must be signed in to change notification settings - Fork 0
Draft: Bot thermoptic behavior experiments #4
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
Draft: Bot thermoptic behavior experiments #4
Conversation
This commit has some extra code that doesn't actually get called, so committing first before experimenting with pruning unused code.
| me->GetLocomotionInterface()->Thermoptic(); | ||
| } | ||
| #endif | ||
|
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I suspect this code is not actually getting called since I started with this approach first and the breakpoint never triggered during the test.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[removed inactive code]
|
With this tracer bullet implementation for thermoptic state querying, bots are now extremely helpless against it, so do not merge in this state. |
Also added aggro for cloak triggering and unsuppressed weapon firing.
Needed to change the scheme for calculating probabilities, because even 1% detection rate multiplied by ~60 ticks a second results in a very high detection rate. Also added distance as a contributing factor for detection.
Also: - support target specific logic - prioritize finishing reloads to avoid decision jitter from reload cancelling weapon change decisions
|
Review continued in: |
Description
Simple thermoptic use logic. Bots simply enable thermoptic cloak if they know of a threat and they have some thermoptic charge available. There is no early shutoff logic and bots have rudimentary checks against thermoptic state.
Toolchain
Linked Issues