Uploaded image for project: 'Minecraft: Java Edition'
  1. Minecraft: Java Edition
  2. MC-138451

All my singleplayers games are "LAN" automatically

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Invalid
    • None
    • Minecraft 18w43c
    • None
    • Unconfirmed

      On a Forge 1.7.10 game, I have got 30 mods + a shader. They all work perfectly. I thought I could play some LAN with my sister, she's got the exact same amount of mods and the same shader, all at the exact same version. When she tried to open a LAN, I could not find her game, so I tried opening it instead, and she still couldn't find it.

      But that is when trouble began. I closed the LAN game, and we tried again with her own game : I couldn't find her, but I found my own game, which is impossible, since I had closed it. How odd. That doesn't stop here though : now, all the games I make on that version are considered to be always opened in LAN. It got confirmed when I started to get disconnected from those game with a message saying "a fatal error has occured, this connexion is terminated". I assume this message only appear in mutliplayer or LAN when the connexion crashes, but I wasn't in LAN nor multiplayer, so it was impossible. Closing the message leads me to the online server lists, as if I was in an online server, even though I was clearly in singleplayer. Later on, I opened that game again and closed it immediatly. For half a second, a message saying "shutting down internal servers" appear, as if it was closing a LAN game. But then again, it isn't opened in LAN, but it seems like the game considers it that way. 

      I tried uninstalling and reinstalling Minecraft entirely, but it didn't change a thing. Is there a way to fix this ? I don't think my mods or the shader have a link with that glitch because all this was working very well until I tried to open my game in LAN.

            Unassigned Unassigned
            Niniisan Mélanie Vincent
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: