»: Nibwaakaawin

[Zephyranthes]

INVALID_ID_LOGON_0000X1A.000
(ADDRESS 0x000000AA)
(ADDRESS 0x000000A3)
(ADDRESS 0x00000011)
(ADDRESS 0x00000012)
(ADDRESS 0x000000CB)
(ADDRESS 0x000000A0)

LOCATION: LENIEX
ID: "NIBWAAKAAWIN"
SUBJECT: RE: HELP

Harper seems to have held down the fort well enough. Other tasks kept me away from business. You understand.

We aren't able to berth your cruisers at this time due to ongoing usage of the remaining drydock, that much is true. However, we can provide a refuge away from prying eyes for manual repairs and refitting with drones, EVA teams, and runabouts. Would take a long time, but you've waited this long to get these ships firing again. I'm sure it won't kill you to wait longer.

Regarding what's needed at home... plenty of structural damage. One shattered biodome, two offline. Two drydocks completely out of commission. Several external modules have broken off from controlled detonations and been battered around by debris and incidental collisions. Two towers, one being the ATC, are just completely gone. And internally, nearly every significant computer system, from life support to the classified archives, is either damaged beyond use or recognition, or locked down tight enough that trying to brute force an unlock might damage the very thing we're trying to get. Essentially, we're operating at the bare minimum of habitation, running off a mixture of backup generators and infrequent supply runs to get by. She's not what she used to be, not by a long shot. For the longest time, I only used the station to inter the fallen. The ghosts are noisier than the machines that once ran everything.

I'll send over more detailed telemetry and data with a more secure method, a datarunner. The damage to our comm arrays and the corruption of software aboard here means I'm not inclined to risk interception of sensitive information. You understand.

We'll be in touch, yeah?

CONNECTION LOST