You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 8, 2023. It is now read-only.
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: