The great Oya sampling event begins - calling all interested CMDRs!

Status
Thread Closed: Not open for further replies.
unlike the last two Titans there are no npcs at Oya in solo

I think they turn up when the Titan is already damaged quite a bit. And/or when its resistance is lower. At least for Leigong I recall that there also weren’t any human NPCs in my solo instances as long as it’s resistance was at „very high“.
 
I think they turn up when the Titan is already damaged quite a bit. And/or when its resistance is lower. At least for Leigong I recall that there also weren’t any human NPCs in my solo instances as long as it’s resistance was at „very high“.

I don't recall there being any NPCs there when I attacked Leigong in its final moments. I was in a Private Group, but was the only player in the area at the time.
 
Sorry guys, I'm just catching up on stuff... I had been planning to move to Oya very soon, to start attacking it directly, due to the number of systems it'd lost. However, the recent scripted events from FDev - which I missed initially - have left me somewhat puzzled. Should we be attacking Oya now, will it still be effective or is this scripted event going to prevent that mechanic from working for the time being?

I've seen messages about a call to arms to attack Oya NOW, to prevent the results of this script event from working, but are we sure it will. Is there evidence that Oya is taking damage as it should? My main concern is missing that vital Window to deal damage before the Titan goes down. Almost missed it last time, but managed some solid hits literally moments before the Titan fell. For some reason, I'm motivated by those decals... I want all eight!
Yesssss, got my 2M for this week (3M actually) in case it goes down, but at the moment very unlikely as we have slow progress, but there may be a huge increase 🖖🙏 with weekend contributions, you never know, it took time (6 runs IIRC, but remember you need 2M in the week before it goes down to get the rewards). I can now relax and do Oya at leisure to help take it down.
If it doesn't go down by Thursday we will all have to think again thank FDev for following or adhering to their own timeline.

I take it the Hyper/Inter dictions are very RNG at the moment, Hyperdictions about 50% of the times on the way to system, Interdictions random, one time I had 5 in SC to Titan, another time had just 1.
Either way just RUN and SC - pointless spending time attacking them ....'s and losing HP.
 
My thought was to pop in, do 2m+ damage so I "qualify" if it does go down. My time to play will likely be limited again over the new few weeks. Need to decide where my "staging area" will be to attack Oya... might move the Carrier in, but I generally only do that if I'm going to operate exclusively in one area for an extended period.
 
Need to decide where my "staging area" will be to attack Oya... might move the Carrier in, but I generally only do that if I'm going to operate exclusively in one area for an extended period.
Check Lhou Mans for that. It has loads of ports, should have some orbitals in there.

As for when Oya goes down - probably, in ~two and a half weeks, or three. Depends on how busy people are clearing up its panic alerts and what it does next week.
 
Apologies - from the latest on the spreadsheet our side, the [XSF] Baiabozo Samples would be final buy order from the original lineup, with an auxiliary effort to sample for Lyncis Sector WU-P b5-0 underway to clean the last bit up.

Baiabozo needs approx 5K samples at time of writing.
 
Apologies - from the latest on the spreadsheet our side, the [XSF] Baiabozo Samples would be final buy order from the original lineup, with an auxiliary effort to sample for Lyncis Sector WU-P b5-0 underway to clean the last bit up.
No problem, it was really a PSA to let other Cmdrs know.
 
Referring to the M. Oya spreadsheet again, Carrier owners are reporting that all payloads are now complete, including the original six Control systems plus the two which will become Control—well done to everyone! Enough of the thirty Alerts were stopped also, that what appeared at first to be a two-week delay ought to be only a one-week delay.

If the Titan stops misbehaving, the next step is a Spire siege week at Cephei Sector XO-A b3. The ideal outcome is reaching 85% swiftly, then holding if possible while everything is delivered to give time to check that all systems become complete, then perhaps finishing the Spire site if so. Spare time to correct any unexpected shortfall is always nice to have!

Having tested those Control strengths personally (and twice!), I am very confident that it should work, and that any such shortfall would be caused almost certainly another unnecessary strength change.
 
Far as potential strength change, it was a concern for Medi0cr3 so, used my being awake at 1:30 servertime for once - 100(Spare, grabbed separately from carrier stock!) samples for WO-A b3 delivered directly after servers came up, with a request that pilots hold on spire activity until 08:00 servertime. Should be able to get a rough measurement for one system at least.
 
Last edited:
Wise! I had been using the slightly sparse regions of M. Thor as a perch from which to peek at high strengths via Leunii, Gluschen and nearby empty systems, and could do so again if anything seems wildly wrong. Clearance elsewhere should also give early indications over the next few days, if any change is such that all distances are affected.

With no immediate misbehaviour by T. Oya, its only apparent ways not to explode next week are if strengths change or if it decides it can get more Control systems immediately.
 
{ "timestamp":"2024-04-11T07:25:46Z", "event":"MarketSell", "MarketID":129021567, "Type":"thargoidscouttissuesample", "Type_Localised":"Thargoid Scout Tissue Sample", "Count":100, "SellPrice":1636, "TotalSale":163600, "AvgPricePaid":0 }
{ "timestamp":"2024-04-11T07:44:30Z", "event":"FSDJump", [...] "StarSystem":"Cephei Sector WO-A b3", [...] "WarProgress":0.000000,
{ "timestamp":"2024-04-11T08:32:18Z", "event":"FSDJump", [...] "StarSystem":"Cephei Sector WO-A b3", [...] "WarProgress":0.001725,

multiplied by 580 would lead to 1.0005 - so 58,000 samples approx... I take it there was a good chunk of spire activity regardless of the request so imprecise reading, but the number was not Higher than expected at least.
 
Last edited:
Spire activity you should be able to cancel out by taking a reading from any other system, as all the spire progress should otherwise be identical.

EDIT: reading 11 minutes ago on the spire itself was 0.0001 progress, so actual sample progress should be around 0.001625.
100/0.001625 = 61538
 
Last edited:
[...]

D) A general idea of how to use research limpets​

Best way to go about this is to drop near a star in the target system, let an interceptor spawn while moving 13-14km away, then letting scouts spawn, kill all but one marauder (or berserker), and then begin sampling activities on the remaining one.

[...]
Why Marauder or Berserker? I tried with Inciter and Regenerator and it works too.
 
Why Marauder or Berserker? I tried with Inciter and Regenerator and it works too.
Marauder and berserker flight patterns on average seemed to keep them closer to your ship, and more stable for you to get more samples back reliably - berserker in particular its special ability leaves it effectively sitting still, and not firing to boot - which for control system sampling where random scouts will attempt to drop in over time, can see it sitting still quite often.

Whereas the support scouts tended to zoom away more often - inciter in part due to its agility special ability. Less time lurking over 2km - less time unable to fire the limpet because out of range - slightly faster process overall.

In the end any scout will do, quality of life advisory.
 
Notably in a wing with regeneration, INIV does the entirely optional alternative of destroying Berserkers until we get a steady set of non-Berserkers. They move around of course, but there is always at least one within range, and the irksome missiles stop!

The specific observations and mechanism are quite interesting:
  • Arriving Scouts always prioritise variants which are missing, or are chosen randomly if priorities are equal.
  • Scouts always arrive in pairs.
  • Scouts stop arriving if at least four are present that way (interdiction Scouts are not counted).
Thus, the first four are always one of each variant. Destroying the Berserker causes a pair to arrive, which is always a replacement plus one random variant. Eventually that fifth Scout will be a non-Berserker, where destroying the replacement Berserker then leaves four others and nothing else arriving. Adapt as needed to remove an unwanted variant!
 
Status
Thread Closed: Not open for further replies.
Back
Top Bottom