Uploaded image for project: 'Minecraft Launcher'
  1. Minecraft Launcher
  2. MCL-13541

Snapshot 20w14inifinite - saved worlds not listed

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Works As Intended
    • None
    • 2.1.13315
    • Java Edition Versions
    • None
    • Windows 10; Java 8 probably; running Beta versions of minecraft.
    • Unconfirmed

      Put the summary of the bug you're having here : A NEW launcher started today with 20w14inifinite and it does not find the previously saved games from last nights save (launcher 20w13b.) The AFFECTED VERSION/S do not list the beta launcher I have. 2.1.13508 non-released version. So I selected 2.1.13315 because it was the newest.
      When I select 20w14infinite no games appear on the selection list.
      When I select <Latest release 1.15.2> from the pull down menu, the 'normal' Mojang screen comfirms my account. I click Single player and see the games. They have the versions 20w13b, 20w13a, 1.15.2, and 1.12.2. The versions 20w13b and 20w13a are in red text indicating they are not valid?

      What I expected to happen was...: To see a list of previously saved games to select to one to play.

      What actually happened was...: No saved games displayed to select to play. The Mojang launcher screen looked "funny." It is unlike previous versions. But it is not likely the problem.

      Describe what happened here. No games in list.
      I did a little searching. Found saved games %appdata%/.minecraft/saves. They just do not appear on a game selection menu. I found all the versions of minecraft that I have played in %appdata$/.minecraft/versions.

      Steps to Reproduce:
      1. Click link on desktop to start minecraft launcher
      2. Watch new Mojang launcher startup and account confirmation
      3. Select saved game screen appears. No games listed.
      4. Stuck.

            Unassigned Unassigned
            RandallTwo David A Randall
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: