Skip to content

Improve performance of protection checks under Paper - #275

Open
Phoenix616 wants to merge 1 commit into
pop4959:paperfrom
Phoenix616:pr/use-paper-non-snapshot-state
Open

Improve performance of protection checks under Paper#275
Phoenix616 wants to merge 1 commit into
pop4959:paperfrom
Phoenix616:pr/use-paper-non-snapshot-state

Conversation

@Phoenix616

Copy link
Copy Markdown
Contributor

Improve performance of protection checks under Paper by not creating a snapshot for each block.

Previously this could cause lag spikes if something (like hoppers or other plugins which move items) would check lots of blocks for protections at the same time. I tried to check the logic which uses those objects/methods whether they actually would require a snapshot and I couldn't find any.

@pop4959

pop4959 commented Aug 3, 2026

Copy link
Copy Markdown
Owner

Good find, seems like a reasonable change - I don't think we use the snapshots anywhere. Do you know if this also works on Spigot, or is it Paper only?

@Phoenix616

Copy link
Copy Markdown
Contributor Author

This is a Paper-only api addition.

@pop4959

pop4959 commented Aug 4, 2026

Copy link
Copy Markdown
Owner

Thanks that's kind of what I thought, but I didn't have time to check. There's still a bit to figure out b/w the Spigot and Paper implementation going forwards but now that we have them essentially split after hard fork this should make sense to do. In the past it was mostly that no one bothered to make it cross compatible.

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.

2 participants