Tim "timmyRS" Speckhals
- timmyRS
- timmyrs
- Europe/Berlin
- Yes
- No
MC-78124![[Mojang] slicedlime](../../../data/assets/gravatar/slicedlime.jpeg){kind=small}
![[Mojang] Nathan Adams](../../../data/assets/gravatar/dinnerbone.png){kind=small}
![[Mojang] Grum (Erik Broes)](../../../data/assets/gravatar/grum.png){kind=small}
Game State 7 freezing client if value is above 1.0F
Game State 7 freezingclient if value is above 1.0FGame State 7 freezing Client if value is above 1.0F
1. Send Packet 0x1E (Change Game State) with reason 7 ("Fade Value") and a value higher than 1.0F
2. Game freezing
3. Game running out of memory after some minutesWhen a server sends a Change Game State packet (0x20 as of 1.13.2) with reason 7 (Fade Value) and the value is 1 or below, the game runs at maximum FPS, but as we send higher values, the FPS get lower. With value 40, I get 20 FPS. With value 45, I get 10 FPS. And with value 50, I get 2-3 FPS. And, finally, with a value as high as 1000, the game freezes completely and is effectively crashed as it will not recover.
Game State 7 freezing Client if value is above 1.0FIncreasing Game State Fade Values make the game increasingly laggier
3.png
When a server sends a Change Game State packet (0x
20as of 1.13.2) with reason 7 (Fade Value) and the value is 1 or below, the game runs at maximum FPS, but as we send higher values, the FPS get lower. With value 40, I get 20 FPS. With value 45, I get 10 FPS. And with value 50, I get 2-3 FPS. And, finally, with a value as high as 1000, the game freezes completely and is effectively crashed as it will not recover.When a server sends a Change Game State packet (0x1E as of 1.14.3-pre1) with reason 7 (Fade Value) and the value is 1 or below, the game runs at maximum FPS, but as we send higher values, the FPS get lower. With value 40, I get 20 FPS. With value 45, I get 10 FPS. And with value 50, I get 2-3 FPS. And, finally, with a value as high as 1000, the game freezes completely and is effectively crashed as it will not recover.
Windows 8.1 & 10
Java 8
How did this even get Confirmed in the first place? I see no reproduction steps.
Well then please don't complain about duplicates when the issues don't get solved anyways.
Can confirm with Java 1.8.0_51 64bit with Minecarts coming from the east, south, and west. North works as expected when turning into any direction.
Confirmed for 19w11b
When the chat is open, and you click anywhere inside of the Minecraft window that's not the text box (which I do to focus a window), it gets unfocused and key presses except for [Escape] and [Enter] are ignored. This was not an issue in 1.13.2.
Can't reproduce.
When printing partially-obfuscated text, such as with:
/tellraw @s {"text":"Bla ","extra":[
{"text":"Bla","obfuscated":"true"},{"text":" Bla"}]}
The first "Bla" will also be obfuscated for a decreasing amount of frames before normalising completely.
When printing partially-obfuscated text, such as with:
/tellraw @s {"text":"Bla ","extra":[
Unknown macro: {"text"},{"text":" Bla"}]}
The first "Bla" will also be obfuscated for a decreasing amount of frames before normalising completely.
When printing partially-obfuscated text, such as with:
/tellraw @s {"text":"Bla ","extra":[
Unknown macro: {"text"},{"text":" Bla"}]}
The first "Bla" will also be obfuscated for a decreasing amount of frames before normalising completely.
When printing partially-obfuscated text, such as with:
{{/tellraw @s {"text":"Bla ","extra":[
{"text":"Bla","obfuscated":"true"},{"text":" Bla"}]}}}
The first "Bla" will also be obfuscated for a decreasing amount of frames before normalising completely.
When printing partially-obfuscated text, such as with:
{{/tellraw @s {"text":"Bla ","extra":[
{"text":"Bla","obfuscated":"true"},{"text":" Bla"}]}}}The first "Bla" will also be obfuscated for a decreasing amount of frames before normalising completely.
When printing partially-obfuscated text, such as with:
{{/tellraw @s {"text":"Bla ","extra":[
{"text":"Bla","obfuscated":"true"},
{"text":" Bla"}]}}}
The first "Bla" will also be obfuscated for a decreasing amount of frames before normalising completely.
When printing partially-obfuscated text, such as with:
{{/tellraw @s {"text":"Bla ","extra":[
{"text":"Bla","obfuscated":"true"},
{"text":" Bla"}]}}}
The first "Bla" will also be obfuscated for a decreasing amount of frames before normalising completely.
When printing partially-obfuscated text, such as with:
/tellraw @s {"text":"Bla ","extra":[\{"text":"Bla","obfuscated":"true"},\{"text":" Bla"}]}
The first "Bla" will also be obfuscated for a decreasing amount of frames before normalising completely.
When printing partially-obfuscated text, such as with:
/tellraw @s {"text":"Bla ","extra":[\{"text":"Bla","obfuscated":"true"},\{"text":" Bla"}]}
The first "Bla" will also be obfuscated for a decreasing amount of frames before normalising completely.
When printing partially-obfuscated text, such as with:
{{/tellraw @s {"text":"Bla ","extra":[
{"text":"Bla","obfuscated":"true"},
{"text":" Bla"}]}}}
The first "Bla" will also be obfuscated for a decreasing amount of frames before normalising completely.
When printing partially-obfuscated text, such as with:
{{/tellraw @s {"text":"Bla ","extra":[
{"text":"Bla","obfuscated":"true"},
{"text":" Bla"}]}}}
The first "Bla" will also be obfuscated for a decreasing amount of frames before normalising completely.
When printing partially-obfuscated text, such as with:
/tellraw @s {"text":"Bla ","extra":[\{"text":"Bla","obfuscated":"true"},\{"text":" Bla"}]}
The first "Bla" will also be obfuscated for a decreasing amount of frames before normalising completely.
When printing partially-obfuscated text, such as with:
/tellraw @s {"text":"Bla ","extra":[\{"text":"Bla","obfuscated":"true"},\{"text":" Bla"}]}
The first "Bla" will also be obfuscated for a decreasing amount of frames before normalising completely.
When printing partially-obfuscated text, such as with:
{{/tellraw @s {"text":"Bla ","extra":[
{"text":"Bla","obfuscated":"true"}\,
{"text":" Bla"}]}}}
The first "Bla" will also be obfuscated for a decreasing amount of frames before normalising completely.
When printing partially-obfuscated text, such as with:
{"text":"Bla","obfuscated":"true"}
{{/tellraw @s {"text":"Bla ","extra":[{"text":" Bla"}
\,]}
}}The first "Bla" will also be obfuscated for a decreasing amount of frames before normalising completely.
When printing partially-obfuscated text, such as with:
/tellraw @s {"text":"Bla ","extra":[
{"text":"Bla","obfuscated":"true"},
{"text":" Bla"}]}
The first "Bla" will also be obfuscated for a decreasing amount of frames before normalising completely.
When printing partially-obfuscated text, such as with:
/tellraw @s {"text":"Bla ","extra":[{"text":"Bla","obfuscated":"true"},{"text":" Bla"}]}The first "Bla" will also be obfuscated for a decreasing amount of frames before normalising completely.
The scroll bar to the right of the "Controls" menu does not have any effect
. This is not an issue withthe resource packs, singleplayer, or multiplayer lists.The scroll bar to the right of the "Controls" menu does not have any effect, as opposed to the resource packs, singleplayer, or multiplayer lists. This was not an issue in 1.13.2.
Although 1.14 can use resource packs made for 1.13 which both use the same pack_version, any new resource pack made for the 1.14 that changes particles or paintings will not have the same effect in 1.13, and as such pack_format 5 should be usable for newer resource packs. However, currently, 1.14 says that pack_format 5 resource packs were made for a newer version.
The changes between 1.14 and 1.13 are not quite compatible, and as such the pack_version should have been changed to 5:
- Resource packs made for the 1.14 that change particles or paintings don't have the same effect in 1.13.
- Resource packs made for the 1.13 that change stone slabs don't have the same effect in the 1.14 because the texture was renamed to smooth stone and the old file name is not recognized.
Do you have enough disk space left?
If yes, have you tried running as admin? Does it work as admin?
If yes, check if .minecraft is write-protected.
Can you provide a screenshot of your profile settings?
What term exactly?
When you click on "Profiles" and then on the profile you are trying to start.
Can confirm for 1.12 and 1.11.2 client.
Can confirm for 1.12
Can confirm for 1.12
This might duplicate
MC-83353, however, that issue has already been marked as resolved.@SunCat but why would everyone want to see the world warp and shake without the overlay?
This problem still is apparent in the 1.12 on a vanilla server with knockback-enchanted items, when the player receiving the knockback is at a high click speeds. There are over 10.000 videos on youtube by PvP players on this: https://www.youtube.com/results?search_query=knockback+reduction
I've verified that the latest version is still affected and updated the attachments. Excuse the overediting in the demo, but I had to get that file below 10 MB.
It looks like you're on a server. Is it possible that the server you are on is not natively 1.13.2 and only protocol hacking to allow you to join?
You're a master of the search. I tried to find this already being reported and I was unable to find anything.
Confirmed for 19w11b
It does indeed. The search sucks :/
Confirmed for 19w12a.
Confirmed for 19w12a.
Confirmed for 19w12a.
Confirmed for 19w12a.
Confirmed for 19w13b
Confirmed for 19w13b
Confirmed for 1.14 Pre-Release 1.
Confirmed for 1.14 Pre-Release 1.
Confirmed for 1.14 Pre-Release 1.
Confirmed for 1.14 Pre-Release 1.
Isn't the real bug that you can even open the chat while in F1 mode?
Confirmed for 1.14.
Confirmed for 1.14.
Confirmed for 1.14.
I managed to reproduce this on 1.14.4 (by accident, of course)
Can not confirm for 19w40a. Perhaps it was fixed sometime between 1.14.4 and now?
Won't fix? Seems like a simple task to just add version information to the UDP multicast, so it can be displayed in the server list, no?
The air there could be cave_air, although the world generator is not supposed to actually put them in the world. Probably a duplicate of
MC-125135.Confirmed for 19w40a. Also, if the camera is in crouching mode, you enter a shulker, and release shift, the camera will stay in crouching move until you move down from it.
This is related to
MC-158131.I'm trying to look at my map, not at any entites with a glow effect, tho.
Can confirm for 19w40a.
I think you could've put this whole suite of issues into just one issue, which is that particles use a 4-byte floating point number for their X, Y, & Z position, which is notorious for losing precision when you're going to extremely high numbers. If you went far enough into the world, you'd only see particles every 4, 8, 16, etc. blocks.
That sounds like more of an excuse than a reason. Like, yeah, I guess technically it's not a part of the user interface, but it moves around with me, and I can chose to show and hide it at any time. Sounds like a user interface element, if you ask me.
Confirmed for 19w41a.
Confirmed for 19w41a.
Confirmed for 19w41a.
I think this is related to MC-124235.