Friend Sharing

Friend Sharing

Everything about playing Blockpal with other people in one place: hosting a world for friends, letting them join from Java or Bedrock, giving them control of your bot, and (coming soon) inviting a whole group for Minigames.

Cross-play direction (read this first)

Blockpal follows the same direction Geyser supports: Bedrock players join a Java host — not the other way around. A Bedrock device can't run the mod, so it can only join; a Java player is always the host. Everything below assumes a Java host with Bedrock and Java friends joining.

Host a world in one click (available now)

A Java player can stand up a Bedrock-ready server from inside the game — no manual setup.

• Open the pause menu (Esc) in a singleplayer world and click "Host with Blockpal" (bottom-left corner as of 3.16.1, so it never covers the vanilla buttons), or run /aihost.
• Accept the Minecraft EULA, then Start hosting. Blockpal downloads the Minecraft server, Fabric, and the latest Geyser + Floodgate from their official sites, configures everything, and launches a real server. Downloads are cached (3.16.1): only the first host pays the full download — after that the Minecraft jar is reused as long as its checksum matches and the "latest" components are re-checked at most once a day, so starting a host is much faster.
• It hosts your current world (3.15.0): the world you were playing is saved, copied into the server, and hosted — you rejoin via Direct Connect → localhost:25565. When you stop, the changes are saved back to your singleplayer world (with a timestamped backup) and the server's copy is deleted. Toggle it off to host a fresh world instead. As of 3.16.1 the world is copied before any downloading, so it's captured moments after the save closes. The copy is much faster now (3.20.0): world files are copied in parallel instead of one at a time, and the status line shows live progress (Copying "MyWorld" into the server… 62% (410/660 MB)) both when hosting starts and when changes are synced back — so a big world no longer looks stuck on "Copying…".
• When it's running it shows the Java (ip:25565) and Bedrock (ip:19132) connect addresses, for both your local network and the internet, with copy buttons.

Full walkthrough and caveats: Bedrock (Geyser).

On Lunar Client? Blockpal detects Lunar (3.16.1) and the Host screen will point out Lunar's own built-in world hosting — that's the easiest path for Java-only friends. Lunar has no API a mod can call, so Blockpal can't start it for you; use Host with Blockpal when you want Bedrock friends (phone/console/iPad) to join too.

⚠ Share addresses carefully. The internet address shown is your own computer's public IP — give it only to people you trust. And showing it doesn't make you reachable: friends outside your network still need a forwarded port (TCP 25565 for Java, UDP 19132 for Bedrock), or use the no-port-forward tunnel below. On the same Wi-Fi/LAN the local address just works.

No port-forwarding? Use the tunnel (3.14.0)

The Host screen has a "Start tunnel (no port-forward)" button that runs the playit.gg agent — the one relay that carries both Java (TCP) and Bedrock (UDP). It prints a free, one-time setup link (with a "Copy link" button); open it, map your Java and Bedrock ports on the playit dashboard, and friends join your playit address with no port-forwarding and without you sharing your real IP. Details: Bedrock (Geyser).

Let Bedrock friends join (available now)

If you already run a Fabric server, add Geyser-Fabric and Floodgate-Fabric to its mods/ folder and your friends on iPad, console, or phone can join and play with Ethan — no mod on their device. Blockpal treats Floodgate as optional, so the server still runs fine without it. Details and the works/doesn't-work list are on the Bedrock (Geyser) page.

Let friends command your bot (available now)

Sharing a world doesn't mean handing over your companion. By default only you (its owner) can give it orders. To let a specific friend command a specific bot, use trust:

/ai trust <player>     # let them give this bot orders
/ai untrust <player>   # take it back
/ai trust list         # who's trusted on this bot

Trusted friends can tell the bot to come/follow/stay/stop and give it tasks; renaming, dismissing, and editing the trust list stay owner-only. Full details: Trust & Per-Bot Management.

Invite a group / party (available now)

Gather a group with the built-in party system — the team that Minigames will run on. It's entirely command-driven and handled on the server, so Java and Bedrock players use it the same way.

/party invite <player>   # invite an online player (auto-creates your party)
/party accept            # accept an invite (expires after 2 minutes)
/party deny              # decline an invite
/party list              # show your party and its leader
/party leave             # leave your party
/party kick <player>     # leader: remove a member
/party disband           # leader: end the party

• One leader, up to 100 members.
• The leader invites, kicks, and disbands; if the leader leaves or disconnects, leadership passes to another member automatically.
• Parties live for the session (they aren't saved across a server restart).

The minigame modes (coming next) will start a round for your whole party, so everyone — and the bot — plays together.

Related pages

• Bedrock (Geyser) — hosting walkthrough + how Bedrock joins.
• Trust & Per-Bot Management — share control of a bot.
• Minigames — the game modes you'll play with your invited friends.