-
Notifications
You must be signed in to change notification settings - Fork 12
FAQ
To be clear, this question and answer only applies to teleportation between servers. Teleportation between gates on the same server (even different worlds) requires no client patch or server trickery.
The short answer is "no". The long answer is more complicated. See ClientPatch.
2. But LegendaryCraft and LevelUpMinecraft (and <insert name here>) teleport without a client patch. How do they do it?
Either you aren't teleporting between servers, or they are using a server proxy, possibly a custom one. See question 1.
<<code text>> 10:10:08 [WARNING] [Transporter] connection with 127.0.0.1:25566 was unexpectedly closed 10:10:08 [INFO] Disconnecting /127.0.0.1:55549: Protocol error <</code>>
You may see these messages each on a different server, or together on the same server.
The problem is you've incorrectly specified the Minecraft server address instead of the plugin address when you added the server using the "trp server add" command. To add a server, you must provide the plugin address. The plugin address is typically the same IP of the MC server, but a different port. By default the plugin listens on port 25555 (unless you changed it with the "trp network set listenAddress ..." command). If you're using the default port, you don't need to specify it; the plugin will do the right thing.
4. When I teleport from one server to another and try to move out of the gate, it teleports me back to the starting server.
Increase the value of the global option "gateLockExpiration". It defaults to 2000 milliseconds, but how much you increase it depends on a lot of things. The idea is to set it at a value that's at least as long as it takes your client to download the terrain from the server.
Increasing the option value too much can cause problems if you have gates close together and run out of one and into the other since the expiration may be longer than the time it takes to run between the gates.