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

Prefix issue with names

    XMLWordPrintable

Details

    • Icon: Bug Bug
    • Resolution: Duplicate
    • None
    • Minecraft 1.12
    • None
    • Unconfirmed

    Description

      Hey there, I've seen a bug with prefixing names using scoreboard teams. DISCLAIMER: This uses very slight modding, but the issue doesn't relate to modding


      The bug

      Quick background info

      You can use a program like NBTExplorer to change a team's prefix. Normally, this is just for scoreboard teams option <team> color <color> to put, say, ┬ža when setting color to green so that players' names on that team are green.


      However, when changing the prefix using a program like NBTExplorer so that it is over 16 characters, it is over the limit and you can not join a server/Realm. The bug here is that if you join a singleplayer world, there is no limit compared to multiplayer worlds and it does not kick you, which is a big pain for testing.


      Other info

      What I expected

      When it went over the limit in a singleplayer world, it would kick me/throw an error in the launcher log/etc.

      What actually happened

      I could use it just fine over the limit in a singleplayer world, but multiplayer worlds/servers will give me an error. This is a big pain for testing.

      How it could be fixed

      Simply add the limit to singleplayer or expand it to, say, 4096*.
      * I was making prefixes for someone's server world and needed to test it in singleplayer when it worked fine. I gave it to him and he installed it on his server, only to have an error given. This was a big pain for both me and most likely him.

      Attachments

        Activity

          People

            Unassigned Unassigned
            TheMuffinPony TheMuffinPony
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: