Voice testing; On decisions between future games

[perfectringofscars]

Now, now. Don't flake out on me, huh? You promised that when the others got settled, and you got this break, it'd be my turn.

Hey, you're the one that said it. And I'm not picky on places to end up, don't get me wrong. But uh...not sure about this user city you're thinking about. Too many problems, and I'm just one program.
But this glitched out other-Grid? Now that's just ridiculous. I'd go nuts in under a microcycle, just looking around at all that work undone.

You can do better. Come on, just let me do the choosing, and we'll get along just fine.
Now get me that list, and be quiet for a little bit.

Comments

[notglitching]

[...

...freeze.

Turn.
Stare.

That's. Just about all Rinzler's managing as a first reaction.]

[perfectringofscars]

[ Well, considering your doubles have reacted with vitriol, or a drawn disk, it's a pretty positive reaction. ]

Hey, man. Seems like you've been on your own for a while now, huh? Don't worry about it, we'll sort all this out.

[ Have a sub-audible [Enter command: Present disk] as well. ]

[notglitching]

[Rinzler: the most positive. All the time.

...or possibly the most wary. Or rigid. Or maybe just stalling out.

Visuals: match.
Render: match.
Signature: match.

It could be a trap. Or a lie. More user tricks, again. Rinzler doesn't know. And just maybe, he doesn't want to.

The command gets a reaction, though. Immediate. Mask dips, reach behind. And if his sound's harsher, louder, skipping out with just an edge more irregularity than usual... the program doesn't break protocol.]

[perfectringofscars]

Let's pop the hood, then. See what you've been up to.

[ At least someone is still making sense. Clu simply activates the viewing functions, and begins looking through what the slightly confusing chronometer relates as being time spent away.
Well. Looking, and making a quick copy of a few audio/visual files he finds pertinent.

Then? A heavy, indulgent sigh. ]

What a mess. I bet the whole world is just one contradiction compounded on top of another, isn't it?

[ Slowing down here, and there, then going back to replay two points in particular. Hmm. That operative coding ( specifically Tron's adaptive programming ) is cropping up more frequently. All these cycles, and he's still puzzling over how to get rid of it without damaging what makes Rinzler so effective in combat. ]

[notglitching]

[ 'Slightly confusing' is a severe understatement. For code as well as chronometer. Clu's own alterations may be dizzying in complexity, but they're familiar enough: structure applied and reinforced, lines of priority and command, filters and definition. The more subtle ties between the carefully sectioned layers: association, chained response, functions calling directives calling variables to redirect and enforce. But it's not all the same, and the wear's erratic, linked memory files flickering back up, commands doubling back on each other in mismatch. At least one line that's simply missing.

Rinzler's own response is substantially less telling. Head bowed, form hunched and still, hands half-open at his sides. The harsh skip and grind of conflict has quieted to its usual low rumble.

The question gets the faintest of shifts—not an answer at all, really. No need for him to answer. The disk should show enough. Contradictions everywhere in this world. Or worlds. Contradictions and errors and users and...

Cluuuu, come fix it. ]

[perfectringofscars]

[ For all that Clu is quite proud of his work on Rinzler, his personal enforcer is still a work in progress. A few things could be done better, code cleaned up a bit, but that was a whole other exercise that took precious time, and attention away from other projects.
Still, until a better solution is found, he will leave those mismatched lines of code alone for the moment. Rinzler is more useful with his new stored data intact.

For now.

Shifting to hold the disk in one hand, still horizontally, Clu does make a small adjustment to power conservation. Ambient absorption, or a handy ETC could have taken care of that problem neatly, but it's no big sacrifice to dial the setting back .004%. It would allow just a little extra leeway on holding a charge without shorting out. ]

Let's see...looks like you've gotten a little snarled up, my friend. Getting caught in those protocol loops must be a pain.

[ Another small adjustment, then, removing one restriction on a set of memories in favor of another. The shift lets the old Tron code fill in the gap momentarily before that segment of memory is rerouted back to root code. A simple voice, or the easier sub-audible command line should take care of it, after all. ]

What have you been up to, hmm? You're knotted up all over.

Rinzler; [ Enter command; system check ]

[ And looking between the disk, and the program it belongs to in order to see where the discrepancy lies in simple startup program physical, with your host Dr. Clu ]