This is happening for me as well on a server running 1.18 and Java 17. I am seeing several impulse command blocks behaving like a repeating command block set to Always Active. The command blocks were placed there when the server was running 1.16.5 and I had no problems in 1.17 and 1.17.1. It seems to be occurring only in command blocks that use the /setblock command.
I am seeing a similar thing happen in a 1.18 server that was upgraded from 1.17. You can walk through the affected chunk, you can place blocks in place of air blocks, but you can't change any existing blocks.
If you do /data get block (coords) on a block entity you get "That position is not loaded" so the chunk is basically both visible and not loaded. Weirdest thing I have ever seen.
Gonna repost there.
This is a duplicate of
MC-62180Someone please remove this report.
This is happening for me as well on a server running 1.18 and Java 17. I am seeing several impulse command blocks behaving like a repeating command block set to Always Active. The command blocks were placed there when the server was running 1.16.5 and I had no problems in 1.17 and 1.17.1. It seems to be occurring only in command blocks that use the /setblock command.
I am seeing a similar thing happen in a 1.18 server that was upgraded from 1.17. You can walk through the affected chunk, you can place blocks in place of air blocks, but you can't change any existing blocks.
If you do /data get block (coords) on a block entity you get "That position is not loaded" so the chunk is basically both visible and not loaded. Weirdest thing I have ever seen.