Add check to prevent canpathtoenemy from running for non baseai #4674
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
|
As a side note, When I was testing this (with the Uveso AI being present) I had issues with the hook of MiscBuildConditions.lua file. |
|
Could you elaborate on the issues? |
|
Not related to this PR. Just something I noticed. I'll explore them more on wednesday once I've got a bit more time. |
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 of changes
This PR adds a base ai check to the CanPathToCurrentEnemy function that is run during AI initialization.
This is to prevent the navmesh getting loaded when 3rd party AI's are using the default BaseMonitorInitialization thread