sk_tripmine_use_owner_relations: Tripmines can use owner entity's relationships instead of default relationships #248
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
…owner entity's relationships instead of default relationships
Blixibon
approved these changes
Mar 2, 2024
1upD
pushed a commit
that referenced
this pull request
Mar 7, 2024
Fixed warnings about conversions between soundlevel_t and float
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.
This PR will add a new ConVar sk_tripmine_use_owner_relations. When sk_tripmine_use_owner_relations is 1, tripmines will check the owner entity's relationship to the target. This will allow tripmines to respect ai_relationship entities and other non-default relationships.
Does this PR close any issues?
PR Checklist
developbranch OR targets another branch with a specific goal in mind