mojira.dev
MCPE-175604

command block in tickingarea may be scheduled earlier by mistake

I found this issue in creative mode.

I built a structure with command blocks like this

[media][media]

It shows that when I have more than 3 slime balls, it will give me a tnt and remove three slime balls, otherwise it will show me the failed message.

Normally it should work like this:

[media]

[media]

But when I set a tickingarea (I used the sculk to mark it)

[media]

It worked like this:

[media]

So, the priority of blocks in tickingarea may higher than redstone transference. But it shouldn't like this, and I consider it as a bug.

Attachments

Comments 10

[media][media][media][media][media][media][media][media]

It'd be much easier to reproduce this if you just attached the world.

I attached it here, but I didn't check whether the tickingarea still exist. So I'm afraid you should add and remove it by yourself.

[media]

Thank you for your report!

However, this issue has been temporarily closed as Awaiting Response.

Is this still an issue in the latest version? If yes, could you please add it to the affected versions (or mention it if you are not the reporter)?

This ticket will automatically reopen when you reply.

Quick Links:
πŸ““ Issue Guidelines – πŸ’¬ Mojang Support – πŸ““ Project Summary – πŸ“§ Suggestions – πŸ“– Minecraft Wiki

Unfortunately, the issue still exist in latest version.

I am unable to reproduce this. Is this still an issue in the latest release? If so, then please try and give more detailed steps on how to reproduce this. A video showing how you reproduced the bug would probably be best.

Additionally, is this limited to just the world you’ve attached, or does it occur in any?

I’m going to show the procedure with the video. It still affects any world in the latest version of minecraft.

[media]

The first I demostrated is correct function of the command block structure

The second one is the one with problem.

And I noticed another problem on the testing world

[media]

the command blocks seems ranked randomly, regardless of the tickingarea
I’ll attach the testing world here

[media]

It is kind of weird. Sometimes the issue happens and sometimes not.

Meanwhile, set and reset the ticking area may change the order of command block functioning.

The issue won’t affect the command blocks not at the edge of ticking area, nor the command blocks inside the ticking area.

And it seems the command block the button right placed on is being delay for 1 tick than other command blocks that can be activated by the button

mingwangdada

(Unassigned)

Unconfirmed

Multiple

1.20.31 Hotfix, 1.20.32 Hotfix, 1.20.60, 1.21.21 Hotfix, 1.21.80

Retrieved