[Minecraft 1.19] Never Use Repeating or Chain Command Blocks Again | Command Block Project

Channel:

Kloo Live

Subscribers:

4,070

Published on August 7, 2022 8:00:00 PM ● Video Link: https://www.youtube.com/watch?v=0QoaxYdoHvs

Game:

Minecraft (2011)

Duration: 16:59

303 views

6

Hi I'm Kllooooyy, but you can call me Kloo. Heres me playing games or working on a random project hope you enjoy. And don't forget to judge this is the internet after all.
Links below will start streaming when Australia gets better internet :)?

Twitch - https://www.twitch.tv/kllooooyy

TL;DR
When using entity checking commands (variations of @e) the command block will continuously check every possible entity regardless of search parameters (type=XYZ). There's occurs on every possible block update regardless of conditioning or Redstone setting.

The findings of this video indicate that the combination of impulse command blocks and a fill/setblock command adjacent will have substantially less tick lag than large chains. This also indicates that repeating and chain command blocks operate more than once in a single tick where as an impulse command block will always trigger only once.

Therefor it is more beneficial to create an impulse command that triggers every tick or 20 times per sec, rather than ever using a repeating or chain command block.

/setblock ~ ~ ~ minecraft:redstone_block replace
/setblock ~ ~ ~ minecraft:air replace

Other Statistics