Not sure if it’s related to Havran I being down, but my main testing character is unable to leave sanctum (was on Havran I when it went offline). When trying to use the other warp conduits in sanctum, all other saved locations show as “loading” and “Unable to warp”.
Edit: Not sure if you’re doing something with Havran I now, but I just got the “Websocket closed” message for it and now I can warp to other worlds again - including my creative test world
they can be used on locked worlds; the issue here is that some database-side formats of data changed and it doesnt play well with worlds that were “already locked” before the update; they need manual patching to fix up and not really sure thats worth it
Interestingly I turned right around and found “Soju’s creative world” which was one of the only two I had been on, and should have been one of the entries shown as “offline” above.
@Soju-VB did you get a new world or have to rename it again? I’m curious, though I’m not sure if it matters to actual testing with @lucadeltodecso’s comment above.
EDIT: actually it might be relevant that once I used a warp augment to create a warp c back to the planet, it reappeared in place of one of the “offline” entries that was already in my list. Strange
No, it is my old world, and it was the only option given to redeem the key against. Also still has stuff on the world just like it was when it got locked before
EDIT: I did do it all from Dand though, not the sanctum… not sure if it matters.
that part is to do with how the client tracks data about the worlds in the list, its been expanded so internally is tracking much more data… but it cant get updates about that data on locked worlds, so until the world is unlocked it would show up without a name etc in the list [ but wont happen if locked again as then does have the data ] … again its more “things change in the background, and not worth complex migrations to patch up bad data just for Testing when wont be a problem in live”