Fix: Bot didn't have plan when repathing #1541
Merged
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
Contributor
Author
|
sunzenshen
force-pushed
the
bot-friendly-repath-null-except
branch
from
da2f77b to
70c7dff
Compare
Sometimes a bot doesn't have a path plan when the repathing code triggers around a friendly which leads to an access error.
sunzenshen
added a commit
to sunzenshen/neo
that referenced
this pull request
Dec 13, 2025
AdamTadeusz
approved these changes
Dec 15, 2025
DESTROYGIRL
approved these changes
Dec 16, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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
Sometimes a bot doesn't have a path plan when the repathing code triggers around a friendly which leads to an access error.
Toolchain
Linked Issues