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.
26 May 2020, 5:54pm
ArtieArne S. SaknussemmHello Artie,
the import of the Frontier data seems to have missed a system I flought through two days ago.
Even using EDDiscovery didn't work. Any idea on what did happen?
THX
S
Hmm, possibly that jump wasn't recorded in the journal by some accident? No idea, but I can check the journal - which star system at what timestamp? Do you remember from/to which system you were jumping before/after?
Outott SX-G c24-1 - May 25, 2020, 6:38:05 PM (Jumping from here)
Outott UA-F d11-15 - May 25, 2020, 6:48:06 PM (missing system)
Outott ZG-D d12-14 - May 25, 2020, 10:10:04 PM (Jumping to this system)
Both EDDiscovery and ESDM registered the system...
26 May 2020, 7:50pm
26 May 2020, 8:15pm
The megaship types is populating correctly, which is really handy. I think range is the only value that commanders will need to input.
27 May 2020, 12:09am
28 May 2020, 11:46am
29 May 2020, 2:18pm
I now have to get my members to re-link their ids and recreate my squadron profile from scratch!
We may not have been active in-game nor on this site for a while but the squadron removal without warning does not seem to be warranted nor reasonable.
29 May 2020, 2:32pm
Arne S. Saknussemm
Outott SX-G c24-1 - May 25, 2020, 6:38:05 PM (Jumping from here)
Outott UA-F d11-15 - May 25, 2020, 6:48:06 PM (missing system)
Outott ZG-D d12-14 - May 25, 2020, 10:10:04 PM (Jumping to this system)
Both EDDiscovery and ESDM registered the system...
Thanks for the details. To be honest, after an investigation, I have no idea why the star system was not registered into the flight log. Everything seems to be normal and I am unable to replicate it (the star system gets added to the log as expected). Please let me know if that will happen again (hopefully it will not).
Spidey002 "Rambo"We're trying to add in-game squadrons to our description page. It seems like we're only able to add 3. The Fatherhood has 6...
As mentioned on Discord, added to the list, but no ETA.
Aunty SledgeI've seen the first Megaships being auto-added to Inara. Megaships are always owned by the system controller, so you could complete the Faction, Government, and Allegiance fields when adding them.
The megaship types is populating correctly, which is really handy. I think range is the only value that commanders will need to input.
Which megaship types in particular? Because, for example, the incursion response vessels are belonging to Aegis.
100.RUBThe "Open Squadron Discord" button keeps telling there is no more than 102 people online, even when we have more than 10 times that.
Yeah, it's probably caused by the old Discord widget which doesn't seem to provide a relevant number (and is cutting the list of people present). I made a quick look for an easy fix before, but it seems there will be more changes needed, so I will take a look on that later.
Pax RabbitOn what grounds was my Squadron removed from INARA?
I now have to get my members to re-link their ids and recreate my squadron profile from scratch!
We may not have been active in-game nor on this site for a while but the squadron removal without warning does not seem to be warranted nor reasonable.
Small squadrons are disbanded after three months of inactivity (it's mentioned on the squadron edit page) to prevent occupying the names. Inactivity means no member will appear here or make an update of his/her game data, so the squadron is considered as inactive/abandoned. I have moved a few things from the old squadron to your new one at least.
29 May 2020, 2:58pm
ArtieSmall squadrons are disbanded after three months of inactivity (it's mentioned on the squadron edit page) to prevent occupying the names. Inactivity means no member will appear here or make an update of his/her game data, so the squadron is considered as inactive/abandoned. I have moved a few things from the old squadron to your new one at least.
That is a relatively new condition, and not a particularly clear nor reasonable one IMO. I can understand that there are data management issues to be considered but there should at lease be an attempt to contact the membership before summarily removing the squadron, unlinking it from the associated users and other squadrons.
And what qualifies as inactivity? Personally I have actually logged in to the game in the past 3 months, just not had much time to spend in the game due to various real-world concerns. My other squadron members have been unable to log-in for similar reasons.
29 May 2020, 3:09pm
29 May 2020, 3:14pm
ArtieI chose this approach as there were quite frequent requests like: "The commander AB is occupying the squadron name XY, although that squadron appears to be dead."
The problem with this is that the approach is not consistent with ED's management of squadrons, exceptions should be made for those with linkages to in-game squadrons and at the very least a warning should be sent in advance to the squadron leader.
29 May 2020, 7:03pm
ArtieArne S. Saknussemm
Outott SX-G c24-1 - May 25, 2020, 6:38:05 PM (Jumping from here)
Outott UA-F d11-15 - May 25, 2020, 6:48:06 PM (missing system)
Outott ZG-D d12-14 - May 25, 2020, 10:10:04 PM (Jumping to this system)
Both EDDiscovery and ESDM registered the system...
Thanks for the details. To be honest, after an investigation, I have no idea why the star system was not registered into the flight log. Everything seems to be normal and I am unable to replicate it (the star system gets added to the log as expected). Please let me know if that will happen again (hopefully it will not).
Maybe I just found Rax.... O_O
29 May 2020, 7:11pm
Artie
Aunty SledgeI've seen the first Megaships being auto-added to Inara. Megaships are always owned by the system controller, so you could complete the Faction, Government, and Allegiance fields when adding them.
The megaship types is populating correctly, which is really handy. I think range is the only value that commanders will need to input.
Which megaship types in particular? Because, for example, the incursion response vessels are belonging to Aegis.
The megaship type IS being populated correctly. Just saying, this is a cool feature.
29 May 2020, 9:53pm
ArtieAunty SledgeI've seen the first Megaships being auto-added to Inara. Megaships are always owned by the system controller, so you could complete the Faction, Government, and Allegiance fields when adding them.
The megaship types is populating correctly, which is really handy. I think range is the only value that commanders will need to input.
Which megaship types in particular? Because, for example, the incursion response vessels are belonging to Aegis.
XX-class Reformatory and XX-Class Traveller megaships in my vicinity are all under the jurisdiction of the controlling faction. I could probably dig out more quickly, as I have yet to see a non-dockable megaship that didn't belong to the system controlling faction in my vicinity. So I would expect the Aegis ships to be the exception rather than the norm?
30 May 2020, 8:09am
DragoCubXArtieAunty SledgeI've seen the first Megaships being auto-added to Inara. Megaships are always owned by the system controller, so you could complete the Faction, Government, and Allegiance fields when adding them.
The megaship types is populating correctly, which is really handy. I think range is the only value that commanders will need to input.
Which megaship types in particular? Because, for example, the incursion response vessels are belonging to Aegis.
XX-class Reformatory and XX-Class Traveller megaships in my vicinity are all under the jurisdiction of the controlling faction. I could probably dig out more quickly, as I have yet to see a non-dockable megaship that didn't belong to the system controlling faction in my vicinity. So I would expect the Aegis ships to be the exception rather than the norm?
Ahh, I mis-understood the point Artie was making. To clarify my findings (and agree with DragoCubX's). All non-landable megaships I have found (and I've recorded the flight plans of dozens) are always controlled by the system owner. Landable ones added as part of Xeno responses are controlled by Aegis. There are special megaships like the The Gnosis which is controlled by Canonn Gnosis Division but again this is a landable megaship.
30 May 2020, 10:28am
Aunty SledgeI've seen the first Megaships being auto-added to Inara. Megaships are always owned by the system controller, so you could complete the Faction, Government, and Allegiance fields when adding them.
The megaship types is populating correctly, which is really handy. I think range is the only value that commanders will need to input.
Wait with this. I already found 8(!) non-dockable megaships, what are NOT owned by the system control faction. (Banner/Hogan/Samson class bulk megaships.)
Link to Inara Discord: https://discord.gg/qfkFWTr