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

Well, so yeah, I thought we would take a look at a couple of those. So I've got all the categories that you listed.

Give me the category first so I can prime my mind.

So hangars. I'm going to start with hangars. Now, I'm going to pick the ones that I think are interesting in the list, in each segment. These aren't in any particular order. This is just some of what people are working on today. So: PU, multi-locations, instanced hangars, "exterior hangar doors remain closed while interior hangar door opens." So that's when your hangar doors open, but the gateway outside is still locked.

So they belong to two different parts, right? You have the exterior and you have the interior. The interior is yours. You can control that in your instance. The exterior needs to be synchronized with your interior door. So what most likely happens there is, for some reason, your interior thinks you've been given the right to this gateway. Or you could have been given a right to a different gateway, and there's an exterior door opening somewhere to nothing, and your door is opening to a closed door. So there's a few things that could happen there, and normally it's that handshake between the exterior and the interior, via the notorious ATC.

But this one goes with its little brother, overlapping hangars: "Player reposition when landing in hangar: ATC given, but seen as trespassing in someone else's hangar, results in being repositioned." Which I think is a sibling.

Yeah, definitely, because you're looking at a situation where you think your interior has been given a certain gateway, you're heading there, but it's actually someone else's casa. So you're correctly trespassing, but you've obviously incorrectly been told that it was yours.

And then the third of the trifecta in this segment, if you put them all together, is "players can get stuck at repositioning player indefinitely after getting impounded." And so if you get impounded, there's a chance that the server will never complete the repositioning that's supposed to take you out of your hangar. Most likely in this case it's one of our charter elements, which is that there's an asynchronous call waiting for a callback that never happens. There should be a timeout so that it can be retried and complete. In this case, it gets stuck there.

It can also be validation. For some reason, the reposition positions that were created are no longer valid. Because I think one of the rules is you will not be repositioned until we know there's floor underneath you. So until there's floor.

And that's a learning, because I'm sure that we repositioned before without checking that. That led to some interesting ones.