Tron
- Luker2009
- luker2009
- America/New_York
- Yes
- No
MC-46535![[Mojang] Nathan Adams](../../../data/assets/gravatar/dinnerbone.png){kind=small}
MCL-4454
Can control minecarts in SPectator ModeCan control minecarts in Spectator Mode
I also am having this with io.netty.handler.codec.DecoderException:java.io.IOException:
The received string length is longer than maximum allowed (50 > 16) Was doing some teams + scoreboard stuff for setting a scoreboard for every player when they join.
I attempted to login to an account with multiple profiles and they all return the same UUID.
What I expected to happen:
The dropdown menu would allow me to pick an account and each would have a different UUIDWhat happened:
All the accounts when used will return an account with the same UUID, namely the first in the list availableProfiles.Steps to reproduce:
1. Login to the launcher with an account with multiple profiles. (Ex: "DaQa")
2. Select a user and join a server that you can view your UUID from
3. Relog into the account using a different user.
4. Join a server that you can view your UUID from
The advancement "Take Aim" is granted to the player if they reflect a Ghast fireball at a Ghast if they do not already have the advancement. The advancement is described as "Shoot something with a bow and arrow." This would not be super uncommon to have happen in survival as some players won't have bows by the time they enter the nether. This bug is due to the fact that the advancement minecraft:adventure/shoot_arrow checks player_hurt_entity for "is_projectile" being true, which, since Ghast fireballs are projectiles, completes the advancement. Some possible ways to fix this would be to add a check to the advancement to make sure the projectile is an arrow, or reword the description to just "Shoot something."
The advancement "Take Aim" is granted to the player if they reflect a Ghast fireball at a Ghast if they do not already have the advancement. The advancement is described as "Shoot something with a bow and arrow." This would not be super uncommon to have happen in survival as some players won't have bows by the time they enter the nether. This bug is due to the fact that the advancement minecraft:adventure/shoot_arrow checks player_hurt_entity for "is_projectile" being true, which, since Ghast fireballs are projectiles, completes the advancement. Some possible ways to fix this would be to add a check to the advancement to make sure the projectile is an arrow, or reword the description to
just"Shoot something."The advancement "Take Aim" is granted to the player if they reflect a Ghast fireball at a Ghast if they do not already have the advancement. The advancement is described as "Shoot something with a bow and arrow." This would not be super uncommon to have happen in survival as some players won't have bows by the time they enter the nether. This bug is due to the fact that the advancement minecraft:adventure/shoot_arrow checks player_hurt_entity for "is_projectile" being true, which, since Ghast fireballs are projectiles, completes the advancement. Some possible ways to fix this would be to add a check to the advancement to make sure the projectile is an arrow, or reword the description to something like "Shoot something."
Confirmed for 1.8.7 as well.
It works as expected in my singleplayer world.
I found the problem, It seems in multiplayer you can not use capital letters in folder/file names but in Single Player you can.
(And I did test & confirm moving the world from single player to multiplayer does not work)
I don't think so, it could just be the OS I'm using and if not it'd probably need a new ticket for the real issue anyway.
Unfortunately still a thing in 1.11.2; had a script to run a bunch of RCON commands from a text file and this is the crash I get.
http://pastebin.com/raw/3uUR383P
As there are no longer any accounts with multiple profiles it's impossible to do a proper test, but with custom responses to the latest launcher's authentication requests I've found out that this issue is fixed in the latest launcher version.
Still a thing for 17w06a
Just had this happen on a vanilla 1.11.2 server.
Seems to be more common now in 17w15a and 17w14a, possibly breaks on more than just connection issues now?
Still appears to be an issue in 17w17a, However I've never had a crash when there are no players on the server, Perhaps the crash only happens when players are online?
Also affects the full release 1.13