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.
22 May 2022, 4:02pm
Inara reports lower values for my "Settlements Rebooted" statistic (statistics > search & rescue > settlements rebooted) than ingame / local journals. My ingame stat is at 67; inara reports 59; my local journal (displayed in ED discovery) reports 63. I've tried both manual updates as well as letting the automatic import run a few times (last ingame update to this stat was 18/05/22), but the lower value displayed on inara remains. I should note that the way this stat is recorded ingame is somewhat inconsistent as it does not always increment on every successful settlement reboot - but should inara not at least match the figure recognised ingame?
Is there anything that I should be doing differently to update my stats here? I'm happy for all suggestions.
22 May 2022, 4:27pm
Syanna Deschaine(Potential?) Bug Report - "Settlements Rebooted" statistic:
Inara reports lower values for my "Settlements Rebooted" statistic (statistics > search & rescue > settlements rebooted) than ingame / local journals. My ingame stat is at 67; inara reports 59; my local journal (displayed in ED discovery) reports 63. I've tried both manual updates as well as letting the automatic import run a few times (last ingame update to this stat was 18/05/22), but the lower value displayed on inara remains. I should note that the way this stat is recorded ingame is somewhat inconsistent as it does not always increment on every successful settlement reboot - but should inara not at least match the figure recognised ingame?
Is there anything that I should be doing differently to update my stats here? I'm happy for all suggestions.
The problem looks in the way the game sessions were imported - the full stats appears to be correct and up to date on Inara, but for medals there needs to be also the import via Import Frontier data performed (assuming there is something to import) as it rely on verified information gained this way. So, your full stats were updated via Inara API to the latest known state (with 67 settlements), but medal remained at 59 settlements as it was last known verified information. The last import made today was made shortly before the session with Statistics event was written into the journal, so it didn't get the latest numbers, yet. It should be alright at the next import, though. Just click the Import Frontier data and it should get in order.
Kimosabe_XJust a suggestion about the EDO bartender material trading. Is it possible to implement a filter for "non relevant" materials ? I did notice a massive increase of assets, goods and data that are not useful for any EDO engineering and are severely cluttering the list. That would be a nice addition imho.
Yes, I know it's straight possible to search for wanted/useful materials, but there are too much to always type them in.
Thanks in advance and sorry if this has been suggested before, but 814 pages are... a lot to get through...
Although it may be certainly handy, I am not exactly sure if I want to support a general "buy everything useful even I don't need it" behavior, due to the limited offers on fleet carriers. I was however thinking about storing the last search form state across the sessions, so the material set, etc. will be still there and it won't be needed to set it all the time. Will that do the trick?
Last edit: 22 May 2022, 4:33pm
22 May 2022, 8:36pm
ArtieSyanna Deschaine(Potential?) Bug Report - "Settlements Rebooted" statistic:
Inara reports lower values for my "Settlements Rebooted" statistic (statistics > search & rescue > settlements rebooted) than ingame / local journals. My ingame stat is at 67; inara reports 59; my local journal (displayed in ED discovery) reports 63. I've tried both manual updates as well as letting the automatic import run a few times (last ingame update to this stat was 18/05/22), but the lower value displayed on inara remains. I should note that the way this stat is recorded ingame is somewhat inconsistent as it does not always increment on every successful settlement reboot - but should inara not at least match the figure recognised ingame?
Is there anything that I should be doing differently to update my stats here? I'm happy for all suggestions.
The problem looks in the way the game sessions were imported - the full stats appears to be correct and up to date on Inara, but for medals there needs to be also the import via Import Frontier data performed (assuming there is something to import) as it rely on verified information gained this way. So, your full stats were updated via Inara API to the latest known state (with 67 settlements), but medal remained at 59 settlements as it was last known verified information. The last import made today was made shortly before the session with Statistics event was written into the journal, so it didn't get the latest numbers, yet. It should be alright at the next import, though. Just click the Import Frontier data and it should get in order.
Thanks for the explanation - I have to admit I didn't quite get that, but as long as this is in fact not a bug I'm happy. I guess what I am confused about is that I was under the impression that importing data from frontier (either via the manual button or the daily auto-update) would always result in verified data - but that (apparently?) wasn't happening. E.g. my ingame stat now shows 72, I finished my session and used the manual "import data from frontier" button - but now the inara stats page (not the medals page) claims my stat is at 68. ED discovery also reports 68 (but doesn't have my inara api key so shouldn't talk to my inara account at all), only EDMC does (presumably sending the 68 stat?). Still not sure why the data import now directly from frontier after my session concluded still seems to lag behind.
Well, I guess as long as you know what's going on (and that nothing is going awry), that's what's important
22 May 2022, 8:56pm
I have been doing a few lately but they just don't add up to the number of missions I have completed.
22 May 2022, 9:56pm
KilladarkNeed some clarification regarding the samaritan medal. What does it mean by settlements rebooted? Are they unique?
I have been doing a few lately but they just don't add up to the number of missions I have completed.
It's the number of times you've completed a station's power restore mission. The number can be found in your Codex under Search and Rescue. The Codex doesn't update in real-time.
22 May 2022, 10:17pm
Syanna Deschaine
Thanks for the explanation - I have to admit I didn't quite get that, but as long as this is in fact not a bug I'm happy. I guess what I am confused about is that I was under the impression that importing data from frontier (either via the manual button or the daily auto-update) would always result in verified data - but that (apparently?) wasn't happening.
...
Yes, that's exactly how it does work, the import via the button always consider the imported data as verified. But, the Statistics event in the journal is usually written just at the game session start (or after a relog to the menu) and the previous import was made something about an hour before such event was there. EDMC/EDDiscovery is also using this event for their numbers, so they may send the value from the game session start but not the value you may see in the game after playing a bit. So if there is no other Statistics event written into the journal near the game session end (for example forced by the menu relog), the numbers may be lagging behind doesn't matter the import method used.
23 May 2022, 7:02am
Artie
Yes, that's exactly how it does work, the import via the button always consider the imported data as verified. But, the Statistics event in the journal is usually written just at the game session start (or after a relog to the menu) and the previous import was made something about an hour before such event was there. EDMC/EDDiscovery is also using this event for their numbers, so they may send the value from the game session start but not the value you may see in the game after playing a bit. So if there is no other Statistics event written into the journal near the game session end (for example forced by the menu relog), the numbers may be lagging behind doesn't matter the import method used.
Thanks for the explanation, really appreciate it - this makes more sense to me now. A lot of moving parts to keep track of, but glad you (and inara) do!
Aunty SledgeKilladarkNeed some clarification regarding the samaritan medal. What does it mean by settlements rebooted? Are they unique?
I have been doing a few lately but they just don't add up to the number of missions I have completed.
It's the number of times you've completed a station's power restore mission. The number can be found in your Codex under Search and Rescue. The Codex doesn't update in real-time.
I've been tracking this stat with more attention in recent weeks because of the medal, and in my experience the Codex either updates instantly (i.e. after the power control panel has fully come online and your mission updates with the green 'settlement powered' checkmark), or it doesn't at all. The game definitely does not track every single successful settlement reboot; usually powering down the settlement, taking the regulator out, resetting the settlement by going into supercruise and booting the settlement up again fixes that though. I would estimate that around 15-20% of successful reboots are not tracked.
Last edit: 23 May 2022, 7:10am
23 May 2022, 8:40am
Syanna Deschaine
Aunty SledgeKilladarkNeed some clarification regarding the samaritan medal. What does it mean by settlements rebooted? Are they unique?
I have been doing a few lately but they just don't add up to the number of missions I have completed.
It's the number of times you've completed a station's power restore mission. The number can be found in your Codex under Search and Rescue. The Codex doesn't update in real-time.
I've been tracking this stat with more attention in recent weeks because of the medal, and in my experience the Codex either updates instantly (i.e. after the power control panel has fully come online and your mission updates with the green 'settlement powered' checkmark), or it doesn't at all. The game definitely does not track every single successful settlement reboot; usually powering down the settlement, taking the regulator out, resetting the settlement by going into supercruise and booting the settlement up again fixes that though. I would estimate that around 15-20% of successful reboots are not tracked.
That makes more sense, so i just have to hope it counts
23 May 2022, 9:29am
ArtieHello, I should probably rename that tab - it provides a list of nearest possible expansion targets, so not all inhabited star systems are in there (they cannot be an expansion target, for example because there is too many factions already).
oh, I had no idea this tab was about expansions. but I guess it is only considering normal range expansions, because it definitely is not showing the ones at expanded range.
25 May 2022, 10:47am
Jugom
oh, I had no idea this tab was about expansions. but I guess it is only considering normal range expansions, because it definitely is not showing the ones at expanded range.
Yes, it's using the base expansion range at the moment (it's sufficient in most cases). I have on the todo list to put some button to load systems in the expanded range there, but no ETA for that yet.
27 May 2022, 8:48am
I seem to have broken my import frontier data again, sorry.
There was a problem with Frontier's service while requesting the data. Please wait a couple of hours and then try to repeat your request.
[httpCode: 0, fetchCode: 28]
Is there anything i can do on my end to fix this?
Or to prevent this from happening, with relogging being part of my strat to farm certain mats.
I started playing Odyssey about 2 weeks ago and went overboard on the mats farming.
I have looked into a solution to prevent heavy relogging in the future.
Hope it will work, and i dont have to bother you for this anymore.
Sorry again.
Thanks.
27 May 2022, 10:08am
Kenji_088Hello.
I seem to have broken my import frontier data again, sorry.
There was a problem with Frontier's service while requesting the data. Please wait a couple of hours and then try to repeat your request.
[httpCode: 0, fetchCode: 28]
Is there anything i can do on my end to fix this?
Or to prevent this from happening, with relogging being part of my strat to farm certain mats.
I started playing Odyssey about 2 weeks ago and went overboard on the mats farming.
I have looked into a solution to prevent heavy relogging in the future.
Hope it will work, and i dont have to bother you for this anymore.
Sorry again.
Thanks.
Try disabling the auto import feature and click the import button manually, preferably outside your gaming sessions when no relogging takes place. This usually resolves the problem for me. Just keep in mind that there's a 15 minute cooldown between manual imports.
If you want frequent automatic updates while playing, consider using EDMC which can talk to Inara directly.
27 May 2022, 10:38am
The problem is that journals of game sessions with a high relog frequency are difficult for Frontier's server to assemble (as far as I know, the journals are made of chunks which are "stitched" together on the request). So in the best case, the journal is stitched and served right on the request. In the slightly worse case, it may end with http 206 error which means Frontier's server still didn't finish the work and returned the error, but a repeated request a couple of minutes later should work. The error 28 usually means it's so overwhelmed with putting the journal together that it will very likely never work (but sometimes it may catch up a couple of hours later). Manual importing is usually just a "I will try later" approach when it fails on the previous try (with 206 or 28 errors) and there is a good chance (at least with 206 error) that Frontier's server finished the work meanwhile. But, that's also what the auto-update does (it repeats the request a couple of times with some delays in between, until it stops completely because even the repeated requests got no results).
27 May 2022, 11:10am
Sakashiro
Try disabling the auto import feature and click the import button manually, preferably outside your gaming sessions when no relogging takes place. This usually resolves the problem for me. Just keep in mind that there's a 15 minute cooldown between manual imports.
If you want frequent automatic updates while playing, consider using EDMC which can talk to Inara directly.
Ill give it a shot.
Every little bit helps.
Thanks.
27 May 2022, 11:12am
ArtieAdjusted, please try again. There is no best solution for that, other than trying to leave some delay between the relogs in the game. What was tested by another player some time ago, it seems that having at least two minutes between the relogs should help (and reducing the number of relogs will help even further).
The problem is that journals of game sessions with a high relog frequency are difficult for Frontier's server to assemble (as far as I know, the journals are made of chunks which are "stitched" together on the request). So in the best case, the journal is stitched and served right on the request. In the slightly worse case, it may end with http 206 error which means Frontier's server still didn't finish the work and returned the error, but a repeated request a couple of minutes later should work. The error 28 usually means it's so overwhelmed with putting the journal together that it will very likely never work (but sometimes it may catch up a couple of hours later). Manual importing is usually just a "I will try later" approach when it fails on the previous try (with 206 or 28 errors) and there is a good chance (at least with 206 error) that Frontier's server finished the work meanwhile. But, that's also what the auto-update does (it repeats the request a couple of times with some delays in between, until it stops completely because even the repeated requests got no results).
It works again, thanks.
I usually dont relog that often, unless i have a session where i farm mats intensely.
Ill look into a more timed out approach too.
Thank you again.
Last edit: 27 May 2022, 11:28am
Link to Inara Discord: https://discord.gg/qfkFWTr