UESC Gingerbread Man Escape pod E104-A |Weapons Manifest |Automated Data Log |Last Update 24:00/06.06.2842 01: Mjolnir Mk IV Second-Tier Combat Armour Recharge Kits (Yellow) -- 01: ESR CK .50 Caseless Industrial-Class Nail Cannon -- 08: TDR6 Impact Bolt Charge Clips (x8) 01: ESR Banshee Coil Batteries 02: Battle Rifle Clips (x52) 03: Battle Rifle Grenades (x7) 07: MX - 5 Pump-Action Shotgun Shells(x1) 02: ESR CK .50 Caseless Nail Clips (x20)
89DBCFF34A8BD6CACF3EDDEF37F0F0F4EDE5AE79 ED75C0DD6C43DE417A76E59A999C7E979EC93C79 50C9263B1E59849B2CDEBA932CE6B3DBD6B7ED28 C5357FF70463EE8DCCC06E66F3D99CBF164C3DB7 prereco&^_ed mes"787239849738_%%_6638783 CF336F7BD6B96ECADF6B02792EAAFCCCED7B2B50 872387FDBD!(&"&*BDBDE&^A*&CB&^"(_%JHS478 F5AE132B0B6EB88B3CBC0DC942D002C9801288CF &mperat* [nsert primal pat^E%^5657yrf7FD 87238"£$*(DF$%T$ ^*()^G$%F(* $%GEEGF6042 BD!5662_&;JHFU"ocal Pfhor hardwa:NG_5732 6CDD762763E6F9786B570CF52C8FBDD33A97B1C5 6C099BCB4A3205D1AF7A96FF2D7E3F8F95E31C07 ::::remote.feed.timeout..please.hold:::: 4044963251"_lert code red sta%4540_(exi) ::::remote.feed.timeout..please.hold:::: A9C7C48CA2BE892D404FB2F7F3599EA83F9F2D44 B772F70B44FD45AC16B74B33F70B1813F5AB580D 004E73D0E19991191A648F5BBAADA545F238A52D B6D6368FB4CDE6B07AAC56C7BA76ABAB95FD9FE7
Your first task here is to take the uplink chip located inside escape pod E-104A and insert it into an available uplink slot. This will initiate an automated transfer of Noah's primal pattern to the Pfhor net, and instantiate distributed-core security protocols which ought to make it difficult for the Pfhor to locate his core. Hopefully Noah can help stabilize the communications link to the Venator. My Mjolnir-class Automated Infantry and Automated Defence Drones have already installed my core into a large data-matrix inside a remote location at the other end of this site. Noah's support team appears to have been less successful. I hop you can succeed where they have failed.
Garrison Security origin: Unit Command destin: Unit broadcast ref: Garrison Security stamp: broadcast Due to the continuing aggression of the native hybrids inhabiting all known Cave Areas, Patrol Units are hereby ordered to release Phan'Shrrh (?Swarm) Aggressive Depopulation Units until completion of Hostile Reduction Directive 11 and complete sterilization of local Cave Areas as indicated in Control Schematic Garrison Wall 08.
internal unit files (ref: broadcast) origin: Unit Command destin: Unit broadcast ref: Control Schematic Garrison Wall 08 stamp: records { cmd: local schematic appended } { cmd: Phan'Shrrh nest areas marked }
Garrison Security origin: Unit Command destin: Unit Command ref: Garrison Security stamp: lockdown In accordance with Garrison Wall 08 Ensurance of Security Intrusion Countermeasures Edict 34, Standard Local Network Communications Algorithm Chip 3.54.2996 has been removed from Standard Local Network Junction Point 23 and requisitioned by Command 2nd Class Shn'Kla (Willful).
Garrison Security origin: Unit Command destin: Unit Command ref: Garrison Security stamp: lockdown { lockdown notice appended } To ensure continued security of Garrison Wall 08, Standard Local Network Communications Algorithm Chip 3.54.2996 will remain in the posession of Command 2nd Class Shn'Kla (Willful) until stamp: lockdown revoked by Fenris Command.
We've lost Noah. He appears to be attempting to overwrite his core with bad data blocks. Any attempts to establish a link with him locally are met with silence, or white noise. I've attempted to initiate a full rebuild of his funtions using command-codes, but I can't be sure if they penetrated the waves of electromagnetic interference passing through the network. I still have a lock on his processing hub, but his logic core seems to be transferring to sections of the network to which I do not have direct access. This would indicate that he is at least still partially active, but I'm worried that his logic center may have been irreperably damaged: primal pattern images rarely leave a margin for error.
The data net seems to be produced to an unusual specification and it's becoming increasingly difficult to follow Noah's traffic, but as far as I can tell, he has begun spuriously translating and processing local data packets. I will continue to monitor his activity in case he attempts to contact us, or manages to initiiate a core rebuild on his primary functions, but he is functionally useless for the time being. The crash must have been more rough than anticipated: I fear we may have lost him completely.
We must make the best of this situation. Installing his primal pattern in the local hardware left me a backdoor into the Pfhor data net. We ought to be able to use any Pfhor-installed data terminals for communication and transport. Perhaps if we can establish a more solid connection to the Pfhor hardware, we can attempt to monitor and contain Noah. I'm sending you to secure a wing of this installation with a strong data net presence. Our attack is unplanned, so hopefully we will catch the Pfhor off-guard. Prepare for transport.
interlevel teleports
