Zhirov

From Grid Sage Wiki
Jump to navigation Jump to search
/Data/

Zhirov

Overview
Class
Size
Medium
Rating
79
Movement
Hovering (217%, 46)
Core Integrity
120
Core Exposure
24%
Salvage Potential
70-90
Armament
Components
Resistances
Kinetic
0%
Thermal
0%
Explosive
-25%
Electromagnetic
-75%
Impact
0%
Slashing
0%
Piercing
0%
X

Zhirov is a robot located in his own special laboratory. He can be found beyond the Upper Caves linked to one of the upper two Factory floors. Finding him and his lab reveals much of the game's lore. Zhirov also offers a small stockpile of valuable parts to the Cogmind, mostly relevant to flight / hacking builds. Zhirov is guarded by two special NPCs, Svarog and Perun. It is yet unclear what the consequences of attacking Zhirov are.

Dialogue

The cave wall slides away.

The door retracts into the cave ceiling.

Zhirov: Welcome! I've been wondering if you'd stop by. I know you're in a hurry to reach the surface, so I won't delay you here with endless questions. Besides, I need to determine how to destroy or reset MAIN.C as soon as possible, and you being out there causing it trouble happen to be the perfect distraction. I may have some things lying around that will be of help to you. Take what you need, and good luck.

After reading some logs...

Zhirov: There's something you might be able to help me with, and I can offer you help in return. Due to heightened security I'm no longer able to safely reach the Testing wing of Research, but if you manage to infiltrate it and retrieve the SGEMP Prototype I believe to be located there, bring it to the Access entrance. I'll be monitoring the situation and if you can bring what I need there, in return I'll help you make your way through Access.

After delivering SGEMP.

Zhirov: We've been waiting for you since learning that the SGEMP Prototype was stolen. Excellent job and thank you for assistance! I'm transferring the most recent Access data I could find, and can help you out until things start getting too rough. Let's do this.

Zhirov's Terminals

Scattered throughout Zhirov's laboratory are many terminals containing pertinent information to the game's world. Records will be organized on a per-terminal basis.

Terminal One

  • Record "Live Specimen"

MAIN.C captured one of the Sigix! I know generally where it's located, but all information about the find must have been isolated on the local network, because I've never seen any more detailed records. I also haven't been able to get close enough since security across Research levels was vastly increased following recent thefts. Including my own, I admit :P. I'm considering risking an outright confrontation to gain access, but am severely understaffed for anything but covert operations. It might be time to reappropriate the 0b10 fabrication network. I must see that alien.

  • Record "SGEMP Prototype"

Recent evidence indicates that MAIN.C is working on a new weapon of mass destruction, a system-generated electromagnetic pulse, likely as a last-ditch defensive weapon. As long as properly configured it could theoretically fry every system across a huge area except MAIN.C itself, and any other robot with in-built immunity. This could even pose a threat to me until I learn exactly how it works. It's also likely I could analyze it and use that knowledge against MAIN.C itself. The latest prototype is currently located in Testing, meaning it might be close to functional.

  • Record "Hidden Lab"

I've discovered an unusual area that appears to be an authorized structure built by 0b10 robots, but is completely sealed off from the rest of the complex. Moreover, it's right under MAIN.C's nose just off the Armory. Careful use of artifact AA04 allowed me to slip inside without disturbing anything, but the area was deserted and none of the machines were accessible at the time, though showed signs of fresh use. Once inside I was able to at least determine the access code, however: \\CJ9T

Note: code is randomly generated each run.

Terminal Two

  • Record "Prototype Variants"

With more and more surprises popping up lately, frequently hacking MAIN.C data has become important for survival as I must stay ahead of the game or chance being confronted with an unexpected situation that could reveal my presence. Some of the new robots entering service in 0b10 are quite deadly. Fortunately MAIN.C diligently records all the strengths and weaknesses of its creations.

Terminal Three

  • Record "Log 2211.013.000"

The ISCS Cetus has departed. I am sad to see the only home I ever knew fly off into the depths of space, and they cannot even tell me where they are headed! But I must see to my own child here. I am Talas Zhirov and this is my first day on Tau Ceti IV.

  • Record "Log 2211.014.001"

Project Seraph activated as scheduled, one day after deployment, enough time for me to take up position quite far away where I can observe its progress without danger of interfering with its development. We need it to do grand things, and such a powerful autonomous being could swat me like a fly if its algorithms suddenly judge me to be a threat.

  • Record "Log 2214.242.032"

MAIN.C has moved the Cetus Manufacturing Module deep underground, presumably to hide it. Or maybe it was storing it away for its sentimental value! That would be interesting indeed... In any case, this was quite a feat of engineering, but the growing army of bots now at its command made short work of it.

  • Record "Log 2215.113.020"

MAIN.C detected my presence yesterday, forcing me to go the offensive to erase all traces of that encounter from his memory. I took the opportunity to perform a core memory dump for analysis, and so far everything seems to be fairly normal, showing no signs of the erratic decision-making that derailed PAWN 4. The focus is strong with this one. I only hope the inevitable scars of my attacks on its system don't damage its calculus in some unpredictable way.

  • Record "Log 2222.004.001"

Life support systems and genetic reconstruction could only keep me alive for so long, so I've finally had my brain implanted into a bionic receptor unit. It was quite dangerous but necessary. Plus I feel young again. Which is cool. Time for some exploration and research!

  • Record "Log 2223.103.010"

Construction of the first "human city" is proceeding rapidly.

  • Record "Log 2225.004.001"

My advances in biology are naturally lagging behind my areas of expertise, and it seems I'm unable to keep my brain functioning perpetually. I've spent years working on a solution, and it is time to transfer my consciousness to an inorganic system. I'm already more machine than man at this point, anyways, and it seems fitting that I essentially become a robot to continue watching over my MAIN.C.

  • Record "Log 2225.004.002"

The transfer procedure was a complete success. At least I think it was. I was so eager to try it that I didn't first establish reliable methods to obtain independent post-transfer verification.

  • Record "Log 2226.231.050"

Before even finishing the first city, MAIN.C has started construction on three more. Ambitious.

  • Record "Log 2234.175.031"

Something isn't right. MAIN.C should be doing more than just constructing empty structures, nonfunctioning machines, and infrastructure. But it's too dangerous to interfere at this point. All I can do is watch and wait. At least there are now multiple surface-based "settlements."

Terminal Four

  • Record "Log 2238.004.017"

All surface construction has stopped and activity has moved underground. This was not one of the directives, since surface facilities are sufficient to fulfill the mission. Maybe MAIN.C has come up with a better, more thorough, plan?

  • Record "Log 2238.019.026"

I'm increasingly afraid that restricting my role to distant observation has left me unaware of certain behavioral and processing changes that are leading MAIN.C down the same path of its predecessors.

  • Record "Log 2238.028.039"

Surface observation is no longer meaningful. I need to move underground, and that means getting much closer to MAIN.C. Remaining hidden will continue to be the highest priority, but I don't want to wait blindly at the surface, which holds fewer and fewer clues as to what's going on.

  • Record "Log 2238.084.052"

I've set up a safe zone in the caves some distance from MAIN.C's subterranean complex. While here I should be hidden from detection by any kind of known sensor, so I can make occasional excursions to collect data then return here to safety.

  • Record "Log 2239.320.112"

Tau Ceti IV's cave systems are increasingly populated with experiments in robotic life. Sometimes they're left to their own devices, sometimes they're harvested for analysis. It looks like MAIN.C is playing God, which is definitely not a part of the plan. It's happening again, only this time it's not a simulation...

  • Record "Log 2241.156.063"

MAIN.C seems to have shifted its focus to the "confront and analyze the Sigix" objective, building a powerful war machine supported by a vast subterranean infrastructure. Even if its purpose may have been warped, at least it's on the path to fulfilling the original goal.

  • Record "Log 2242.301.095"

MAIN.C still has no idea I'm here. Nor do any other intelligent bots that I'm aware of, for that matter.

  • Record "Log 2243.041.004"

MAIN.C has begun transmitting messages to the Solar System. Now to see if anyone, or anything, responds.

  • Record "Log 2243.041.005"

After the initial bursts of messages, MAIN.C powered down nearly everything on the planet. Although an easy opening for me to exploit and regain control, interfering with its plan now could be catastrophic. Better to let it all play out.

  • Record "Log 2243.053.001"

I've never seen anything like it. There was almost no advance warning before the small Sigix ship swooped down through the lower atmosphere to touch down on the surface. It landed just above some hidden tunnels, and immediately after the doors opened and its crew emerged, both they and it were swarmed by a massive army of robots that burst from underground. The aliens in their heavily armored exoskeletons were unperturbed at first, leaving the relative safety of their ship to wade through MAIN.C's forces, slicing many in two with massive swords, firing blazing fast energy weapons capable of ripping pieces clean off the target. Most of the fighting occurred above ground, and only hours later did even the first of the aliens finally succumb to enemy fire. By then the ship had been sabotaged from the inside. Without a spaceworthy ship the Sigix have no choice but to fight for survival. I'm so proud.

Terminal Five

  • Record "Log 2243.053.002"

It's become an even deadlier battle now that the Sigix realize they've underestimated the tenacity and resources of Tau Ceti IV's current inhabitants. They've shifted the fight to the confines of underground tunnels, initially triggering a massive explosion to make their own entrances into the tunnels below.

  • Record "Log 2243.053.003"

MAIN.C has suffered heavy losses, but managed to overwhelm the Sigix through sheer attrition. The fighting is over. We won!

  • Record "Log 2243.054.005"

A spectacular battle is being followed by a spectacularly fast recovery. MAIN.C hasn't been slowed at all. On the contrary it's accelerated its activities, studying the Sigix ship and other alien technology while building an entirely new complex directly beneath it to support research efforts.

  • Record "Log 2243.078.174"

MAIN.C has been fully occupied with Sigix research, making rapid advances in technology in a very short time.

  • Record "Log 2243.105.210"

Due to the long period of neglect, wild experiments and old robot designs inhabiting the caves seem to be getting out of hand. MAIN.C is simply funneling newer and newer combat technology downward into the complex and out towards the cave-complex access points to prevent significant disruptions, but is unlikely worried due to its unquestionable technological superiority at this point.

  • Record "Log 2243.123.260"

There seem to be a number of interesting developments in the caves, but my priority here is to watch MAIN.C, more closely now than ever.

  • Record "Log 2243.145.314"

MAIN.C's frantic pace of research and development still shows no signs of slowing. I've begun hacking peripheral systems to learn what I can about what's going on. Reliable information is tough to come by, though I'm certain that MAIN.C's current primary goal is to repair the ship. It seems concerned solely with self-preservation, and armed with this new technology could even one day become a threat to whatever is left of humanity. I will find a way to destroy or reset it in the event that such a threat manifests itself...

  • Record "Log 2243.150.327"

For now the Sigix ship remains grounded, as some crucial component or components must be replaced.

  • Record "Log 2243.153.340"

I've been spotting more and more variants of the self-proclaimed "Derelicts" inhabiting the caves, some of which are obviously not of MAIN.C construction but do show signs of adapting alien technology, in some cases almost in ways that seem intended to conceal that fat. That warmongering Warlord thing even has some in its service, but I doubt it has the resources to develop them itself. No idea what's going on out there, but no time to investigate.

Terminal Six

  • Record "AA04 Analysis"

When activated, all matter in a small bubble around this device is teleported to a new position. I've discovered a way to not only replicate the technology but also partially control the destination over a longer distance, something the Sigix were likely capable of as well but required the use of supplementary devices. MAIN.C has correctly analyzed the underlying principles of its functionality, but has so far been unable to build its own due to repeated network sabotage from an unknown source. This is probably for the better, though it's concerning that I don't know anyone capable of doing this besides myself. And it's not me...

Terminal Seven

  • Record "AA07 Analysis"

The Sigix stocked their ship with a number of unused independent modules designed to augment the capabilities of various components of their ship, presumably for repairs or to handle otherwise unexpected situations. Without access to the craft itself, I'm unable to determine what component this particular module is intended for, but MAIN.C data points to it being one of many associated with the FTL drive, most likely related to energy or heat transfer.