Console and log are being spammed with "Command Block chain tried to execute more than 65536 steps!" with "enable-command-block=false" in server.properties.
After enabling command blocks and restarting, the actual error from the command block is then also spammed with the chain error
Aug 06 14:40 [Server] WARN Couldn't load custom particle dustAug 06 14:40 [Server] INFO com.mojang.brigadier.exceptions.CommandSyntaxException: Expected ' ' at position 4: dust<–[HERE]Aug 06 14:40 [Server] WARN Command Block chain tried to execute more than 65536 steps!
If command blocks are disabled, Minecraft should not be analyzing the command block chain at all.
Attachments
Comments 7
No data packs.
In the end it took an x-ray mod to locate the rogue command blocks in the spawn area, which were placed by someone with op permissions. The command blocks were removed and the spamming stopped.
#Minecraft server properties#Tue Aug 06 13:19:48 MDT 2019allow-flight=falseallow-nether=truebroadcast-console-to-ops=truebroadcast-rcon-to-ops=truedebug=falsedifficulty=peacefulenable-command-block=falseenable-query=trueenable-rcon=falseenforce-whitelist=falseforce-gamemode=truefunction-permission-level=2gamemode=survivalgenerate-structures=truegenerator-settings=hardcore=falselevel-name=xxxxxlevel-seed=level-type=defaultmax-build-height=256max-players=48max-tick-time=60000max-world-size=10000motd=Mellominecraftnetwork-compression-threshold=256online-mode=trueop-permission-level=4player-idle-timeout=0prevent-proxy-connections=falsepvp=falsequery.port=25565rcon.password=rcon.port=25575resource-pack-sha1=resource-pack=server-ip=xx.xx.xx.xxserver-name=xxxxxserver-port=25565snooper-enabled=truespawn-animals=truespawn-monsters=truespawn-npcs=truespawn-protection=300use-native-transport=trueview-distance=7white-list=false
I just tested this, and can confirm that the server checks for command chain length even if commands run. The message occurs only if there's a command block chain in the world that would run if command blocks were enabled and exceeds the gamerule limit.
I've attached the spawn region file. Start it up on Minecraft 1.14.4 release with "enable-command-block=false" in server.properties and you'll immediately see the error in the console. Also notice that attempting to turn off command block output with the gamerule does nothing.
Having a single powered repeating command block in the world and running /gamerule maxCommandChainLength 0 also does the trick.
Furthermore, /gamerule commandBlockOutput false does NOT suppress the errors in the console.