Conversation
wjt
added this pull request to stack #2889
September 14, 2026 15:23
Previously if either of these properties were unset, the game would crash. Both these properties are required for proper functionality but it's kinder to show a warning in the editor and then have the enemy do the best it can at runtime. Doing this will also help to make a challenge scene for learners where they have to correctly configure the enemy before improving its path.
wjt
force-pushed
the
wjt/void-spreading-enemy-don-t-crash-if-void-layer-or-path-are-unset
branch
from
September 14, 2026 15:25
9ed4b51 to
b85b002
Compare
manuq
approved these changes
Sep 14, 2026
| warnings.append("Void Layer not set. The enemy cannot cover the world or consume props") | ||
|
|
||
| if not idle_patrol_path: | ||
| warnings.append("Idle Patrol Path not set. The enemy will be invisible when idle") |
Collaborator
There was a problem hiding this comment.
Yeah, it will be invisible as a consequence of being in the same position / not moving.
manuq
deleted the
wjt/void-spreading-enemy-don-t-crash-if-void-layer-or-path-are-unset
branch
September 14, 2026 15:28
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Previously if either of these properties were unset, the game would crash.
Both these properties are required for proper functionality but it's
kinder to show a warning in the editor and then have the enemy do the
best it can at runtime. Doing this will also help to make a challenge
scene for learners where they have to correctly configure the enemy
before improving its path.