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

Skin Display does not automatically update to correct one when switching accounts in Launcher

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • None
    • 2.0.934 (Windows)
    • None
    • None
    • Unconfirmed

      Bug explanation:

      If you got several accounts and switch between them in the Launcher, look into the "Skins" tab of the Launcher, it does not update correctly, only when I restart the Launcher it immediately displays the correct skin for that account.

      Example:
      On account 1 is a Batman-Skin (correct)

      On account 2 should be my usual "blue demon" skin, but it shows the skin of account 1, the Batman skin

      Only if I restart the Launcher, I see my correct "blue demon" skin displayed on the second account.

      If any possible, it should grab the correct skin info, at least I get a bit confused as I can never know which account currently got which skin, as I need to juggle often with various skins for demonstration purposes

      On a side note: I just crashed ingame, and now that I restarted the Launcher, it doesn't show me any skin at all, I restarted the Launcher several times. Might be on my side only though, maybe some driver failing or something, I'll restart the computer (which fixes usually the majority of display problems )

      As always, I searched on Mojira (but am often really bad at this), sorry if I overlooked this bug being already posted.

        1. 01_correct-skin_first-account.png
          115 kB
          Meri Diana
        2. 02_wrong-skin_second-account.png
          115 kB
          Meri Diana
        3. 03_correct-skin_second-account_after-restart.png
          115 kB
          Meri Diana
        4. 04_no-skin_after-crash.png
          102 kB
          Meri Diana

            Unassigned Unassigned
            LapisDemon Meri Diana
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: