“Online” doesn’t automatically mean “joinable world.” In Java 26.3, the friends list is not a replacement for LAN, Realms, or a server address. With 26.2 Pre-Release 1 on May 26, 2026, Mojang took out the direct friend-world joining it had previously been testing. In Bedrock, you can generally join a friend’s shared world directly, as long as edition, version, account permissions, and connection all line up. Java and Bedrock don’t connect to each other without additional technology. Mojang’s change, Bedrock friend worlds.
The fastest next step: ask each other “Java or Bedrock, which version, and where is the world running?” Only then is it worth hunting for a network setting. A missing Java join button doesn’t turn into a supported feature because you open a port on your router.
As of October 29, 2026; sources rechecked November 1, 2026. For Minecraft Java and Bedrock, with or without your own server. You don’t need a customer account with a hosting provider to use this guide.
Share These Five Details First
Send each other a short message before anyone reinstalls anything:
- Edition and device: for example, “Java on macOS” or “Bedrock on Nintendo Switch.” “We both play on PC” isn’t enough: both editions are available on Windows.
- Exact game version: the number shown in the game or in the installation you launched. For Java, also the loader and modpack version, if you use them.
- Where the world lives: a friend’s singleplayer world, a LAN session, a Realm, your own server, or someone else’s public server.
- Connection route: the same home network or different internet connections? Wi-Fi and an Ethernet cable can belong to the same home network; a guest Wi-Fi network doesn’t have to.
- What you observe: is the world missing, is the button missing, or does a specific error message appear after you click? Write down the exact wording and the time.
A useful example, not a test report: “Both on Java 26.3 without mods, two computers on the same home router. The world is open to LAN. With Direct Connection, a timeout appears after a few seconds.” That makes it clear which section will help. “Minecraft doesn’t work,” on the other hand, leaves the edition, the way you play, and the point of failure open.
Which Way to Play Together Fits Your Group?
Go through the questions in order. As soon as one route fits, jump to the matching section.
- Does one of you play Java and the other Bedrock? Then a normal invitation between the editions won’t work. Settle on the same edition or a suitable Java server with Geyser. For consoles, check the access restrictions first; for Java modpacks, check content compatibility first.
- Do you both play Java on the same local network? Open the world to LAN. If it doesn’t show up automatically, use the host’s local address and the LAN port actually shown in the game.
- Do you both play Java in different places? Use a Java Realm or a reachable Java server. Running a server yourself is possible. A private network connection between your devices is another option for technically experienced groups; it doesn’t replace edition compatibility.
- Do you both play Bedrock? Have the owner open the world you want and allow multiplayer. Check the invitation or the joinable friend’s world. On the same network, there’s also LAN; for a world that doesn’t depend on the host, use a Bedrock Realm or a suitable server.
- Do you already have a Realm or a server address? Stop searching the friends list. Check the Realm invitation or the server entry, the matching version, and access rights.
Important: A Realm is also a server service, but it has its own way to join. “My friend has a server” may simply mean they opened their singleplayer world. Ask before you report a problem to the wrong operator.
Platform Matrix: Who Can Join Whom?
The matrix below is checked against primary sources, not presented as a full device test. It describes supported routes and known limits. A checkmark in a list wouldn’t prove that your specific combination of accounts, router, save, and version works. The test checklist later in this guide helps you check exactly that combination.
| Your combination | Matching route | Limit | Concrete next step |
|---|---|---|---|
| Java on Windows, macOS, or Linux; same network | Java LAN | Host must keep the world open; matching game version | Open the world to LAN, note the current port |
| Java on these computers; different locations | Java Realm or Java server | Friend status alone doesn’t open a world | Accept the Realm invitation or enter the server address |
| Bedrock on Windows, Android, or iOS | Friend’s world, Bedrock Realm, or Bedrock server | Account, version, and multiplayer permissions must match | Host opens the world; guest checks the invitation |
| Bedrock on Xbox, PlayStation, or Switch with other Bedrock players | Friend’s world or Bedrock Realm; featured servers | Platform online subscription; no free server entry like on PC | Use a friend’s world or Realm first |
| Bedrock devices on the same network | Bedrock LAN on supported devices | Local visibility and device/platform conditions | Turn on LAN visibility, look for the LAN entry |
| Java and Bedrock mixed | Suitable Java server with Geyser | No native crossplay; versions and content limit it | Ask the operator about the Bedrock endpoint and compatibility |
| Console to your own Bedrock/Geyser server | Not available as a normal free server entry | Third-party methods are extra solutions that keep changing | Check console access separately before choosing a server |
| Java modpack to the same Java modpack | Matching LAN/dedicated modpack server | Pack version and required client mods must match | Compare the exact pack export, not just the Minecraft version |
| Bedrock to a Java modpack with required client mods | No generally compatible route | Geyser doesn’t install Java mods on Bedrock | Choose a shared vanilla-compatible world or Java clients |
| Java to a Bedrock Realm, or Bedrock to a Java Realm | No native join | Realms stay separated by edition | Choose a Realm for the edition you share |
Sources: Mojang’s edition comparison, multiplayer requirements, Realms comparison, Bedrock server access, Geyser FAQ.
What We Tested Ourselves
On October 29, 2026, we connected Minecraft Java 26.3 without mods on macOS to our own dedicated vanilla server on the same computer. Account authentication and the whitelist stayed enabled. The real game client joined twice and, in both sessions, received a server message sent specifically for the test. The connection was closed between the attempts, and rejoining afterward worked. Client and test server were then shut down. Compact test log.
This test confirms the local Java server route with one authorized game account. It doesn’t test two different friends at the same time, LAN between two devices, access over the internet, Bedrock, Realms, or consoles. Those rows of the matrix are based on the linked primary sources. Check your actual combination with the test checklist further down; a successful local server join says nothing about your router or any other device.
Java 26.3: Your Friend Is Online
The mix-up has an understandable origin. 26.2 Snapshot 7 introduced the friends list together with an experimental direct connection. If you come across news or videos from that time, you may expect a feature that didn’t make it into the release in the same form.
Mojang removed the direct peer-to-peer connection in 26.2 Pre-Release 1. The friends list stayed. The Java 26.2 release on June 16 documents friend statuses such as Online, World, LAN, Realm, and Server. This activity indicator tells you what someone is doing right now; it doesn’t grant general access to their world.
The question came up again after Java 26.3 on September 15: in the public ticket MC-312751, a family describes exactly this confusion. The reply from October 21, 2026 names LAN, Realms, and servers as ways that still work and gives no date for the feature’s return. The ticket was closed as “Invalid.” Here, that doesn’t mean the observation was made up; it means the ticket was classified as a support question rather than a bug report.
What this means: For a normal game night on Java 26.3, plan on LAN, a Realm, or a server. Don’t install an old snapshot into your existing world to get back a button you once saw. An old interface is neither a promise that the services behind it still work nor a safe way back for your save. Check the current release notes again for later versions; this section is explicitly dated.
Open and Find a Java LAN World
On the Computer That Has the World
Open Minecraft Java with the installation your group has agreed on. Load the world, open the pause menu, and choose Open to LAN; the exact label can vary by version and language. Set the game mode and command permissions deliberately, then click Start LAN World. Write down the port number from the in-game message. Official Java LAN guide.
Keep the game and the computer running. Closing the laptop lid, sleep mode, or leaving the world can end the session. For a quick cross-check, a new small test world helps: that way, you don’t change your shared main world while testing.
On the Guest’s Computer
In Java, open Multiplayer and wait a moment for the local world to appear. If it’s missing, use Direct Connection with the host’s local address and the current LAN port. Example: 192.168.1.42:52187. Both numbers are just examples; don’t copy them as they are.
You’ll find the local IP address on the host in the network details of the active connection. On Windows, ipconfig shows the IPv4 address of the Wi-Fi or Ethernet adapter. Ignore adapters that aren’t part of your connection. On macOS, you’ll find the information in System Settings, under the details of the active network connection. Your router’s overview page can also show which address the host currently has.
Don’t mix these up: localhost and 127.0.0.1 point to the device you type them on. On the guest’s computer, they won’t lead to your friend. Likewise, a friend on a different internet connection can’t simply reach an address from your private home network over the internet.
When the World Isn’t in the List
Automatic discovery and actual reachability are two separate checks. If Direct Connection works, your setup is already usable, even if the LAN entry is missing. Save the address and port for this session. If the port changes after you open the world to LAN again, you need the new value. Mojang’s server guide also covers the optional port choice in the LAN dialog.
If Direct Connection fails, check these in order:
- Are both devices really on the same home network, and not one on guest Wi-Fi, mobile data, or a separate network segment?
- Is the world still open, and did you copy the port from the current session?
- Does the host firewall allow access for the Java/Minecraft application you’re actually using, on a trusted private network?
- Is the router blocking communication between Wi-Fi devices, for example through guest or client isolation?
Change only one setting per attempt. On managed school, hotel, or company networks, the separation is often intentional; don’t try to get around it. Use another permitted way to play there. For ordinary play within the same home network, you don’t need internet port forwarding.
Success check: The guest enters the right world, and both of you see the same harmless change, such as a newly placed block at an agreed spot. Rollback: Close the test LAN session, remove any firewall rule you added for testing, and reset any changed router setting to its documented original value.
Bedrock: Checking the World Join
In Bedrock, joining a friend’s world directly is a standard option. Start with the world itself: the host must have loaded the world you want and allowed multiplayer. An account that’s only online in the main menu isn’t providing a running world yet. Then check the invitation or the entry for a joinable friend’s world. Mojang’s joining guide points to the Friends tab for this; menu layout and labels can differ between interfaces.
Next, go through four separate layers:
- Game: Both of you use Bedrock with a compatible version. A Preview/Beta installation isn’t automatically compatible with the regular release.
- Identity: The expected Microsoft account is active in the game. A console friend and the identity used in Minecraft can get mixed up.
- Access: Multiplayer is allowed on the account, the world lets you in, and on consoles the required online subscription is in place.
- Session: The host stays in the world, the invitation is current, and the network connection stays up.
If all of that checks out, run a small, reversible comparison: the host creates a new test world with no add-on content and invites exactly the same guest. If that works, look at the settings and add-on content of the original world next. If it fails too, deleting or resetting your actual world has no clear benefit.
After that, the previous guest can open a test world of their own. Only one direction works: this narrows the search to the host device, the sharing settings, or the network path; it doesn’t yet prove which one is the cause. Both directions fail: this points to a shared requirement or a service problem, but it isn’t a finished diagnosis either.
On the same home network, Bedrock also offers LAN. In the world settings, turn on Multiplayer Game and Visible to LAN Players. Mojang describes the LAN entry in the Worlds tab. If both players are friends and online, Bedrock may show the online join option instead; “same Wi-Fi” therefore doesn’t prove that your current session actually uses LAN. Bedrock LAN guide.
Success check: The invitation leads into the expected world, and both players can move and perform an allowed interaction. Rollback: Keep the test world or delete it deliberately, and revoke only its sharing settings. Don’t unlink the whole account, don’t delete saved worlds, and don’t reset your entire network configuration as long as a narrower test is possible.
Check Accounts and Consoles
If you see a message like “Multiplayer is disabled” that points to your account settings, the router isn’t the first place to look. The adult who manages the family group should check the multiplayer and, where relevant, cross-platform permissions of the affected account. A child shouldn’t change their date of birth or use someone else’s sign-in details to get around this. Mojang’s guide to family and multiplayer permissions.
Change only the permission needed for the game session you’ve agreed on. Note what was set before, save the change, and sign in again or restart the game if the new setting isn’t picked up yet. If the message persists, first check whether the account you just changed is really the one active in the game. That keeps you from changing permissions on the wrong family member.
Online multiplayer on consoles also requires the platform’s own subscription. That’s a different entitlement from a Realm subscription. So your group should keep two questions apart: “Does someone own the Realm?” and “Is my console account allowed to play online?” Minecraft Help lists the current requirements; check which plan actually includes online play instead of relying on an old plan name alone.
If accounts seem to be linked incorrectly, don’t unlink Microsoft and console accounts on a hunch. Read the platform’s account help first and clarify who owns which account and how to sign back in. A join problem doesn’t justify an unprepared change to your account links.
Realms: Invitation and Edition
A Java Realm is for Java players, and a Bedrock Realm is for Bedrock players. For Realms, “cross-platform” means playing together on the supported devices within the same edition, not automatically Java plus Bedrock. The Realm owner doesn’t need to be online during your session. Invited guests don’t need their own Realm subscription; they still need access to the game and, where applicable, a console online subscription. Official Realms comparison.
Check these one by one:
- Did the owner actually invite the right player profile or account?
- Did you accept the invitation and select the right Realm?
- Is the Realm open, and is there a free slot for another guest playing at the same time?
- Do the edition and released game version match the Realm?
- Can other members who were already invited join?
If all members are locked out at the same time, the owner should check the Realm’s state and the service status information. If only one person is affected, start with their account, version, and invitation. This narrows things down; it doesn’t prove a specific fault.
Don’t rush into: replacing the world, restoring a backup, or recreating the Realm. Connection problems and corrupted saves are different things. Before actually swapping the world, the owner needs a current backup and has to know which save is being restored. For the first test, a verified invitation is enough.
Your Own Server: Checking the Join
Your own server can run on a computer at home, on rented infrastructure, or with a game server provider. How you join depends on the edition and the server configuration, not on the provider’s brand name.
For Java, enter the hostname or IP address on the Multiplayer screen, plus :Port if needed. Example: play.example.org:25565. For Bedrock on supported computer and mobile versions, enter the address and port in the fields provided for them. https:// and a web page path don’t belong in a normal game server address. The example domain is not a test server.
The owner should give you four details: edition, exact version or pack version, player address, and player port. Not the web address of the admin panel, not RCON access, and not an admin password. With Geyser, the Bedrock endpoint can differ from the one Java players use.
For the Operator: Check from Near to Far
First check whether the game process has finished starting up. Then test, as far as it fits your setup, on the server machine, from a second device on the home network, and finally from a permitted device outside it. Success on the same machine doesn’t confirm that the server is reachable from the internet. A test from inside the home network using the public address can turn out differently from a real external test because of how the router behaves.
Compare the game port that’s actually configured with the firewall and, if used, the router’s port forward. Paper documents server-port=25565 as the default, and Microsoft documents server-port=19132 for Bedrock; a provider or your own configuration may assign different values. Don’t blindly change working assignments to a supposed default. Paper configuration, Bedrock configuration.
For current Geyser installations, the transport matters a lot: the project’s setup guide accounts for NetherNet and lists TCP as well as UDP on the Geyser port. Since October 30, 2026, it no longer recommends the combined NetherNet and RakNet transport that needed an extra UDP port. So don’t carry an old “UDP 19132 only” tip over to every Bedrock/Geyser setup without checking. Server type, version, and transport need to be settled before you change a port.
When Your Connection Doesn’t Allow Incoming Connections
A port forward on your own router doesn’t help on its own if there’s another router in front of it or address translation managed by your internet provider. With CGNAT, several connections share one public IPv4 address; DS-Lite can also explain why the usual incoming IPv4 connection isn’t available. Have your internet provider confirm what reachability is actually available before you set up more port forwards.
Possible routes are public reachability that is explicitly available, a private connection between your devices, a tunnel that supports the Minecraft protocol, or a server hosted elsewhere. They come with different requirements and trust boundaries. A VPN toggle in your browser is not an automatic fix for incoming Minecraft connections. If you use a private connection, limit access to the devices involved and the services you need.
Don’t Switch Off Protections as a Fix
Being turned away by the allowlist often means a protection is working. The operator adds the profile that’s actually being used through the intended admin route. They don’t make the whole world public to do it. Account authentication and the firewall stay on as well. online-mode=false, a router DMZ, or switching off the firewall entirely are not suitable default answers to “my friend can’t join.”
Success check: An authorized regular player joins through the intended external or local route, and that exact attempt can be traced in the relevant server log. Rollback: Back up the configuration before making changes, label each new rule or port forward individually, remove unneeded rules, and restore the previous state deliberately. Don’t regenerate a live world just to test a connection.
Java and Bedrock with Geyser
Geyser translates a Bedrock client’s connection for a suitable Java server. It’s not a setting you can turn on in any friend’s world. Floodgate adds a way for Bedrock players to sign in without an additional paid Java account; setting it up is part of running the server. According to the Geyser FAQ, both projects are free and open source.
Before setting it up, the operator should check the currently supported versions. When we checked on October 29, 2026, the project listed Bedrock 26.40–26.60 and Java 26.3. That’s a dated snapshot of the documentation, not a promise for every older Geyser file that’s already installed. So after a Bedrock update, the bridge may need an update too, even if Java players can still join without problems.
Java content that requires a special client is a different limit. A Bedrock player can’t just install a modpack’s Java JAR files. For a mixed group, a deliberately vanilla-compatible world is a better fit than a modpack whose extra content requires client mods. Test individual features (inventories, menus, interactions) instead of assuming full playability from a successful login.
On consoles, there’s the added issue that you can’t normally enter any server address you like. Geyser describes third-party methods for consoles but also warns about problems with this kind of access. That’s why this guide doesn’t promise a universal console trick and doesn’t recommend any unverified DNS address. If you deliberately test one of these methods, write down your original network settings first and restore them if problems come up. For an easy Bedrock evening, a friend’s world or a Bedrock Realm remain the obvious standard options.
How to Read Error Messages
| What you see | What it narrows down | Sensible next test |
|---|---|---|
| Java friend is online, but no world join is available | The feature you expect may not match the release | Choose LAN, a Realm, or a specific server address |
| LAN world is missing from the list | Automatic discovery or sharing is missing | Direct Connection with the current host and port |
| “Outdated client” / “Outdated server” | Game protocols don’t match | Write down client and server versions side by side |
| Timeout | The target doesn’t respond in time on this route | Check address, port, running host, and network path |
| “Connection refused” | The connection is rejected at the target/port | Check server startup and the port actually in use |
| No multiplayer because of account settings | Account permissions | Check the permissions of the signed-in account |
| Not on the allowlist | Access control reached | Operator checks exactly this profile |
| Mod or registry error after connecting | Required content may not match | Compare pack version, loader, and required mods |
| Bedrock: generic “Unable to connect to world” | No single cause proven yet | Test world, the other hosting direction, account permissions, and version |
| NetherNet errors | Multiplayer connection error, no clear single cause | Current Minecraft network help and transport configuration |
The table is a diagnostic aid, not an automatic verdict. A “timeout,” for example, doesn’t prove that your internet provider is to blame. Microsoft’s Bedrock server getting-started guide explains version mismatches; Mojang’s error code help classifies NetherNet as a connection problem.
Playing Together for Free
Java LAN doesn’t require a hosting subscription. You need suitable devices, access to the game, and the same local network. The host computer has to stay on. Bedrock friend worlds don’t require a server subscription either; on consoles, online costs may still apply. So “no server rental” doesn’t automatically mean “no extra cost at all.”
Self-hosting saves you the rent for a ready-made game server, but in return you take on computer uptime, electricity, the connection, backups, and maintenance. A private network connection can suit a small, trusted group. For third-party services, check the current free limits, the supported devices, and how they handle your data. This guide deliberately makes no performance promises that haven’t been measured.
Free hosting offers can be an alternative as long as startup times, possible queues, shutdown on inactivity, mod support, and the option to export your own world suit your group. Check these points with each provider. For a spontaneous hour, different limits are acceptable than for a building project that runs for months. Whatever the provider, keep your own backups.
Realms and paid hosting can make upkeep and availability easier. But they don’t fix the wrong edition or a missing account permission. Don’t buy anything until you’ve sorted out your combination of platforms and the content you need. Two Java players on the same home network don’t need a rented server.
Test Your Connection Step by Step
Use the same short test checklist for every route. After an update, it lets you tell whether you really tested the same combination. It’s a guide for your own test, not a multiplayer test we carried out.
- Note the setup: Date, edition, full client/server version, devices, network route, and, where relevant, loader, pack, and Geyser version. Don’t put passwords or public access details into a shared note.
- Check the join: The guest signs in with the intended account through the intended route. The world is the right one, not just a test world with the same name.
- Check interaction: Both of you can see each other and perform an allowed action. With visitor permissions, not being able to break blocks isn’t a connection error.
- Check rejoining: The guest leaves the session and comes back in. For LAN, use the current port after the world has been reopened.
- Check persistence: Only with a test world meant for this, save in a controlled way and reopen it; then find your small test change again. Don’t restart a shared server for this without asking.
- Record the limits: Devices, mods, and networks you didn’t test explicitly remain open. A success on PC doesn’t replace a console test.
A useful log might read: “Bedrock on Windows to a Bedrock friend world on Android, both version X, different internet connections: join and rejoin worked; console not tested.” That’s more honest, and more useful for the next round of troubleshooting, than “Crossplay works everywhere.”
Details That Help Support
Send the operator or official support a short summary with edition, device, version numbers, time including time zone, the route you chose, and the exact error message. Add whether other players can get in, whether a fresh test world works, and which single change you tried last.
A screenshot should show only the relevant error. Black out private account details, invite codes, and other players’ names. Share server logs only in the appropriate private support channel, and check them beforehand for tokens, IP addresses, and other unnecessary personal data. Nobody needs your Microsoft password to narrow down a join error.
If you suspect a general outage, check the service status pages Mojang links from its multiplayer troubleshooting help. Note the time. A green status later on doesn’t prove after the fact that everything was working when your error happened.
Short Glossary
Host: The device or service where your shared world runs. Client: The Minecraft game you use to join. LAN: Your local network. Port: The number of the service at an address; for the connection to work, both the target and the port have to be right. Realm: Mojang’s managed private server service. Allowlist: The list of approved players. Snapshot/Preview: A test version that may differ from the released game. Geyser: A translation layer for Bedrock clients on a suitable Java server. CGNAT: Address translation at your internet provider that can prevent a normal incoming IPv4 connection.
For your next game night: Decide on the edition and route first, then test exactly one connection with a small test world. Once joining, interaction, and rejoining work, write the combination down. That way, you’ll have a starting point after the next update instead of starting over at “but my friend is online.”
Frequently Asked Questions
Can I Just Click on My Friend in Java 26.3 and Join?
The friends list shows status, but it doesn’t offer the previously tested direct world join as a general way to play. Use LAN, a Java Realm, or a Java server. The removal is documented in Mojang’s 26.2 pre-release notes; MC-312751 picks up the question again in October.
Why Did It Work in a Video but Not for Me?
The video may show a test version, a different edition, or extra mods. First compare the edition, version number, and any add-ons used. A snapshot announcement isn’t a commitment about what a later release will include.
Can a Mac and a Windows PC Play Together?
Yes, if both use Java with a matching version, for example over LAN, a Java Realm, or a server. If the Windows player launches Bedrock, you need a different compatible route; the name of the operating system alone doesn’t settle the question.
Can PlayStation, Xbox, Switch, and Phones Play Together?
In general, yes, within Bedrock and through a suitable shared route, especially a friend’s world or a Bedrock Realm. Check the version, account permissions, and console online subscription. On consoles, freely entering any server address doesn’t work the same way as on computers and mobile devices.
Does Everyone Have to Pay for a Realm?
No. Invited guests don’t need their own Realm subscription. They still need the right game and, if applicable, their console’s online subscription. Java Realms and Bedrock Realms remain separate.
Do I Need to Open Ports on My Router for LAN?
Not for a normal join within the same home network. First check the local sharing, the current port, and the host firewall. Access from outside the home network is a different task and needs a deliberately set-up, reachable route.
Does Turning Off the Firewall or Reinstalling Minecraft Help?
Start with edition, version, address, sharing, and account. A narrowly scoped, matching firewall rule makes more sense than switching the firewall off completely. A reinstall is no substitute for a diagnosis and must not put your local worlds at risk.
Can Bedrock Play Any Java Modpack with Geyser?
No. Geyser translates connections; it doesn’t make required Java client mods run on Bedrock. Look into a suitable vanilla-compatible setup and the current version support.
Editorial review method
The MCRedstone editorial team checked versions, platform rules, and support pages against the official sources linked in this article, last on November 1, 2026. Our own test is limited to the Java 26.3 join test on macOS from October 29, 2026, described above; every other step is researched guidance for your own checks. We review the article again when Minecraft, Realms, or Geyser change the details it relies on.