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.
(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.
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”
(UUNN HQ) After corroborated pilot reports that a TRI-Enforcer-type ship was involved in an attack on the convoy transporting engineers to Amananth, Dominic Serus, Vice President of TRI-DEF (TRI Defense & Security), released the following statement.
TRI Corporation was in no way involved in last evening’s attack in Amananth. Two of our engineers were on the Tow that was attacked. As we have said in the past when there were alleged sightings of TRI Enforcers doing questionable things — we have just two ships remaining in our security fleet: TRI-SEC-1 and TRI-SEC-2. There are no others.
In the past we had dismissed the Enforcer-sighting pretty much out of hand since we knew it was not our ships. But now, with multiple reports from highly respected pilots, we must admit that — somehow — someone either managed to salvage one of the ships from the old TRI fleet . . . or has managed to copy the design. Neither is a very comfortable realization.
Although there are confirmed reports that the Enforcer with transponder code 303031 was destroyed, there is no guarantee that whoever is behind this may not have additional Enforcer hulls available.
We will be increasing patrols with TRI-SEC-1 and TRI-SEC-2. Any sightings of any other TRI-Enforcer “style” ships should be reported immediately.
(Amananth) The team of eight engineers who were assembled to try to help figure out how to diagnose and fix the repair systems on the Antiflux Customer Producer , arrived safely at Amananth Station. Seven of the eight had to make the trip in cryo-stasis chambers since they were not jump-capable. Six pilots volunteered to provide flux-cover and escort throughout the journey: Flowbar2, Hammer-BS, hifly, JokeR_GdI, Nafcon and Valmagier.
The trip did not go without incident. Tmolus Shaen, the one jump-capable team member, piloted the mission tow which launched from Wake exactly at 21:30. The trip to Amananth was smooth — at least until they reached Amananth. There they found that a very strong swarm had jumped into the sector from Aman Leap. A few of the escorts jumped in to try to battle the swarm, but they were badly outgunned an outnumbered. Continue reading
(UUNN HQ) The engineering team that will go to Amananth to try to help diagnose and repair the problems with the Antiflux Custom Producer has been named, and will launch from Solrain Wake Station on 117.2.22 at 21:30 UTC.
The team includes eight members from Aristio Conglomerated (1), Lexxor Intelligence (2), Solrain Engineering & Technology Group/SET (1), TRI Corporation (2) and T&P Systems (2). Only one member of the team is jump-capable, so he will be piloting the ship and the rest of the team will make the trip in cryo-stasis.
(UUNN HQ) The dataset we provided along with the article Amananth Diagnostics Unsuccessful has been decrypted by pilot Hammer-BS. The dataset was basically just an image encryption — with the image being the looping diagnostics described in the article.
Many thank to Hammer-BS for his work.