esi-issues
esi-issues copied to clipboard
esi
ESI reporting incorrect character location
Bug
Character Location doesn't update after either a jump clone or a podding
Request
/v1/characters/ [ id ] /location
Response
The return is the system you cloned from or died in and not the system you respawn in. It stays this way until you gate/bridge to another system
Expected
After pod jumping or re-spawning in a medical clone the characters location to be correct
Just a little more detail : this will continue to report the wrong system until you un-dock into space
Just closed several duplicate issues all related to this one. Please use this issue has the root for Frozen Location issues with the /characters/{character_id}/locations endpoint.
Encountered this issue a few days ago. None of the above has fixed the issue. When the cluster shutdown happened last night my location was updated to the system that I was in during the shutdown, but it’s now stuck on that location.
Location does not update after pod death: Confirmed Location does not update after jump clone from station to station: Could not reproduce
I'm going to do some testing to see if there's a difference between JC'ing between stations and citadels, but if anyone has extra info along these lines it'd be really helpful.
I have had this occur when I have not been podded and have not clone jumped. Also it has persisted through downtime (although location was moved to location at downtime it remained stuck at the location). It is happened sporadically over the last year and half.
I do not know if this is the same issue, a related issue, or something else entirely.
Both characters on my account are not tracking today. No clone jumps or podding.
Not sure if this is a commonality or not but I spend a lot of time in wormholes and flip back and forth between characters on this account.
Experienced this very bug just today. Started after Downtime on the 14th of Nov, and still ongoing as of now. Hoping for downtime today (15th) to clear it. It was not triggered by podding, or any Abyssal activity. Just plain normal jump cloning.
If it gets stuck due to podding it does not fix itself when the user changes ship, but it does if the user undocks.
I'm going to pursue that angle since it's all we've got at this point. We're still very scant on details for all these other cases, unfortunately.
I just experienced this issue on my character Jim Antollare. I don't believe mine was triggered by jump cloning, it just started happening when I logged in. It appears that whatever the issue is persists from downtime to the next downtime. I logged into Jita 4-4 in a Gnosis and that's what ESI reported as my location until the next downtime. It didn't update between changing systems, ships, undocking, or logging out and back in. Downtime appears to fix the issue as my character location is now updating normally.
Just tested again to avoid false wh connections created due to podding. Location did not update after being podded. It updated after undocking.
Just happend to me multiple days in a row now. no podding or clone jumping. However i did notice it happens if characters are being disconnected - like cluster shutdown on downtime, or the shortage that happned today (04.11) at 15:35 ET. So far i have tried changing pods (same-citadel changing), getting podded, changing ships, docking somewhere else, logging out in space, forcefully shutting down the game client and it's connection to the server, but it appears only downtime fixes it.
This happened to me as well now. I haven't been killed, podded or done jump clone jumps. My character location & ship information doesn't update. I have tried undocking, switching ship, jumping around.
I lost connection to cluster few times during the night, but I didn't notice when this problem exactly started. It worked yesterday before downtime, as we were doing WH ops.
Hi there -- this is currently happening to me. No updating of location from wh jump to wh jump.
CCP Devs are fully aware that this is a bug with this particular endpoint. if you experience this issue, please upvote the OP instead of doing a +1 post or equivalent. Thank you
Happend to me as well, one day working, next day broken, next day working, next day broken... behaviour always resets at downtime
It has nothing to do with podding or clone jumping as the first report suggests.
