Play · Connection Guide
Join in under a minute.
One address for both Java and Bedrock. Enter the hostname and matching port for your edition, then hop straight into the realm.
Server Address


play.wureta.net
- Java · port
- 25565
- Bedrock · port
- 19132
Java port 25565 is filled in automatically by default in the Java client.
Protocol Versions
Backend 26.2, proxy 26.3.
The backend and proxy do not always run the exact same build number. Whether you can connect depends on the protocol translation window, not just the version badge.
- Backend
- 26.2
- SkyBlock server version running the world.
- Proxy
- 26.3
- Protocol version accepted at the network gateway.
ViaVersion translates packets between your client and the backend. A 26.3 client can play on the 26.2 backend as long as its protocol sits within the translation window.
Java Edition

Java: play.wureta.net, port 25565.
Java uses the default port 25565. Log in with your Java Edition account — no extra web registration is required.
Launch Minecraft: Java Edition
Use client version 26.3. The backend runs on 26.2, and ViaVersion bridges the protocol between both versions seamlessly.
ClientMinecraft Java 26.3
Add the server
Open Multiplayer → Add Server. Enter any server name you like, then paste the address and Java port below.
Addressplay.wureta.net
Java Port25565
Save, select, and Join
If a connection attempt fails, do not assume the network is offline right away. Check network status first.
Bedrock Edition

Bedrock: play.wureta.net, port 19132.
Bedrock connects through NetherNet to the same gateway proxy. The website reports one combined Java + Bedrock online player count from the proxy.
Launch Minecraft: Bedrock Edition
Bedrock connects through NetherNet to the dedicated proxy — not a LAN world or Realm. There is no separate Bedrock hostname.
ClientLatest Minecraft Bedrock
Add the server
Go to Servers → Add Server. Enter port 19132 in the port field, along with the main network address.
Addressplay.wureta.net
Bedrock Port19132
Join with your Bedrock gamertag
Bedrock names appear with a leading dot on the server, such as .Name. That is standard Floodgate prefixing, not a second account.
Example name.Name
Troubleshooting
If you cannot connect
The four most common causes. None of these steps alter server state; live service health is always shown on the status page.
“Incompatible version” appears on Java
The backend runs on 26.2 while the proxy accepts 26.3 clients. ViaVersion translates protocol packets, but clients outside the translation window are rejected. Switch to client 26.3 and reconnect.
My Bedrock name changed to .Name
Floodgate prefixes a dot to Bedrock usernames so they never collide with Java accounts. Your underlying name remains Name. You can look up your profile with or without the leading dot.
Bedrock cannot find the server (NetherNet)
Add the server manually using address play.wureta.net and port 19132. NetherNet does not use Xbox friend lists or LAN discovery. If Add Server is missing, update your Bedrock client.
Java connection timed out or refused
Inspect the status page. An “unknown” status means the probe did not answer yet, not proof that the server is offline. If the network is running and you still cannot join, open a support ticket with the timestamp, edition (Java/Bedrock), client version, and error message.












