Thisavrou Head Mods (
savmods) wrote in
thisavrou_log2018-02-10 04:46 pm
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
![[community profile]](https://www.dreamwidth.org/img/silk/identity/community.png)
Entry tags:
- *event,
- dceu: diana prince,
- destiny: cayde-6,
- dogs bullets & carnage: badou nails,
- dogs bullets & carnage: nill,
- generator rex: caesar salazar,
- mass effect: clone shepard,
- mcu: james buchanan barnes,
- mcu: wanda maximoff,
- mushishi: ginko,
- overwatch: lena oxton,
- roadies: kelly ann,
- star wars: rey,
- tron: alan bradley,
- tron: clu 2,
- tron: kevin flynn,
- tron: yori (crau),
- uncharted: nathan drake (crau),
- undertale: chara dreemurr,
- voltron ld: alfor,
- x-men movies: erik lehnsherr,
- x-men movies: kurt wagner,
- x-men movies: rogue
February Event Log I: Breathing Space
Who: Anyone and Everyone
When: February 10-19
Where: Avagi
What: Life support fails, and a team sets out. Check out this ooc post for more.
Warnings: Label your content.
[For questions, signups, or plotting, check out the ooc post. For the duration of this log, characters may travel between teams to whatever extent they are capable. The event will escalate with a second log on February 20.]
When: February 10-19
Where: Avagi
What: Life support fails, and a team sets out. Check out this ooc post for more.
Warnings: Label your content.
Synce their arrival, Avagi's residents have been plagued by minor system failures. Faulty taskbots and infested crawlspaces, supply shortages and the floods last month. For the most part, they've coped admirably, and quality of life aboard the station is substantially improved from what it was. But even as the damage in the lived-in space is scrubbed away, more dangerous poisons have been building underneath. On February 10, the groaning from the walls will escalate to a harsh scraping, audible station-wide. Then silence falls as the filtration systems die completely: leaving all vents to begin spewing thick, black smoke. |
System Failures | ||
(February 10-19) |
Acrid and hazardous, the cocktail of gases emerging from the vents are the result of three centuries' toxin storage spilling over. A shallow breath can cause a coughing fit, but individuals who draw in too much of the toxic air will find themselves becoming dizzy, passing out, or worse. While effects may vary based on individual biology, all beings who require breath will find their lungs burning and their vision blurred. An hour after the initial failure, the lighting goes out too. With it, all station power: to computers, doors, and any system not hooked up to its own supply.Investigation: Survival (Home Team): |
Travel (Away Team) | ||
(February 12-19) |
When Avagi's current population first got here, it was clear that others had inhabited the space before. Recent developments have even proven that these others—or, perhaps, their descendants—might still exist elsewhere on the station now. With the crystals that might repair your home missing, diplomacy is no longer an optional consideration. It's time to meet the neighbors, and hope they come in peace.Navigation: Survival: Discoveries: |
[For questions, signups, or plotting, check out the ooc post. For the duration of this log, characters may travel between teams to whatever extent they are capable. The event will escalate with a second log on February 20.]
no subject
None of which means he has much of an idea what to say.
Half a cycle back, saying wouldn't have been a consideration. Two cycles earlier, and he wouldn't have known he had a user at all. And a thousand cycles before that...
Rinzler doesn't know.
But it probably would have been easier.
He shakes his head to the question. Shifts slightly, offering his user space: along the wall, on a nearby crate, wherever he prefers to settle. The hall outside is dark and empty, no power from the generator's sparse supply wasted on lighting spaces while the users sleep. Rinzler stares down it anyway.
"...no threats observed."
no subject
“Good,” he murmurs. “I feel a lot safer with you keeping watch.”
That constant vigilance for attack may cause trouble at times, but even Alan can’t deny that it’s a valuable trait at others. That is, in part, what Alan wants to address. But more than that, Alan wants to clear the air. If things go south later on in their journey, well… Alan doesn’t want either of them harboring any unnecessary regrets.
“If it’s alright, I was hoping we could talk." He tries to keep his tone conversational. The last thing he wants to do is make Rinzler think he's here to scold him. "I know there are some things I haven’t understood very well with you and… I’d like to fix that.”
At the very least, he wants to make an effort.
Sorry for delay!
He won't let any threats get by.
Still, it's not entirely surprising that his user came for something different. 'Talk' matches readily to tags of censure and review, and it takes effort not to bow his head, frame shrinking in towards defaults. That doesn't match Alan-one's tone, though, or the conditionals that hover around the term. Shoulders set, a flicker of uneasy tension, but Rinzler only nods again in answer.
He's willing.
no worries!
“Well, we both know that things got rather... tense, after what happened with Anon. I’ll admit that I jumped to conclusions.” Alan lifts a hand to his neck, a small, contrite grimace on his face. “I was wrong. And I’m sorry.” He’s already apologized. That isn’t the reason he’s approached Rinzler now—at least, not all of it.
“But it seemed like you were upset for another reason, too. Another reason that I’m not as clear on.” He stifles a sigh of frustration. This could much too easily be taken as censure, especially by Rinzler. He opens his hands at his sides. “This isn’t a criticism or an order for you not to feel that way. I just want to understand why.”
Whatever Alan had done, it was enough for Rinzler to seemingly renounce Alan as his user and then refuse to accept repairs. Of course Alan wants to know what it was. And, perhaps, in light of what Rinzler has said, there’s another, more fragile question beneath the surface—the same question Alan had asked after he had first learned who Rinzler used to be: ’So am I still your user?’
no subject
And it's not the first time Alan-one flagged him a risk.
The enforcer ducks his head. Bows assent to the clarification: inquiry, not correction (if not any easier to respond). Alan-one is his programmer. His user—and to Rinzler, that value has never been in doubt.
His own value, slightly more so.
"...why did you write Tron?"
no subject
He’d said this wasn’t going to be a lecture and he intends to stick to that.
no subject
It's the expected response.
"How?"
no subject
’But we aren’t in ENCOM anymore,’ Alan stops himself from saying. If that’s a point he needs to make, then he’ll make it—after Rinzler has finished his own inquiry.
no subject
"...I'm not Tron."
Not his code. Not his function. Alan-one acknowledged it cycles ago (when Tron was still a distinct program to approve of). But there's another side to the fact too, and the enforcer's sound rises, harsh and defensive, as he continues.
"Told you what I'm for."
no subject
“I know you’re not Tron,” Alan says. And then, more reluctantly. “But maybe sometimes I forget that you don’t have his function. Or, I choose to forget it.”
Of course, Alan hates to think of Rinzler as belonging to Clu. Thus, it had always seemed better to him to think of the program’s ‘function’ as an obstacle to be circumvented rather than an integral part of who he is. And in the void that leaves, Tron’s function is the natural substitute.
Given Rinzler’s identity issues, Alan can see why that would be upsetting.
“After what happened with Anon, did you feel like I was treating you like I would Tron?”
no subject
"Tron does—what you want." The syllables stutter, shoulders shrugging close: in frustration or apology. Imprecise. "Meets standards."
Alan-one's standards. He was written that way.