Skip to content
This repository has been archived by the owner on Sep 8, 2023. It is now read-only.

Ensure nether portals work as expected #37

Open
Jaxkr opened this issue Dec 1, 2021 · 0 comments
Open

Ensure nether portals work as expected #37

Jaxkr opened this issue Dec 1, 2021 · 0 comments
Assignees

Comments

@Jaxkr
Copy link
Member

Jaxkr commented Dec 1, 2021

PortalCreateEventListener is a messy abomination I wrote for the old version of WQL that used parameter arrays to represent Records.

The desired logic is simple, when a portal is created, sync all of the related blocks (obsidian and nether portals) to the other servers. This event is called for the automatically generated exit portal. Exit portal location is random but if a portal is already present it connects to it.

For consistent nether portal mechanics, portals from other servers should be synced regardless of whether they're subscribed to the area. If the PortalCreateEvent sends RecordCreate and GlobalMessage messages for the portal blocks with the "MinecraftBlockUpdate" parameter, it should work nicely.

You'll want to remove the nether portal cancelling code from PlayerTeleportEventListener.

@Jaxkr Jaxkr assigned Jaxkr and unassigned Jaxkr Dec 1, 2021
@Jaxkr Jaxkr self-assigned this Dec 9, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant