Bedrock Dedicated Server: simulatedplayer forced to Simulation Distance 4 regardless of server.properties setting

Description:

On a Bedrock Dedicated Server (BDS), the simulatedplayer entity ignores the simulation distance value set in server.properties.

Regardless of whether the tick-distance (simulation-distance) is set to 6, 8, or 10, any simulatedplayer that is loaded/spawned into the world behaves as if the server is locked to Simulation Distance 4. This causes severe technical limitations in redstone engineering, mob farms, and crop growth mechanics that rely on the simulatedplayer to keep chunks ticking.

Steps to Reproduce:

1. Set up a Bedrock Dedicated Server (BDS).

2. In server.properties, set tick-distance=10 (or any value greater than 4).

3. Join the server and spawn/load a simulatedplayer via commands or behaviour pack.

4. Move the simulated player away from the original player.

5. Observe chunk ticking (e.g., crop growth, hopper speed, mob spawning/despawning) around the simulated player.

Expected Results:

• The simulatedplayer should respect the server-wide simulation distance (e.g., 10 chunks).

• Entities, redstone, and random ticks should remain active within the configured tick-distance range around the simulated player.

Actual Results:

• The simulatedplayer instantly enforces a Simulation Distance of 4.

• Any chunk beyond 44 blocks (Euclidean) or 4 chunks (Manhattan) from the simulated player stops ticking immediately