Add ModInterop for adding ignored anchor fields#53
Merged
aonkeeper4 merged 5 commits intodevfrom Mar 17, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Currently, entity containers check against every field in all base classes of a contained entity for "anchors" (fields which happen to have the same value as the entity's
Position) which it assumes are meant to always hold thePositionof the entity, and will update them accordingly. This is obviously not always the case, so this PR adds ModInterop to support excluding fields from being anchors. The current implementation respects inheritance, so excluding a field on a base class will also automatically exclude it on any derived classes.