Inara updates, bug reports, requests
When you try to link your accounts, you may receive the http error 400 about expired tokens. It's an issue on Frontier's end that I cannot solve on Inara. Fortunately, the solution is simple - please give it a few days and it will start to work later (probably when the access token on their cAPI server expires). If the error 400 appeared later and it worked before, try to reauthenticate as said in the error message (may be just a regular reauth forced by Frontier). Alternatively, you can try to use the workaround below. If even that won't work, it's the problem described above.
Please vote for the issue on the official bug tracker: https://issues.frontierstore.net/issue-detail/21258
Possible workaround: Try to connect the account while you are in the game. It may work.
Game data and imports not available for console commanders and PC players with Legacy game version
Inara supports only the Live game version (so PC Horizons 4.0 and Odyssey) since game update 14, thus all the game data on the site and the commander data imports work only for those game versions.
today, 12:41pm
Aunty SledgeJ. J. ThomsonHello to everyone,
I was looking at the ship details in my hanger, and noticed my starting sidewinder shows '-' for the jump range and cargo capacity. My cobra shows the proper values. I only have these two ships since I cleared my save after returning to the game years later.
I use EDDiscovery for API syncs, but I could not find any journal entries that contain these values. My assumption is that Inara calculates them to populate the ship details page. Is there anything I need to do to get those values to update for the sidewinder? It's on OCD thing of mine.
I've used EDDiscovery to sync data since the very first journal entry on this character, so everything should be synced. Ship modules, etc. are all current and accurate.
Thanks Artie!
I can help you with that one as I've had to do the same myself. Jump into each ship, log out to menu and back into the game. That will generate the journal entry with all your stats on the ship you are in.
Do that for each ship with missing stats and they will eventually make their way into Inara. The important bit is to be in the ship with imcomplete data when you log in.
Thanks! That did it.
today, 4:56pm
AHIs there a way to "ping" Fleet Carrier to see if it's still where it was last reported?
Not really. If the owner is registered on Inara and Inara has a valid Frontier API access token, then the carrier’s location ought to be updated periodically; but even then, the owner might have already moved the FC since the last update. (The owner, or anyone present in the system where the FC is, can also update Inara via a tool like EDMC, but many people don’t, and various bugs and deficiencies in the process may result in the update being delayed.)
AHThis is my 3.. maybe 4th time, when I am way out there, take a detour to get on a FC with services I need, only to find out there is nobody in the system. Time and resources wasted.
As far as I know, the only FCs one can reliably find way out there are listed in the Deep Space Support Array spreadsheet. I suggest to use those only, unless you know the owner of the FC in question and can contact them.
AHI am surprised that ED servers do not push that data out to some type of service we can get notices from.
I am not surprised at all. Having been around since early pre-release versions (being a Kickstarter backer), I am grateful that we do have stuff like cAPI and the journal files. It took years for FDev to start taking this kind of stuff seriously.
today, 7:50pm
Sampi Ogonek
As far as I know, the only FCs one can reliably find way out there are listed in the Deep Space Support Array spreadsheet. I suggest to use those only, unless you know the owner of the FC in question and can contact them.
Thanks. Big help.
BTW, what if they gave you the data and you made it into a searchable like the "nearest"? That would be really awesome.
Thanks.
Link to Inara Discord: https://discord.gg/qfkFWTr