Weird computer behavior under /tick freeze

[Bamberghh]

Minecraft Version

1.20.x

Version

1.110.2

Details

Logs

I haven't found anything related to CC in the logs but I'm attaching them anyways just in case:

latest.log

Details

The /tick command, that was added in MC 1.20.3, allows for stopping/starting (most of) game ticking. However the computers behave weirdly when /tick freeze is active (note that the list below is in no way exhaustive):

• The computers still respond to commands, however they shut down in 5 seconds and have to be turned on again. They repeat this the entire time the ticks are frozen.
  Steps to reproduce:
  1. Place a computer, turn it on, do something in the terminal
  2. Run /tick freeze
  3. Wait for 5 seconds for the computer to turn off by itself
     Video:

simple.mp4

• The inventory peripheral item transfer still works (I discovered this current issue when trying to measure the item transfer time). Note that the computers still turn off after 5 seconds.

Video:

transfer.mp4

Program to reproduce the behavior shown in the video:

-- transfer.lua

local chestA = peripheral.wrap('left')
local chestB = peripheral.wrap('right')

local function transfer(a, b)
    for i = 1, 54 do
        a.pushItems(peripheral.getName(b), i)
    end
end

transfer(chestA, chestB)
transfer(chestB, chestA)

• Turtles that try to drop/suck items into the world/chests, move or turn, freeze until the game shutdowns them after 5 seconds. After that you can still interact with them, and at the /tick unfreeze the queued actions execute one-by-one.

Video:

turtle.mp4

Additional details

Since I don't know whether any of the described behaviors are correct/incorrect, I've filed this issue partially for further discussion.

Just in case, here are all exact versions of MC or its mods:

• Minecraft 1.20.4
• Fabric 0.15.11
• CC: Tweaked 1.20.4 1.110.2
• Fabric API 1.20.4 0.97.1

[zyxkad]

Related #1868