Conflict://003 - [text; encrypted; hackable] - Backdated to the morning of 1/10
[FILTERED to: Laura Kinney]
[The message is short. Specific. Directed to just one number, with encryptions applied to prevent outsiders from listening in.
But anyone with skill and interest in watching the network? Will notice something. This encryption is weak. Obvious errors, obvious flaws, that make it simple enough to crack, despite the ( Read more... )
[The message is short. Specific. Directed to just one number, with encryptions applied to prevent outsiders from listening in.
But anyone with skill and interest in watching the network? Will notice something. This encryption is weak. Obvious errors, obvious flaws, that make it simple enough to crack, despite the ( Read more... )
Encryption failed, message easily accessible.
This reply encrypted probably.
Request: status.
[...]
Additional request: location?
Reply
Doesn't matter.
There's a fairly long pause before a response comes. Uncertainty or effort, take your pick.]
Status: damaged.
Left arm derezzed, code instability across left side. Minor damage: torso, facial render.
Energy levels critical.
[No response to the location query. Yet.]
Reply
But first more intel fishing.]
Acknowledged.
Query: capable of self repair? To what extent?
Reply
Rewrite is not. Rinzler just. Stares for a moment. (Yes, at the audio feed.) He's not a recompiler. He's not an admin. And whatever additional permissions Clu granted this copy, if he's capable of that...
Rinzler just. Doesn't know anymore.]
Not a function.
Disk access restricted: Clu.
Reply
Not permissions from CLU. Vague self-repair functions from original Tron coding. Nothing extensive.
However, he has picked up a few things from Flynn.
Least to say though he can't actually write that sort of code on his own. But at this point? Rinzler is Rinzler's best option for a crude patch.]
Understood.
Extensive damage. No admin present.
Offer: energy exchange.
[That's something he can do easily.]
Reply
Acceptable. [Location ping.]
User in transit to transport stored reserves. Ally.
[He has no real idea which will arrive first, or if they'll even be within the same timeframe. But probably worth warning.]
Reply
[Rinzler doesn't waste his time picking up any extra energy; he has plenty in reserve with the way he's been operating lately. He heads straight for the location ping and doesn't stop till he sees the state of his double upon arrival.]
Reply
Which isn't to say he's gone far. The program's sitting on the flat black ground, leaned against one of the scattered cars that fill the rooftop parking lot. A short distance to the left, Soundwave's shell is easily visible, dark and dead, a multitude of coils still grasping out at the space beyond. Disks are docked, phone resting on the pavement to the right. At his copy's approach, Rinzler looks up, rumble ticking out evenly.
Though his user clothes cover a great deal, it's not hard to miss the absence from half of his left shoulder down the sleeve. A few voxels glint red-orange on the ground nearby-the damage might not have cascaded to derezz, but it's by no means stable. Which damage is again, another question-small puncture marks are visible across his shirt where ( ... )
Reply
Though not without noting the shell of a form laying dead and lifeless off to the side. Not before noting the design and make of it, of noting that he recognized that mech. 'Interesting' wasn't quite the word for it...
He approached his double with no outward sign of caution though that was a bit belying of his true self. But right now there was no need for the obvious. And he didn't think he needed it around his double anyway. Not yet anyhow.
He knelt down next to his double, eying carefully but being sure not to reach out and touch.]
Reply
He doesn't react much as the other closes the gap. A minimal sideways shift, head angling in question as his copy settles near. Rinzler's more or less relaxed, noise an even whir. Whether Rinzler trusts his copy or simply thinks he knows him, there's not much point in tension or aggression. He's in no shape for a fight.
What little circuitry can be seen stays at a dim burn as he looks up, blue-grey stare meeting the other's red-orange one. Well?]
Reply
The flow of energy was smooth and calm. For a moment the security programs were linked, and in the process Rinzler took in as much data as he could about the other. Mostly his scans confirmed the amount of damage the other was suffering. He could feel every nick and scrap, and drain and leak and break of circuitry and the flow of energy the other had. Not only was he low on energy but Rinzler could tell his double had serious energy flow problems due to all the damage. It hindered everything to some extent.
For his own part, Rinzler was completely functional (other than what Abax wouldn't allow) and his energy flows were as smooth as possible. All previous damage was patched. Even his rumble wasn't a byproduct of damage anymore--that, too, had been fixed. What had replaced it was a function that Rinzler had ( ... )
Reply
The damage is substantial. The smaller cuts and punctures don't go deep, but the instability does. Spreading out from the jagged break through his shoulder, even worse where he'd impacted-landed-on his side. Voxels fractured, misaligned and fragile, code barely holding together. It's no true injury, nothing his systems can't passively realign with time. But right now? Rinzler's one blow in the right place away from damage cascade and derezz ( ... )
Reply
Leave a comment