Repository navigation
fix: validate region ownership of cached AI targets - #523
Open
PluginsKers wants to merge 1 commit into
Open
PluginsKers wants to merge 1 commit into
PluginsKers wants to merge 1 commit into
Conversation
PluginsKers
force-pushed
the
fix/region-owned-ai-sensors-v2
branch
from
October 11, 2026 03:00
4f041a1 to
3f588ee
Compare
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
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.
Sensor memories can retain entities after their region ownership changes. Reading those targets can access entity state from the wrong region thread.
Check ownership before evaluating target predicates and cached visibility, before collecting nearby entities, and before
BabyFollowAdultreads a cached or event-replaced target. Clear the cached adult memory when its target is no longer owned.AI tools were used to implement and review the change and write this description.