mojira.dev
MCPE-188266

Removing ticking area prevents beacon effects in origin chunk

After removing a ticking area circle of radius 4 from my base, the chunk where the ticking area was centered is prevented from having beacon affects applied to players within it.

I have been unable to reproduce this on a new world created to try to reproduce this, but it is consistent on my existing survival world.

My world is a single-player survival world, hosted on my PC, although it is open to multiplayer.

Background: Due to the minecart stoppage bug, and the annoyance of having to have another player at my base to keep the carts running, I applied a ticking area as a circle with radius 4 to my base chunks. That covered all my farm carts and did prevent the carts from stopping.

I removed the ticking area to see if the current Minecraft version fixed the issue with the cart stoppages.

I then noticed that when I am within my base living areas (entirely inside the center chunk), I had no effects from my beacons. This lead me to discover that the effects resumed when I step outside the central chunk.

I have a video show this on my OneDrive here: <https://1drv.ms/u/s!ArfRTuC0cl3qhJMX0iS1GSlICX8GXA?e=4XBLKi> Unfortunately that is too large to attach here.

Restoring the ticking area restores the beacons' effects.

Comments 4

To help in confirming your report, please add the following information to the Description, as shown here:

Steps to Reproduce:
1. (list every step completely, so someone else can reproduce the issue)
2.
3.
Observed Results:
(briefly describe what you see happen, including any message(s) shown)
Expected Results:
(briefly describe what should happen)

Try following your steps to make sure you include everything and can still reproduce the issue yourself.

Screenshots and videos are also helpful, though they should not be used as a replacement for the above information

This report has been temporarily resolved as Awaiting Response. It will automatically reopen when you add information. Please follow the format shown and include all sections (steps, observed, expected). Reports that do not contain all of the requested information and complete steps to reproduce the issue may be closed as Incomplete.
Please review the Bug Tracker Guidelines before creating additional bug reports.

Many players find this Bug Report Creation Form useful for filling in all helpful information.

To help in confirming your report, please add the following information to the Description, as shown here:

Steps to Reproduce:
1. (list every step completely, so someone else can reproduce the issue)
2.
3.
Observed Results:
(briefly describe what you see happen, including any message(s) shown)
Expected Results:
(briefly describe what should happen)

Try following your steps to make sure you include everything and can still reproduce the issue yourself.

Screenshots and videos are also helpful, though they should not be used as a replacement for the above information

This report has been temporarily resolved as Awaiting Response. It will automatically reopen when you add information. Please follow the format shown and include all sections (steps, observed, expected). Reports that do not contain all of the requested information and complete steps to reproduce the issue may be closed as Incomplete.
Please review the Bug Tracker Guidelines before creating additional bug reports.

Many players find this Bug Report Creation Form useful for filling in all helpful information.

I spent some time on trying to reproduce this today. I have been able to reproduce this, and it turns out that this bug is very different from what it first appeared to be.

I could use a suggestion in how to report what appears to be the actual bug to the correct place, because I'm not sure if it's Mojang or an addon creator, but since ticking the beacon seems to fix it, it seems at last partially a game bug.

So what seems to be happening is this: if I load the marketplace addon Markers Pack, then the chunks including the corners of the square radius for a beacon are no longer covered by the beacon effect. The ticking area fixes that somehow, because if the ticking area is large enough to affect the beacon, then the effect does correctly affect the corner chunks. So it's not the location of the ticking area, but whether the ticking area is large enough to cover the beacons that are seeing a truncated effect.

When I load a world with no addons, the bug does not seem to appear. If I deactivate the addon that did exist in my test world and then load it, the bug persists.

So I don't know if this is a bug in something the game is doing, triggered by an API call the addon makes, or what might be happening.

ETA: I have tested when loading a different addon (DragonFire Lite Add-on), and the bug does exist with this addon, so it may be related to loading any addons at all, which does seem like a bug Mojang should know about.

You can close this bug. I'm going to open a new one for this.

ETA: I have created a new bug report to replace this one, that actually reflects the issue correctly: MCPE-188296

InkySmears

(Unassigned)

Unconfirmed

Windows

11

1.21.44 Hotfix

Retrieved