🐞 Problem Description
When a model entity's hitbox is initially generated at a position that falls outside the player's simulation distance, the hitbox entity becomes completely frozen. Since hitbox entities rely on the server's entity activation system (entity ticking), they never receive any tick updates if they are spawned outside the loaded simulation range. As a result, the hitbox fails to update its position, rotation, and collision state, effectively staying stuck at its spawn position indefinitely.
the trouble may be only on folia
Steps to reproduce:
1.Set the server's simulation distance to a small value (e.g., 4 chunks).
2.Spawn a model entity whose hitbox(es) will be generated at a location far enough from the player, outside the simulation distance.
3.The hitbox will remain frozen at its initial position and never move or update.
🧪 Test Model / Code
🐞 Problem Description
When a model entity's hitbox is initially generated at a position that falls outside the player's simulation distance, the hitbox entity becomes completely frozen. Since hitbox entities rely on the server's entity activation system (entity ticking), they never receive any tick updates if they are spawned outside the loaded simulation range. As a result, the hitbox fails to update its position, rotation, and collision state, effectively staying stuck at its spawn position indefinitely.
the trouble may be only on folia
Steps to reproduce:
1.Set the server's simulation distance to a small value (e.g., 4 chunks).
2.Spawn a model entity whose hitbox(es) will be generated at a location far enough from the player, outside the simulation distance.
3.The hitbox will remain frozen at its initial position and never move or update.
🧪 Test Model / Code
toro_enderdragon.zip