Reduce capture response delay time #2147
Merged
Conversation
This file contains 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
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.
What type of PR is this.
What have you changed and why?
Approximately halved the maximum capture response delay. See #2146.
Also removed the case where if you captured a marker outside mission radius, the response would be delayed until the marker despawned. Not sure what the purpose of this was, but it feels weird and exploitable.
Not happy with the response + delay mechanic in general as it feels very artificial with the intentional flag flips, but it'll have to do for the moment.
Please specify which Issue this PR Resolves.
closes #2146
Please verify the following and ensure all checks are completed.
Is further testing or are further changes required?