Java Edition
Java players should use the Java address shown in the server's Network tab. SPUDZWARE's Java route is designed so players can use the clean server hostname rather than needing to know which internal game-node port happens to run the process.
If the server says it is starting but the Network tab is not ready yet, wait for the game process and route health checks to finish. A running Java process and a joinable Minecraft server are not always the same moment; Minecraft still has to open the listener and finish world startup.
QuestCraft
QuestCraft is a Java Edition client for Meta Quest, so treat it like Java rather than Bedrock. Use the Java connection information shown by SPUDZWARE. If your Quest can reach normal Java servers but not this one, compare the exact hostname and any port instructions shown in the Network tab before changing the server itself.
VR does not require a different Minecraft world. The server sees a Java player. Client-side VR behavior depends on the QuestCraft/client setup and any compatible mods you choose to run.
Bedrock crossplay with Geyser and Floodgate
Bedrock clients use a different network transport from Java. Geyser translates between Bedrock and Java, and Floodgate can provide the account/authentication integration commonly used for Bedrock players on a Java server. When crossplay is enabled, use the Bedrock hostname and exact UDP port shown by SPUDZWARE.
Do not assume port 25565 or the normal Java route will work for Bedrock. UDP must reach the Geyser listener. HTTP-oriented proxy/tunnel products do not automatically proxy arbitrary Bedrock UDP traffic, which is why SPUDZWARE exposes the Bedrock connection details separately.
If one edition can join and another cannot
| Situation | Check first |
|---|---|
| Java works, Bedrock fails | Geyser/Floodgate status, Bedrock UDP port, and the exact Bedrock address shown in Network |
| Bedrock works for some users | Client version support and whether the failing player used the exact current port |
| QuestCraft fails, desktop Java works | Quest network, Java hostname/port instructions, and client Minecraft version |
| Nobody can join | Server startup/log state before troubleshooting crossplay |
Version compatibility still matters
Geyser can bridge editions, but it does not make every Minecraft version magically compatible. The Java server version, Geyser build, and Bedrock protocol support still need to line up. After a major Minecraft release, crossplay components may need an update before the newest Bedrock client can connect reliably.
The same principle applies to mods. A Java server can be crossplay-enabled and still use server-side plugins or compatible mods, but content that requires a Java client mod may not make sense for Bedrock players unless the pack has been designed around that limitation.
First prove the Minecraft server itself is healthy with Java. Then check Geyser/Floodgate. Then check the Bedrock UDP path. Changing all three layers at once makes it much harder to see where the failure actually is.
Cracked/offline mode is separate from crossplay
Crossplay and offline/cracked mode are different settings. Turning on Geyser does not require you to disable normal Java account verification. Offline mode changes Java identity verification and can allow username impersonation if it is used carelessly. Only enable it when you understand the security trade-off and have the right protections for the kind of community you run.