Actions

Work Header

the thing about ash:

Summary:

A glitch (as defined by Wikipedia) is a short-lived fault in a system, such as a transient fault that corrects itself, making it difficult to troubleshoot.

In an article by Alex Pieschel, Pieschel writes that a "'glitch' suggests something more mysterious and unknowable inflicted by surprise inputs or stuff outside the realm of code."

(or: ash, as told in the very nature of himself and what makes him, him.

Notes:

(See the end of the work for notes.)

Work Text:

Here’s the thing about Ash: he's not exactly  from  anywhere. Not in the way Branzy is from EchoCraft or how Red is from Hypixel. Unlike them, he doesn't have a place he can call  his .

 

He's self-made, grasping at code until he's formed from a billion different things from a million different places.

 

(That’s the thing that differentiates him, he thinks. He can’t even relate to someone like Clown—or anyone who’s known for a thousand different things.)

 

It's...a little lonely, sometimes. The thing about being self-made is that you don't really have anyone around. There's only you, your code, and your stubbornness that's willing to burn your fingertips in order to prove yourself and go mad with power.

 

After a while, it does get exhausting. Going into your code, ripping it apart, and not leaving anything. If you do it enough times, you're left with nothing else to go around.

 

(You're suddenly reminded of Ouroboros when you think of that. Doomed to live, over and over again, with nothing but yourself to survive off of.)

 

(Except, in Ash’s case, he's been given a way out. An option to rely on something else, a friend, if you're being generous.)

 

(He doesn't decide.)

 

Ash is someone who shouldn't really exist. An anomaly, almost. A person who wasn’t even whitelisted but is still in front of you nonetheless. Standing there, ready to rule over the world, over and over again.

 

(And part of him doesn't want to let that go.)

 

Ash knows he shouldn’t really exist—I mean, what normal player wouldn’t struggle to even move without feeling his body fighting against it? A body fighting against code that’s barely stuck together. Code that’s off. Off and easily looked over, until it becomes apparent.

 

But by the very nature of a glitch, it isn’t something easily ironed out. It’s a factor caused by every single line of code, even if it’s just a section. It’s every single weakness, every single overlooked part, all codling together into a result that’s impossible to track. Impossible to even know where it even started.

 

And before you can even process it, it’s gone. Hiding away until it makes itself known.

 

(No matter what you do, it  will  make itself known again.)

 

(Ash lets it happen. Over and over again. A result of lines and lines of code, mashed together until it becomes impossible to miss. And even harder to chase down

 

It’s an inevitability, and Ash isn’t sure if he wants to let that go.)

Notes:

(as the tags said) dawg i have no idea about anything compsci but like. who am i to not add weird ass symbolism to everything i write and romanticize the mundane

but i hope you enjoyed! i had a lot of fun writing this, ashswag being from nowhere But being everywhere my beloved concept <3

and big shout out to the wikipedia article about glitches for carrying this entire thing. wikipedia editors are the goats!!!!