Ticking areas extend beyond user defined parameters in 1.18.30

Partner Rank: 1 (Critical)

Partner Team Reporting: Oreville Studios

Verification builds: 1.18.30.04_rc2

Summary:

In 1.18.30, ticking areas now extend several chunks further in each direction than what is defined in the /tickingarea command. If you want a single chunk as a ticking area, this is no longer feasible in 1.18.30 as this radius seemingly extends tens of chunks around the ticking area. This did not occur in 1.18.12.

Impact:

This impacts content in development. We often execute commands off of a marker entity in a ticking area that we have defined in a single chunk. If the chunks around a ticking area are also loaded, it can cause command selectors to target the incorrect entity. This can cause progression of the game to halt in certain scenarios in our content, and possibly in other partner's content.

Repro Steps:

1. Download the attached world.
2. Run /tickingarea list to confirm that the ticking area defined is the chunk boxed in wood.
3. Click the command block button to teleport away.
4. Click the command block button to execute "/say hi" as any loaded husk.

Observed Results:

The husk says hi, meaning that the husk is loaded outside of the defined ticking area. This means the ticking area extends beyond user defined parameters.

Expected Results:

The husk should not be located and the command should fail.

Screenshots/Videos attached: Yes (https://www.youtube.com/watch?v=qROqlKzog_w)

Regression Builds: 1.18.12