Do the new command blocks still cause lag by sending a bunch of packets?
So basically in 1.8 the was a 63 block update limit (as explained here)
My question is when the command blocks changed, does the server still send packets every tick telling the client that the command block were powered? If so is there anything I can do to remove that so I can have a large amount of command blocks near the person and not lag them out? Or in general should I not have my command blocks near the person?
And on a side note, can you also tell me what the block update limit (per chunk) was increased to?
Pictures about "Do the new command blocks still cause lag by sending a bunch of packets?"
How do you stop a command block from lagging?
Client lag is affected by things like a large amount of entities (e.g thousands of dropped blocks or animals, and a few other related things, such as light values on structures running shader-packs, mods, etc). This will cause your FPS (Frames Per Second) to drop, and is the most common type of lag.Do blocks cause lag in Minecraft?
The most common cause of FPS lag is produced when the Nether is entered. This is mostly due to the massive amounts of entities (such as fire) found in the world, as well as the fluids (lava) being generated.What causes the most lag in Minecraft?
In Bedrock Edition, it can also delay before executing commands if "Delay in Ticks" is not 0: When it is triggered, If it has been activated, the chain command block checks whether the command block behind it has executed successfully (if in conditional mode), then it delays.Clear Lag command in minecraft BEDROCK
Sources: Stack Exchange - This article follows the attribution requirements of Stack Exchange and is licensed under CC BY-SA 3.0.
Images: FWStudio, Sarah Chai, Sarah Chai, Ketut Subiyanto