removed NavigateTowards2dNodes attribute, instead push parent values downwards by searching appropriate component (fixes #20)
#25
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
Abb4
force-pushed
the
fixing-#20-by-removing-circular-reference
branch
2 times, most recently
from
9f2f394 to
c5112f2
Compare
…s downwards by searching appropriate component (fixes #20)
Abb4
commented
Aug 10, 2023
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.
fixes Verify that scene load issue is gone #20
apparently the reference to
NavigateTowards2dNodesbyNavMesh2DSeekeras an attribute is what caused the errorNavMesh2DSeekerto push values set in the editor downstream to the componentGetNodeto find the componentGetNode(specificallyTryFindNodeInChildrenRecursivelyhelper function)(Yes it was neither the cashe nor the naming 🙈)