Skip to content

Anchor API sanity - #6990

Open
metalgearsloth wants to merge 1 commit into
space-wizards:masterfrom
metalgearsloth:2026-06-21-rainbow6-anchor
Open

Anchor API sanity#6990
metalgearsloth wants to merge 1 commit into
space-wizards:masterfrom
metalgearsloth:2026-06-21-rainbow6-anchor

Conversation

@metalgearsloth

Copy link
Copy Markdown
Contributor
  • Removes the property
  • Anchoring now works as expected so anchoring twice doesn't silently corrupt.
  • Kills ReAnchorEvent because any perf gains are not worth the bugs.

PR from the other repo.

- Removes the property
- Anchoring now works as expected so anchoring twice doesn't silently corrupt.
- Kills ReAnchorEvent because any perf gains are not worth the bugs.
@whatston3

Copy link
Copy Markdown
Contributor

Does this resolve #6739?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm excited to see these warnings finally go away!

@DrSmugleaf DrSmugleaf left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm on my (half broken) phone so checking would take a while but does this add a VV path for anchored? Or make setting the field directly work
A lot of admins toggle anchored with VV so removing that for them would be very bad
Could just keep the setter around as a private setter maybe

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants