[TF2] Add ForceDifficultyBasedAim CTFBot flag to allow MvM missions to let Spies aim better #1520
+7
−1
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…t Spies aim better
|
I think a better way would be to make it depend on the bot skill and use the imprecise aim for all skill levels except expert. it doesn't need a whole new attribute. |
Because bot difficulty controls more than just this aim setting, we have to maintain compatibility with the potential existing use case of someone intentionally using Expert Spy with the handicapped aim behavior. |
Bitl
added a commit
to BitlDevelopmentStudios/source-sdk-2013-bds-base
that referenced
this pull request
Sep 7, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Fixes ValveSoftware/Source-1-Games#7538
This adds a flag that popfiles can use to let spies use default aiming behavior instead of handicapped aiming behavior.
Since the default behavior is used if the flag isn't present, there should be no incompatibility issues if this is added.