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... )
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 demanded be placed in his code.
None of that really mattered right now though. He concentrated on sending energy to the other, quick and painless, and efficient. He wasn't lacking in energy at all it seemed. How or why was something the double would have to ask if he were interested.]
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.
The energy influx helps considerably. Rinzler's own scans are minimal, most nonessential functions reduced, but he notices the other's levels. It does interest him. Rinzler's found sufficient energy in this system to run, but between his high level of activity and the lack of a gridsuit to help contain and regulate, he's rarely been at full charge. He doesn't question, though, not now-just accepts the transfer, surplus energy sparking across damaged gaps, giving power for true function where the earlier recharge had just kept him running.
When his levels are more or less functional, Rinzler shifts slightly, gives his double a short nod-though he doesn't break contact himself. His noise ticks out evenly-another difference the other's scans might detect. For all his current state of injury, there's no damage causing the rumble. Nothing external at all. Just the faint skips of conflict, code grinding against code in an unbroken pattern. Not that Rinzler notices. Or cares, at the moment.]
Reply
Leave a comment