These fixes were originally written by Fuzs_, who asked me to implement Particle Fixes into RandomPatches.These fixes work on Minecraft 1.10 and newer and are server-sided.Explosion particles when the ender dragon destroys blocks upon touching them.A heap of heart particles around one of the parents when a baby animal is born.Smoke when placing an eye of ender in an end portal frame.Armor breaking particles when worn by a mob.Red particles on redstone torch burn out.Large smoke particles when lava and water mix.Snowball particles when an iron golem or wither boss is built.Small snow particles upon building a snow golem.Heart particles constantly popping up from animals in love.Lots of particles will appear once again that haven't done so in the vanilla game since Minecraft 1.3 from July 2012.MC-93826 - Breeding hearts show only once instead of all the time an animal can breed.MC-10369 - server-sided particle spawning doesn't spawn particles for clients (fixed in Minecraft 1.14).Many of Minecraft's particles aren't shown due to two long-standing bugs:.The login timeout is entirely server-sided, but the read timeout is both client and server-sided.These timeouts can be configured and take effect in-game, unless the NetHandlerPlayServer patches are disabled in the configuration.This also sets the 'fml.readTimeout' and 'fml.loginTimeout' system properties.The login timeout generally has more impact than the read timeout.

Do not increase the KeepAlive packet interval unless necessary.The read timeout is automatically rounded up to a product of the KeepAlive packet interval.This interval can also be configured on Minecraft 1.9 and higher. The read timeout is the time the server waits for a response to the KeepAlive packet it sends every set interval.By default, RandomPatches sets the read and login timeouts to 90 seconds.On Minecraft 1.9 and higher, RandomPatches allows you to configure the login timeout, and on Minecraft 1.12 and higher, the read timeout is also configurable.The read and login timeouts are hardcoded in vanilla Minecraft, and are often not long enough for slower computers.Walking into it will still add it to the inventory. There will now be an invisible dropped item.JDB will immediately say that the breakpoint was hit in thread=Render thread type resume a second time to resume it. After a second, type resume to resume all threads.This specifically needs to be done to ensure the item gets ticked before entity metadata is received, and is what actually reproduces the race condition. Type resume 1 in JDB to resume the render thread (which should advance one frame and then freeze again, or may unfreeze the game completely).The game will freeze with the breakpoint hit in thread=Netty Client IO #2 (or similar).Make sure that the item will land far enough away that it won't be picked up immediately. This can be done by breaking a block or tossing an item in your inventory. If this is accidentally triggered, you will need to run resume several times. Note that this means that any entity metadata change will trigger the breakpoint, which includes sneaking and sprinting. In JDB, type stop at ra:11 (where ra is ClientboundSetEntityDataPacket as of 1.16.4-pre1, and line 11 is handle).Connect to the server, and wait a few seconds.In JDB, type threads and verify that ()0x1 Render thread running appears (that 'Render thread' has ID 1).Open a command line, and run jdb -attach minecraft.Add -agentlib:jdwp=transport=dt_shmem,address=minecraft,server=y,suspend=n to the client JVM arguments.Disable mob spawning, and kill all entities (due to MC-51732 this will need to be repeated a few times to eliminate slimes). Set up and start a server (superflat is the easiest).This can be a bit awkward to set up, though: One way to force it to happen is to set a breakpoint in the entity metadata packet handler, and then resume the main thread. This bug is a continuation of MC-11834, and also a race condition, so it's hard to consistently reproduce. The shulker boxes are especially worrying, because one invisible shulker box can result in the loss of a lot of valuable materials.Ĭode analysis. I've had it happen with seeds, lily pads and shulker boxes. About Wolfram Wolfram is a hacked client for Minecraft that allows you to do all kinds of cheats and hacks that the game normally wouldnt allow, such as. It doesn't seem to matter what the item is. I've had items turn invisible both when tossing them out of my inventory and when being dropped from broken blocks. It doesn't seem to matter where the item entity comes from. The problem is intermittent, and I haven't found a way to reliably reproduce it.

Item entities turn invisible when dropped on the ground.

Minecraft 1.11 impact client