What else you got [on the bugs being worked on today]?

"Player loses access to persistent hangar at primary residence." It's a classic one. My character is actually in this state right now.

Where is your hangar?

Area 18. The hangar is actually there, but I never spawned it, in my case. But in these cases, with most players I've discussed with, the hangar is actually stowed in another inventory somewhere else for some reason. So that's the hunch so far. We'll see what the team actually comes up with, but that's one that we definitely want to solve. Now, I've got more on the hangar side, but I figure in the interest of time I would keep going with the other categories. We've got login flow related issues. So we talked a bit about shard lock. That's one of them. So basically being a bit more communicative about shard lock, and no longer having shard lock at all for players that stay in the shard. 64008 spawn resolution error and its little brother, 64006 disconnection. Again, resolve player location. I can speak to this one a little bit. This is typically a symptom. If we fix this issue specifically, the display will change. But what actually happens is that when you connect to a game shard, the replication layer, so the hybrid that's in front of it, is going to coordinate bringing your character into the game world. But it doesn't know at the start which of the 10 servers it's running your character should be on. And so it needs one of those servers to help resolve your location, so that we can unstow you in the right area in the tree and then hand off authority to the server that's managing this region. The way this is done is that the replication layer will hand this work off to any of the game servers on the shard. Now, when we have Idrises blowing up servers left and right, there's a very high chance that the server this is handed to is dead, or is in the process of dying and is rebooting. And so what happens in this case is that the player will get to the end of the context establisher tasks, the CETs, and he will get a 64008 or 12 error. We need to make this a bit more robust on that side, so that we know which servers are completely alive, and if a server is doing a reboot, we don't assign them a resolution task. That would be one thing. But also trying to streamline that so that it's a bit more efficient. A small one I wanted to touch on here was "friends list showing 0 out of 1 instead of the player counts per shard." So we're rejigging this bit. It's going to come back. This is a temporary thing.

Is that a priority fix though?

In the login flow section, it is.