When you join a party, it puts an identifier over people's heads. How far out does that go? If somebody's on Cellin and you're on Port Olisar, are you going to see a little marker saying this person's on Cellin?
TL;DRParty markers stop updating when far away because entities outside a certain range stop updating; they're deciding whether to fix it, aren't sure it can make 3.2, and it may help performance.
I think I saw a bug that's currently being throttled by streaming, that if you get too far away, it'll just stop updating your information. I don't know if it's a bug. I just saw that was a thing.
So there's a problem: when the entity goes outside of a certain range, it stops updating. And since the marker is also an entity, it is getting affected by it. We are planning to fix it, but I'm not entirely sure if we can get this out in 3.2.
We're deciding if we're planning to fix it.
Well, I also have to imagine there are some performance considerations too, because sometimes that culling, the thing that you refer to as a bug and you say is not a bug, might actually help us in performance. If we don't have to update people from eight different locations around the Crusader system, that could be a benefit, especially as server populations begin to expand past 50, and now you've got everybody sending constant updates. It's not a bug, it's an emergent behavior. So it's a thing that needs continuing investigation. We need to decide whether that's something we even want to address, because, like anything, a big part of bind culling and object container streaming and all that stuff is about limiting the information that we send halfway across the galaxy for no reason.
In the future, we can decide whether we want to manage this design-wise, or technically by updating the position.
We just tell design what they get and they're happy about it.