COMPLETED CG Maintain Reorte's Alliance Membership (Trade)

Status
Thread Closed: Not open for further replies.
Interesting - I had read this before, and tried it with seemingly no success, so assumed it was just people drawing incorrect conclusions from observations.

I'll hold my hand up if I'm wrong - even though I tried it, it honestly sounded like the sort of thing FDev wouldn't implement in a million years! Any suggestions for a station that's likely to be busy enough to test it out?

Edit: I guess the megaship, but presumably only in open?
If it's NPC behaviour you're investigating then solo would be better. Any station with a single pad of a given size will do, outposts and megaships usually fit the bill.

In my case it was Rackham's Peak which was both an outpost, very busy, and you were guaranteed to have an NPC spawn before you could get within 7.5km. That's not exactly an easy station to drop in on for a bit of testing. Unfortunately I can't think of any other outpost that's quite as busy off the top of my head, although in my experience any outpost will spawn an npc within a couple of minutes if a player doesn't take the slot.

I'd heard various versions before, like "request once for every pad and it will clear one" or "Target the docked NPC to make them leave". At first it didn't seem to work untill I added the 30 second wait, and then every single time the pad would immediately retract to turn them round. I'd position myself so I could see the pad behind the left panel.
 

Flossy

Volunteer Moderator
I rarely have any problems getting Docking Permission at a Megaship or Outpost since I started doing as stated above - boost as soon as I drop into the instance and request docking when 7.5 KM away. Works every time in Solo. In PG or Open there are more likely to be other commanders also trying to dock. This is the problem with CGs that use Megaships where the majority of commanders taking part are in large ships.
 
Tier 4 and tier 5 are so close they cant be Pixel counted...
Scale bar to 1000 pixel
1 = 90 2 = 175 3= 365... Pixels... 4&5 cant be split...
FOqksO5XIAYC3k1.png
 
As I said earlier: Tier 5 in this CG may be the new way for FD to show unreachable tier.
As tier 4 and 5 is right next to each other it points to tier 5 value being a typo again. Yes it was meant to be unreachable but the typo caused the value to be a duplicate of tier 4... and not its full value expect the unreasch able value was meant to be like 600 million but the typo is 66 million...
 
Dumb embarassing noob question - is there an "easy" way to tell from a distance which side of the rings the megaship is on?

So far I have been going with "the spikey ball end points towards the rings...ish" and that's mostly helped whenever an interdiction has sent me off a-wandering, but there's probably some really simple obvious indicator that my brain's sensory processing issues just hasn't registered is there. 😅
 
I'd heard various versions before, like "request once for every pad and it will clear one" or "Target the docked NPC to make them leave". At first it didn't seem to work untill I added the 30 second wait, and then every single time the pad would immediately retract to turn them round. I'd position myself so I could see the pad behind the left panel.
I just spent about 90 mins at an outpost to test this out, but the medium pad gets used by NPCs so infrequently that a proper analysis would take days to collect enough data. I doubt I saw more than 12 NPCs land in that time (I probably missed some, as I wasn't paying full attention while waiting) and only 2 of those went down into the station, the rest just sat on the pad.

Based on the small sample size, the only thing I'd confidently say is that requesting docking access definitely seems to help. In almost all cases, simply requesting docking as soon as the ship had fully landed triggered the departure without needing to target the NPC. I let a couple sit there without requesting docking, just to confirm that they weren't leaving that quickly without any input from me, and they did stick around much longer.

It didn't work every single time. A couple of times the first request didn't trigger departure, but the next one did. On the two times that the ship went inside the station, a simple docking request triggered departure once, but the other time repeated requests didn't work, until I targeted the NPC, which then worked first time. Might be a coincidence, might not - I don't think I had any cases where a request with the NPC targeted didn't trigger departure, but it's a tiny sample size.

Summary: Not enough data to form any real conclusions, but simple non-targeted docking requests seemed to get the job done almost all the time. Maybe some special cases where targeting the NPC helps?
 
Dumb embarassing noob question - is there an "easy" way to tell from a distance which side of the rings the megaship is on?

So far I have been going with "the spikey ball end points towards the rings...ish" and that's mostly helped whenever an interdiction has sent me off a-wandering, but there's probably some really simple obvious indicator that my brain's sensory processing issues just hasn't registered is there. 😅
I use the side that the bulk of the Milky Way is on.
 
Interesting - I had read this before, and tried it with seemingly no success, so assumed it was just people drawing incorrect conclusions from observations.

I'll hold my hand up if I'm wrong - even though I tried it, it honestly sounded like the sort of thing FDev wouldn't implement in a million years!

I've done this multiple times and it works like clockwork. Anyone who's done the Booze Cruise in Rackham's Peak will tell you the same.

Heck, once or twice I've even gotten NPC messages in local chat saying "Well, time to leave, I guess..." or something to that effect, which made me lmao.

Any suggestions for a station that's likely to be busy enough to test it out?

Edit: I guess the megaship, but presumably only in open? Stupid idea 🙄

Better test it in solo at any outpost/megaship where you can have a clear view of the pad so you can target the NPC.
 
As tier 4 and 5 is right next to each other it points to tier 5 value being a typo again. Yes it was meant to be unreachable but the typo caused the value to be a duplicate of tier 4... and not its full value expect the unreasch able value was meant to be like 600 million but the typo is 66 million...
Note the following:
  • While T5 isn't shown on left hand panel, it is shown in station CG UI.
  • There is NO dotted line between T4 and T5 in station CG UI.
  • T5's bracket is bugged (at least on my system - it overlaps CG UI).

This does not seem to be in line with "typo", but fits perfectly with "new unreachable tier method".

Anyway, we'll see - if this CG will reach the predicted 66M tons.
 
Inara gets the number from the official API that even the official site uses.
I went looking for docs about official APIs the other day and turned up a complete blank. I have heard of the "companion API" and perhaps that's not the only one.
In any case, all I could find were fan-made sites with links to the old version of the forum so not a single link worked...
If you have links to docs I'd be really grateful! :)
 
Note the following:
  • While T5 isn't shown on left hand panel, it is shown in station CG UI.
  • There is NO dotted line between T4 and T5 in station CG UI.
  • T5's bracket is bugged (at least on my system - it overlaps CG UI).

This does not seem to be in line with "typo", but fits perfectly with "new unreachable tier method".

Anyway, we'll see - if this CG will reach the predicted 66M tons.
Horizons still has linear display mode on the primary screen that is the included Photo that is exactly 1000 pixels from 0 to 66million, the secondary screen uses the font rules to seperate the markers so that there readable and has never been linear display value...
Its made up so the text is readable the first primary display has no text so remained linear... second screen is never linear as showing Billions for combat would cause over laps in text values for early tiers..
 
Last edited:
Status
Thread Closed: Not open for further replies.
Back
Top Bottom