yeah. i mean i think arcane is talking about the default net cull distance. Where an actor stops replicating to clients once their beyond a certain distance, to save on performance. But in this case it seems to be a bug with the entity system. Movement replication appears to be based on the players spawn location proximity to the entity, instead of the players current location to the entity.
In other words even if you’re standing next to an entity its movement doesn’t visually update to the client. But if you log its position, it is moving accordingly,
I confirmed this by actually copy pasting my code and applying it to prop blueprints instead. The movement replicates perfectly as long as the player is close enough to the blueprint. But the same exact code on entities only updates movement based on the players spawn location, instead of proximity to the entity.