Are you sure this isn't just an extreme problem with your GPU or video drivers?
The performance drop did begin before 1.14 though. Maybe we're dealing with an entirely different issue by now?
This bug report might just be too broad.
Just discovered something: Disabling mob spawning removed all signs of the lag. At 40 players it performed exactly as it should on a $120/month machine.
What I mean is that entities should not have affected performance as much as they have, that is remove the problem completely. It's likely the performance leak is somewhere in there.
That's not a real workaround. The real cause of this problem is input lag, so typing would still be hard at low FPS.
This bug tracker is not for the modded game, though
@RM that might be a problem with your GPU instead
Updated: Elaborated on explosion sounds. They do have a small falloff distance outside of the 32 block radius, but are also full volume inside of it.
I'd like to point out that this issue creates a gateway for custom active items to be implemented in maps. Carrot on a stick can be used as a "unversral right click detector", and paired with a resource pack durability predecate for textures, to generate up to 26 custom items - or even more if negative durability values are used.
The rare case of having to detect a pig speed boosted with a carrot on a stick over unmodded custom items, this is a tough choice indeed
The issue didn't go anywhere, still around on pre 8
[media]Still an issue, even after changing desktop environment.
The issue appears during performance (FPS) drops, and gets worse the lower and less stable the FPS is. It also occurs for every linux user I know.
This issue appears again in 1.13pre-5 (and 4)
[Client thread/ERROR]: Invalid icon for server Minecraft Server (ip.censored)java.lang.IllegalArgumentException: Illegal base64 character a
at java.util.Base64$Decoder.decode0(Base64.java:714) ~[?:1.8.0_51]
at java.util.Base64$Decoder.decode(Base64.java:623) ~[?:1.8.0_51]
at ckd.g(SourceFile:211) [1.13-pre5.jar:?]
at ckd.a(SourceFile:143) [1.13-pre5.jar:?]
at cgc.a(SourceFile:33) [1.13-pre5.jar:?]
at cgh.a(SourceFile:391) [1.13-pre5.jar:?] //from here and on different lines are referenced
at cgh.a(SourceFile:194) [1.13-pre5.jar:?]
at cka.a(SourceFile:310) [1.13-pre5.jar:?]
at csa.a(SourceFile:795) [1.13-pre5.jar:?]
at cep.c(SourceFile:808) [1.13-pre5.jar:?]
at cep.a(SourceFile:373) [1.13-pre5.jar:?]
at net.minecraft.client.main.Main.main(SourceFile:143) [1.13-pre5.jar:?]
peregrine fuller, iOS has an entirely different codebase, and runs on different kind of hardware, so this can't be the same issue
i advise you to look in the Minecraft (Bedrock Codebase) section
I was able to reproduce it in 18w05a
Attached files to the issue: issue in action
Command run:
/execute at MetoolDaddy anchored eyes facing 1026 71.5 1062 run particle minecraft:flame ^ ^ ^3 0 0 0 0 1 force
Using particle end_rod for command block, flame for manually ran command
Luis, if that was the case, clientside mods like Optifine wouldnt have fixed it. But they do.
Can confirm for 1.11 release
Definitely intentional
All explosions are extensions of the same exact behavior. If they were all meant to have 100% drop chances, it would have just been hard-coded into the base behavior and wouldn't have been affected by it's source - a bug like this wouldn't even be possible.