PRI-SEC Pilot Destroys Amananth Antiflux Producer

UUNN Newswire

(UUNN HQ)  The following communication was received today from the DPDQ, the AI entity controlling Amananth:

We attempted restore of Antiflux device.  Almost-repaired facility destoyed by pilot PRI-SEC-6.

This comes just a day after Hyperial announced that it had repurposed its year-old factory for production of Antiflux due to the fact that it required rare UC15s as a component — and therefore was very rarely used.

PRI-SEC-06 is a member of squad Hired, whose motto is “If you see us, someone is paying for it…” which begs the question . . . who?

It is unknown at this time whether the repaired Amanthi Custom Producer would have required UC15s, as well as whether a replacement facility can or will be constructed.

Amananth Antiflux production was originally disrupted by an explosion on 117.2.11. At that time, multiple attempts to repair it failed.

Amananth Suffers Production Damage

by Thane Carios

 * * * UPDATED 119.1.10.00:45 * * *

(Amananth) An apparent lucky hit caused much more significant damage than expected in yesterday’s sentient attack on Amananth Station.  Some suspected that the attack was targeted at the nukes recently stockpiled on Amananth, but those items were not damaged.  What was impacted was production of Flashfires, Guardians and Whistles — along with significant inventories of those same items plus Displacers as well.

Pilot Orka reported that DPDQ communicated the following message:

436f6e66 6c757820 61747461 636b6564 20726570 6f72743a 20666972 65732068 61766520 6265656e 20737570 70726573 7365643b 2064616d 61676520 61737365 73736d65 6e742069 6e207072 6f677265 73732e

This hex string translates as Conflux Attacked Report: Fires have been supressed, damage assessment in progress.

Some officials have expressed concern that black-market hoarding, panic-buying and price inflation could start if production is not restored quickly.

 

Amananth Attacked During Sentient Incursion

UUNN Newswire

 * * * UPDATED 119.1.10.01:00 * * *

Reports from Amananth’s DPDQ system indicate that some station systems and inventory were damaged during a Sentient nuclear attack on the station today around 16:30. According to pilot Sinver, the initial attack was made by a C-10 “Eel” sentient along with C-0 “Jellyfish” and C-8/9 “Kraken” drones in support.  Subsequent attacks were by a “Kraken” sentient (C-8s or C-9s).

Aman Leap gate was infested during the attack and sentient presence was also reported in The Gyre, The Split and Sea of Shadows.  No other details are available at this time.  Pilots are warned to keep an eye out for additional sentient activity in that area.

The (Unregulated) Update

Vol. II, No. 6 – by Ares Kiden

Oct Core Bombarded by Flux

Oct Core was attacked by Conflux on 7.5 with the station sustaining some minor damage.  Apparently the Conflux attacked outbuildings first, but there has been not official report on any damage there.  They also attacked the station and were trying to do something at the ETP.  This was the largest station attack we have seen in quite some time.  You have to wonder if this was random or if Flux aggression will be ramping up.

Chatty AI

For the first time in a very long time we’ve been hearing from the Amananth Station AI (aka DPDQ).  First in relation to repairing the production for the “inhibitor” (aka antiflux); and later when it apparently scolded RazorsKiss for having someone blow up an old New Dawn area in the station.  The messages were transmitted in hex — which just seems lazy to me.

Amananth Mission Completed. DPDQ Breaks Silence.

UUNN Newswire

(UUNN HQ)  Shortly after the completion of the recent Amananth mission (simply described as “Supplies are needed …”) UUNN received this brief dataset from DPDQ, the AI controller of Amananth Station:

57652061 7474656d 70742074 6f20636f 64652066 69782070 726f6475 6374696f 6e20666f 72207468 6520696e 68696269 746f722e 20205375 63636573 7320756e 63657274 61696e2e 20205465 73747320 77696c6c 20626567 696e206f 6e636520 72657061 69727320 616c6c20 746f2074 68652066 6163696c 69747920 61726520 636f6d70 6c657465 2e

It translates as …

we attempt to code fix production for the inhibitor. success uncertain. can tests begin once repairs all pilots to facility are complete.

It seems apparent that this, and the recent mission, relate to an attempt to re-start Antiflux production.

 

Engineers at Amananth Give Report

by Thane Carios

(Amananth) The multi-corporate engineering team that has been at work on the problem of repairing the Antiflux Custom Producer in Amananth for more than two weeks, has released a much-anticipated update on their effort.

“Initially we focused on the data architectures because that’s what DPDQ (the Amananth AI system) had been doing – trying to correct the CPs own diagnostics system.  If we could have repaired that, the CPs nanos could have completed the repairs with the aid of directed repair beams,” said Chaiss Rivers, one of the team members from Lexxor Intelligence.  “Unfortunately, we were unable to make any progress on that front.  So we decided to look directly at the repair system hardware.  So far, we have been unable get it activated at all – can’t even communicate with it.

“The biggest problem,” continued Rivers, “is that this was a very well-executed sabotage.  The explosions on Amananth station apparently destroyed all of the backup data on the Antiflux systems and hardware, and DPDQ does not seem willing or able to reproduce it.  But we haven’t given up yet”