Bedrock cannot join a Java server directly

livedaw.store is a Minecraft: Java Edition 1.8.8 server running Paper with the DawGuard anti-cheat. Bedrock — the edition on phones, tablets and consoles — speaks a completely different protocol. Typing the Java address into Minecraft for Android or iOS fails with “Unable to connect to world” whatever port you use, and no client setting changes that.

There are two routes onto the server. Only one of them works today.

Option 1 — the Java 1.8.8 client on your phone

Launchers such as Amethyst run Minecraft: Java Edition on Android and iOS. It is the maintained successor to PojavLauncher, which has been archived and is no longer supported. Amethyst launches versions from rd-132211 up to current snapshots, so 1.8.8 is inside its range.

1. Install it. Android: the APK from Amethyst-Android. iOS: Amethyst-iOS, which is sideloaded — there is no App Store build.
2. Sign in with a Microsoft account that owns Java Edition. livedaw.store runs online-mode=true, so offline or “cracked” logins are refused. It is the same account you would use on a PC.
3. Create a 1.8.8 instance and let the launcher download the game files.
4. Multiplayer → Add Server → livedaw.store. If the address does not resolve on your device, use livedaw.store:25565.
5. Enable the on-screen controls and drop render distance until the frame rate holds steady. 1.8.8 is light, but a phone is still a phone.

Honest limits: touch controls are not competitive in 1.8 PvP — block-hitting, strafing and rod timing all assume a mouse — and DawGuard judges your movement exactly as it judges a desktop client. The client mods in the download center target 1.21.11 Fabric and do not apply to a 1.8.8 profile.

Option 2 — Bedrock through a Geyser bridge

Geyser (GeyserMC) translates Bedrock into Java so Bedrock clients can join a Java server. It is not installed on livedaw.store, so there is no Bedrock address to type today; this hub does not publish an address that does not answer.

On this server it is also not a drop-in plugin. Geyser’s Spigot/Paper build requires a Java server of 1.12.2 or newer, and livedaw.store is 1.8.8. Geyser additionally emulates a current Java client, so a 1.8.8 server only accepts it through ViaVersion, with ViaRewind handling the jump below 1.9. Geyser’s own supported versions page says the same: older servers need ViaVersion, and a proxy or standalone install.

What an administrator would have to do:

1. Install a Java 8-compatible ViaVersion build on the Paper 1.8.8 server and restart it, so a modern protocol can log in at all.
2. Run Geyser-Standalone on Java 17+ as a separate process, with its remote Java address set to 127.0.0.1:25565.
3. Settle authentication. The server is online-mode=true, so Bedrock players need a Java account unless Floodgate is added — and Floodgate changes how logins work, which DawGuard and the existing 1.8 permissions would have to tolerate.
4. Allow UDP 19132 inbound on Windows and forward it on the router, the way TCP 25565 already is.

Even when it runs, crossplay has real gaps: 1.8 combat has no attack cooldown and Bedrock does, so hit timing and knockback differ; inventories, redstone and some blocks translate imperfectly; clients cannot use the Java mod set; and a predictive anti-cheat tuned for vanilla 1.8 movement may flag translated players. Consoles (Xbox, PlayStation, Switch) cannot add custom servers at all without a separate companion device. Desktop Java stays the reference experience.

Which route applies to you

Connecting from a computer, the account requirement and the status API are on the documentation page; what gets you kicked is on the rules page.