Two players are sitting in the same room. Both phones show a Wi-Fi connection. Minecraft opens without a problem, yet the host's world is missing from the other player's screen. This is a familiar multiplayer headache, and it can happen before either player has done anything wrong inside the game.

The missing world is usually a clue about how the devices, editions or network are connected. Minecraft Java Edition and Bedrock Edition do not use exactly the same local multiplayer steps. A guest Wi-Fi network can also make devices behave as though they are strangers, even when the router name looks identical.

For families and friends in Malaysia who want to play at home or on a shared connection, the useful approach is to diagnose the connection in order, rather than immediately buying a server or reinstalling Minecraft.

Highlights

Quick answer: If a Minecraft world is not showing on the same Wi-Fi, first verify that both players use the same edition and compatible current versions. Then check the host's multiplayer settings, connect both devices to the same local network and test whether the world appears. Java and Bedrock have different menus, so follow the correct steps for your edition.

The first question: are you both playing the same Minecraft?

The name Minecraft covers two major editions. Java Edition is available on desktop computers using Windows, macOS and Linux. Bedrock Edition runs on supported mobile devices, consoles and Windows. The games share much of the same world-building experience, but their ordinary multiplayer systems are not interchangeable.

A phone running Bedrock cannot simply discover a standard Java Edition LAN session on a laptop. Both devices might be connected to the same router, and both might be running what appears to be Minecraft, but the edition mismatch remains. Some independently managed servers use additional software to bridge players across editions. That is a separate server configuration, not an ordinary built-in LAN feature.

Before checking anything else, look at the edition shown in each player's app or launcher. On a Windows computer that has access to both editions, launching the wrong one is an easy mistake. For a group with Android phones and an iPhone, Bedrock is generally the relevant edition, provided versions and device compatibility align.

Java Edition: how to host a world over LAN

Minecraft's official help instructions for Java Edition are straightforward. On the host computer, launch Java Edition, select Singleplayer and open an existing world or create a new one. Press Escape to bring up the game menu, choose Open to LAN, adjust the offered settings and select Start LAN World. The game displays a message that a local session has opened, including its port number.

On the second computer, start Java Edition and open Multiplayer. The host's LAN game should normally appear in the list. If it does not, first leave the host world running. An open LAN session closes when the host closes that world, so the game cannot stay discoverable after the host returns to the title screen.

Java Edition's LAN feature is meant for players on the same local network. It is not a substitute for an internet-accessible server when friends are in different houses. For remote play, the group needs another hosting method such as a Realm or server, subject to the edition and subscription terms.

Bedrock Edition: enable the world, not just the Wi-Fi

Bedrock uses a different set of screens. The host should open Minecraft, select Play and find the world they intend to share. Use the edit or pencil control for that world, open Multiplayer and enable both Multiplayer Game and Visible to LAN Players when those settings are available. Then start the world.

The guest joins the same network and opens Play. Minecraft's official help says a local game can appear under Worlds with a LAN label. Where this interface changes with updates, look for the available local-world discovery control rather than assuming a specific old screenshot is still current.

One important detail often gets overlooked: Bedrock can recognise a signed-in Microsoft-account friend and offer to join that person's online world instead. In that case, the world may appear through the Friends experience rather than as the kind of LAN listing a player expected. The ability to join is more important than which tab displays it.

Check Java Edition Bedrock Edition
Typical host action Singleplayer world → Open to LAN World settings → Multiplayer Game and Visible to LAN Players
Guest entry point Multiplayer game list Local world listing or online Friends route
Edition requirement Other Java players Compatible Bedrock players
Host must keep world open Yes Yes for a directly hosted world
Common confusion Host forgot Open to LAN Multiplayer visibility or account route is different

Same Wi-Fi does not always mean the same local network

Imagine a café router offering a regular Wi-Fi network and a separate guest network. The two networks may share an internet connection but deliberately prevent devices from seeing one another. Even at home, some routers enable a feature called client isolation or AP isolation that restricts local device-to-device traffic. That is useful for security in public spaces but inconvenient for local games.

If the players use different networks, move them onto one trusted home network if permitted. A network called "Home-Guest" is not necessarily the same as "Home". On more complex mesh or campus systems, devices may also sit behind separate network segments despite sharing a familiar Wi-Fi name. A player cannot reliably solve that by toggling the game's graphics settings.

Avoid asking a café or school administrator to disable network isolation for a game. On shared infrastructure, that protection may be intentional. Use an approved personal network or choose a supported online multiplayer method instead.

Check the game versions before changing router settings

Version mismatch is another frequent source of confusion. Minecraft's official multiplayer requirements recommend that players use compatible, up-to-date releases. Bedrock Preview or Beta builds are not the same thing as a standard stable release. Java snapshots can also behave differently from normal releases, and a game world created for experimental features may not be suitable for an ordinary group session.

Open the title screen on both devices and compare the displayed build. If one person updated while the other still has an older release, use the platform's normal update mechanism. Do not download an unknown APK because somebody claims it is the only way to join a newer multiplayer world.

When a long-running world contains valuable builds, make a backup before experimenting with previews or changing versions. Multiplayer problems can be frustrating, but they should not become a reason to expose the only copy of a family's world to unnecessary risk.

Microsoft accounts, invitations and family settings

Bedrock's online multiplayer relies on account permissions in ways that pure network troubleshooting cannot fix. If the host is trying to invite friends online, they may need to sign into a Microsoft account, add the relevant friends and allow multiplayer in the world's settings. A child account can have restrictions that prevent joining multiplayer or interacting with strangers. These controls are managed by a parent or guardian; players should not try to bypass them.

On consoles, online play can also depend on the platform's subscription requirements. Local play and internet play are not necessarily treated identically, so check the official platform guidance for the exact arrangement. A phone-to-phone Bedrock session should not be diagnosed by assuming it needs the same paid console service.

For a Malaysian household where one child plays on a phone and another on a console, separating LAN, online friends and subscription requirements makes the setup much easier to understand. "Minecraft multiplayer" is not one universal switch.

A ten-minute diagnosis in the right order

Minute one: identify the edition on each device. If the group mixes Java and Bedrock, stop treating it as a simple LAN-discovery failure. Decide on a compatible edition or a properly configured bridging server.

Minutes two and three: compare version numbers. Open the host's world and make sure the appropriate Java or Bedrock multiplayer setting is active. Leave the world open while the second player searches.

Minutes four and five: reconnect both devices to the same trusted local network. If one uses a mobile hotspot while the other uses a home router, the local connection may not be what you assume. Temporarily disconnect from guest Wi-Fi where possible and use the intended home network.

Minutes six and seven: check where the world appears. Java guests use the Multiplayer screen. Bedrock guests may find the session under Worlds as LAN, or through the Friends route if their accounts recognise each other online.

Minutes eight and nine: restart the host's world and both clients once, then repeat the test. Avoid changing several unrelated settings at the same time. A controlled test tells you whether the last change made a difference.

Minute ten: write down the exact error message. "Unable to connect to world" is not the same as "No LAN game found." With that information you can follow Minecraft's official troubleshooting guidance for the correct failure type.

What about Windows Firewall or security software?

On a Windows PC, local multiplayer can be affected by firewall rules or a network that Windows has classified as public. That does not mean you should disable every security control. Check whether Minecraft or the Java runtime is permitted to communicate on the intended trusted private network. If a managed school or office computer blocks local games, follow the device administrator's policy.

Troubleshooting should be narrow. Temporarily turning off antivirus software or exposing arbitrary ports to the internet is a poor first response to a missing LAN listing. Likewise, changing router port forwarding usually concerns connections arriving from outside the home network; it is not the standard solution for two devices on a properly functioning LAN.

If you are unfamiliar with network settings, focus on the official game controls, versions and router-network choice before considering technical changes. A household should not need to sacrifice basic network security to make a casual game work.

Why a world appears for one friend but not another

This often points to a difference in account permissions, game versions or local routing rather than the world itself. One player might be signed in, added as a friend and able to join an online Bedrock session. Another might be searching for a LAN world from a different network segment or using a child account without the same permissions.

Try one guest at a time and record what happens. If Player A can join while Player B cannot, test Player B's edition, version and permissions before changing the host's entire setup. If nobody can join, return to the host's world settings and network.

The same reasoning helps with lag. A world that appears but runs badly has passed at least part of the discovery test. Now the problem may involve device performance, a poor Wi-Fi signal or the host being overloaded. Treating all problems as "LAN not working" hides useful clues.

Offline LAN, online worlds and Realms are three different options

A local session is designed for devices sharing a network. A directly hosted online Bedrock world can let friends join through their accounts while the host is playing. A Realm is a separately hosted service that can remain available without the owner's device running the world all the time. The right choice depends on whether friends are in the same house, whether they want to play at different times and which edition they own.

For a weekend with siblings on one Wi-Fi network, LAN may be enough. For friends living in Kuala Lumpur and Johor Bahru who want to meet inside a shared world, ordinary LAN will not bridge those households. Choose a supported online option instead. Those examples describe network geography, not a claim about popularity in either city.

A paid solution is not automatically better. Test the simple arrangement first, then consider hosting services only when the players genuinely need always-on access or remote connectivity.

Four real-world connection cases and what each one tells you

Case one: two Android phones on home Wi-Fi. Both are running Bedrock, but one player's world never appears. Begin by checking the host world's Multiplayer Game and Visible to LAN Players settings. Compare the version numbers and confirm both devices are on the same normal home network. If one phone is on a guest SSID, move it to the trusted network with the owner's permission. If the players are signed-in friends, check the online Friends route as well.

Case two: a laptop and a phone on the same router. The laptop owner says they have Minecraft Java Edition, while the phone runs Bedrock. No amount of refreshing the multiplayer list will make an ordinary Java LAN world appear as a Bedrock LAN session. The players need compatible editions or a deliberately configured cross-edition server. This is an edition problem, not evidence that the household's Wi-Fi is defective.

Case three: two Java PCs where only one can see the host. Start by confirming that the host actually selected Open to LAN in the world currently running. Compare both guests' versions. If one PC sees the game and the other does not, the host is probably broadcasting a valid session somewhere on the network. Focus on the second computer's local network, firewall and edition rather than resetting the router for everybody.

Case four: friends on different home connections. A player in Penang cannot normally discover a friend's ordinary LAN session in Kuala Lumpur simply by entering the same Wi-Fi name at home. A local area network is not a global friend list. Choose a supported internet multiplayer method, such as an online hosted world, Realm or server appropriate to the edition. The distance is not the problem; the fact that the devices are on separate local networks is.

These cases illustrate why the exact setup matters. "Minecraft will not connect" is not enough information to determine whether somebody needs to change a game setting, select another edition or use a different type of multiplayer service.

A home-network checklist that does not weaken security

When troubleshooting a local game, avoid turning the router into an experiment with unknown side effects. Record the existing settings before changing anything. In most homes, the simple checks are whether both devices have joined the intended SSID, whether either is using a mobile hotspot instead of the router, and whether a guest-network option is isolating users from other devices.

If your router offers separate 2.4 GHz and 5 GHz networks, the frequency alone does not establish that the devices are isolated. Some routers bridge them into one local network; others may separate particular segments. The safe approach is to verify connectivity and follow the router's own documentation, not to assume that a different-looking Wi-Fi name always means LAN play is impossible.

A phone's automatic switching between Wi-Fi and mobile data can also confuse testing. A device may show a Wi-Fi icon while some traffic is handled differently by its operating system or network service. For one controlled attempt, keep both devices on a known, stable network and avoid changing between connections mid-session.

If a school, hotel or public café operates the network, accept that local discovery may be intentionally blocked. Do not attempt to bypass access controls. Use a connection you are authorised to manage or a supported online game service. Multiplayer convenience is not a reason to expose other people's devices on shared infrastructure.

When the connection works but the game runs badly

A guest successfully entering the world is a useful milestone. It means discovery and joining have worked, even if the experience then becomes choppy. At that point, the troubleshooting question changes. Is the host's device overloaded by rendering a complex world? Are several people sharing a weak Wi-Fi signal? Does the slowdown occur only when players move far apart and load more terrain?

Test with a simple new world as a control. If the new world runs normally while the large survival world struggles, the issue may be the load created by the world or the host rather than a basic inability to connect. If both sessions are unstable, examine network quality and device performance. A fast internet speed test is not a complete measure of local Wi-Fi stability, but repeated disconnections under all conditions are worth noting.

Reduce unnecessary device load, avoid running background downloads and keep the host in a stable position with good reception. If problems persist, follow the official Minecraft troubleshooting guidance appropriate to the error. This separation between "not discovered," "cannot join" and "joined but lagging" will save more time than using one generic fix for all three.

Frequently asked questions

Can Minecraft Java and Bedrock play together on the same Wi-Fi?

Not through ordinary built-in LAN discovery. Java connects to Java sessions and Bedrock connects to compatible Bedrock sessions. Some specially configured servers can bridge editions, but that is different from a standard home LAN game.

Why can my friend see my world online but not under LAN?

Bedrock may show an online friend's world through its account-based joining interface instead of a local listing. Check the Friends experience as well as the local-world controls.

Can I play Minecraft LAN without internet?

A properly configured local network can support LAN play, but account sign-in or platform-specific services may need connectivity during setup. The exact behaviour depends on the edition and device.

Does Minecraft LAN need a paid server?

No. A supported Java or Bedrock local session can be hosted directly from a player's device. Servers and Realms provide different features for remote or persistent play.

Should I open router ports if the LAN world is missing?

Not as a first step. Check editions, versions, host settings and local network isolation. Port forwarding is usually relevant to external connections, not normal devices communicating on the same trusted LAN.

Conclusion

When a Minecraft LAN game disappears, begin with what the devices actually share: an edition, a compatible version, an open host world and a working local network. The icon showing Wi-Fi is only the start. Follow the correct Java or Bedrock instructions, and most of the mystery becomes a manageable checklist rather than a reason to start again.

Sources and verification notes