Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: Move EntityMoveProcessor to portals module, only check entities in worlds with activated portals #217

Merged

Conversation

thatfulvioguy
Copy link
Contributor

EntityMoveProcessor can be quite expensive and is only used for portals. Moving it to the portals module means the performance cost is only paid for servers that use portals. There's also no need to check for movement of all entities when no portals are activated - instead, only check entities in worlds with active portals.

…in worlds with activated portals

EntityMoveProcessor can be quite expensive and is only used for portals. Moving
it to the portals module means the performance cost is only paid for servers
that use portals. There's also no need to check for movement of all entities
when no portals are activated - instead, only check entities in worlds with
active portals.
@oddlama
Copy link
Owner

oddlama commented Aug 26, 2023

Thanks a lot, LGTM!

@oddlama oddlama merged commit 6057796 into oddlama:develop Aug 26, 2023
1 check passed
@thatfulvioguy thatfulvioguy deleted the move-entitymoveprocessor-to-portals branch August 26, 2023 22:34
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