Rinzler / Tron (
notglitching) wrote in
thisavrou_log2016-04-13 08:09 pm
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
![[community profile]](https://www.dreamwidth.org/img/silk/identity/community.png)
You can never say that I didn't try
Who: Rinzler and OPEN
When: April 14th through the 24th
Where: the Hold
What: Rinzler killed some people and copes poorly. Set after this log.
Warnings: references to character death and mindscrew, glowy injuries, unfortunate assumptions. (See also: Rinzler.)
The first place Rinzler woke up in this system was a cell. He'd been locked in after a fight with his duplicate—with Tron. Not that the enforcer had been capable then of even hearing the older version's name. Rinzler had attacked because he had to, because the overrides built in his mind detected conflict and demanded he delete the source. Since then, he's shattered that if/then chain. Chipped away at the filters on his memories, even managed, once or twice, to speak.
But he's back where he started, and he knows better than to expect things to end the same way.
For the most part, visitors will find Rinzler seated on the low bench back against the wall. Circuits burn dimly in the shadows, almost outshone by the dull glint of fractured code that covers a full half of the enforcer's core. He's turned slightly to conceal the injured side, but the spiderwebbing cracks through code and armor are obvious to see, and he doesn't have the power to refresh his shell and cover up the damage.
The low rattle of corrupted code echoes through the cell and down the corridor, though it does nothing to compete with the invectives from the user locked in one door down. Rinzler approaches shutdown just once, curled up against the wall, and if the flickering lights and twitch of limbs is any sign, it's anything but restful. The program won't notice anyone approaching then, but he probably wouldn't mind being woken.
Once or twice, Rinzler rises, pacing, frustration and the need to move boiling up through the despair. There's nowhere to go, though, nothing to do, and even that much risks opening his damage further. Maybe he should. Fracture, break, rip himself apart and leave them voxels on the floor to claim and punish. Rinzler wonders if he ever tried before. If he does, he can't remember. He wonders what they'll make him into. Alan-one had told him what would happen, told him he'd correct the fault if Rinzler fought again. Now two users are dead, and if there's any hope at all, it's that they'll decide he's too worthless to salvage.
[[ooc:the duration during which Rinzler can be visited depends largely on the results of his trial, so there may be some time-wobbling. In particular, if he ends up with solitary confinement... no longer applicable; Rinzler will be visitable for both the trial period and his sentence. ETA 2: As of the 20th, temperature conditions will be improved thanks to Vision + co.
Prose and spam both welcome!]]
When: April 14th through the 24th
Where: the Hold
What: Rinzler killed some people and copes poorly. Set after this log.
Warnings: references to character death and mindscrew, glowy injuries, unfortunate assumptions. (See also: Rinzler.)
The first place Rinzler woke up in this system was a cell. He'd been locked in after a fight with his duplicate—with Tron. Not that the enforcer had been capable then of even hearing the older version's name. Rinzler had attacked because he had to, because the overrides built in his mind detected conflict and demanded he delete the source. Since then, he's shattered that if/then chain. Chipped away at the filters on his memories, even managed, once or twice, to speak.
But he's back where he started, and he knows better than to expect things to end the same way.
For the most part, visitors will find Rinzler seated on the low bench back against the wall. Circuits burn dimly in the shadows, almost outshone by the dull glint of fractured code that covers a full half of the enforcer's core. He's turned slightly to conceal the injured side, but the spiderwebbing cracks through code and armor are obvious to see, and he doesn't have the power to refresh his shell and cover up the damage.
The low rattle of corrupted code echoes through the cell and down the corridor, though it does nothing to compete with the invectives from the user locked in one door down. Rinzler approaches shutdown just once, curled up against the wall, and if the flickering lights and twitch of limbs is any sign, it's anything but restful. The program won't notice anyone approaching then, but he probably wouldn't mind being woken.
Once or twice, Rinzler rises, pacing, frustration and the need to move boiling up through the despair. There's nowhere to go, though, nothing to do, and even that much risks opening his damage further. Maybe he should. Fracture, break, rip himself apart and leave them voxels on the floor to claim and punish. Rinzler wonders if he ever tried before. If he does, he can't remember. He wonders what they'll make him into. Alan-one had told him what would happen, told him he'd correct the fault if Rinzler fought again. Now two users are dead, and if there's any hope at all, it's that they'll decide he's too worthless to salvage.
[[ooc:
Prose and spam both welcome!]]
no subject
He steps into their line of sight and his eyes linger on the destruction still ailing his form.
"Do you--"
His lips press together, finding it difficult to voice his initial words when this unique being whose balance had tipped causing destruction in their wake was left in this state even after their sentence.
"-- Are you in pain?"
no subject
Still, if there's one thing Rinzler hates, it's not being able to feel people coming. He twitches audibly at the voice before his sound harshens, glass-edged irritation at his own reaction. There's slightly more control (if just as much tension) as Rinzler glances up... before the motion stalls with a blank stare.
That's not the question he'd expected. The program's helmet is still for several moments before it slants warily to the side. Question for question. (Even if the answer to its own was obvious.) Why does it want to know?
no subject
have an essay
It's this flaw, this gap in otherwise-neat coding that allowed for the rest. Repeated impact, again and again in a short span, as the user wielded Rinzler's own inactive blade to smash apart the wound. Core functions are half-shattered, split apart in shards, and if his code is making efforts to restabilize, Rinzler's had neither the power nor the time for the fractured lines to draw back together. Even that wouldn't fix everything. There's missing code, gaps of data that would need to be rewritten. Shattered voxels spread across the hall as Shepard slammed him back, long since faded into nothing.
For the program, his functions are his form. But that doesn't mean there's nothing else behind it. If Vision's awareness brushes past pure structure, he'll get a sense of something equally corrupted: a mind outlined by the snarl of restrictions and by something seething underneath. The struggle is tangible. Audible. It always has been: the ticking, rattling whir Rinzler produces every moment he's online.
Vision won't have long to analyze. As his mind brushes past Rinzler's own code-sense, there's a spike of sharp, frozen awareness. Encryptions slam up, blocking off the scan, and as damaged—and yes, in pain—as Rinzler is, he's on his feet in seconds. Fury joins the scrape of conflict, and the program's noise snarls out in a low growl, fists curling as he glares at Vision through his mask.
Stay out of his code.
1/2 AI's what a bunch of ramblers
His eyes suddenly open and the small mechanics behind them whirl as he takes in the room and the agitated state of the program.
2/2
He gestures to him. "You are damaged."
no subject
If he were less on edge, its conclusion would be laughable. As things stand, the black mask only twitches sharply, mute rejoinder. Yes, he's damaged. So what?
no subject
no subject
no subject
"But, you're in pain."
no subject
No edits.
no subject
This being who had killed without a qualm yet fought to stay alive, and even now struggled to keep operating was --
"You are... afraid."
no subject
Rinzler doesn't disagree.
no subject
"Changing your program would destroy who you are.... at this moment. It would kill you." He looks at him. "You were not sentenced to death. It would break their laws to edit you. But you-- " His lips press together as his face falls and worry sweeps across his features. "You need help - power possibly - to keep functioning. It is immoral to keep you here like this. Injured."
no subject
Still, he can't quite stop the flicker of derision at the lines that follow. Their laws? No. Rinzler shakes his head, turning to pace (albeit slowly) back toward the low shelf. User laws are meant for users, and certainly there's no restriction against improving a tool. Or going however far they needed to correct for its malfunctions. Even if Alan-one hadn't told him outright what was coming, Rinzler wouldn't expect any other outcome now.
He sits back down, noise resuming its dull rumble as the enforcer's shoulders draw inwards in a shrug. So long as it stays out of his code, the other can apply whatever morality it chooses. Nothing will change, and Rinzler's been through worse before.
no subject
"I will try to appropriate some changes for your stay here." He tells his as he steps back to head out.
no subject