#idk if programmer was meant to be the creator of the software animating Symbol sticks or just an expert in it
Explore tagged Tumblr posts
Text
scene of programmer021 throwing together the code for the first TCOs: "what if i just give them 100% in all stats lmao."
releases one into a sandbox*
sandbox bricked irretrievably within 3 minutes
ho-ly shit.
..... that's hilarious.
they try like ten more times, each with the same outcome. the little worm is good at what it does, scary good, and programmer is grateful that they went the extra mile with the sandbox layer of protection from it.
at a safe distance, the TCOs are brilliant sparring partners.
*(basically a mini computer running inside of (but held separately from) another computer) (used to test new features without risking a whole system)
on the twelfth go, they've learned enough of its tricks to have more of a chance. both of them take a moment after a long scuffle to catch their breaths. the stick figure gasps on the floor - it's amazing! so lifelike! and programmer is celebrating this little victory for the field of recreational AI right up until
it looks at them.
TCO #12 turns its hollow face out through the screen, looking at them.
programmer is unsettled.
can it see them?
their webcam is off.
surely it's impossible?
right?
and yet, it seems to see them regardless, because not only does it react to their reaction (little twitches eerily realistic, how did their program know to do those things), it capitalizes on their shock. it springs to its feet while they're still open-mouthed and reaches the walls of the sandbox window (which programmer had been herding them away from at all costs), crashing against the side, rebounding, and hitting them again and again.
programmer flails to reconnect to their Cursor (you know when you forget where it is and have to wave it around before you can use it again? like that, but with even more panic, confusion, and imminent peril).
there are cracks in a multitude of funny colors forming at the edge of the sandbox instance. pieces of the window dent out of its normal bounding box. The Chosen One adapts instantly, focusing its hits toward the weak points.
WTF! this has gone way too far.
programmer's Cursor swoops around from out of nowhere and catches the TCO by the base of its head. it tries to breathe fire and only manages strangled puffs of smoke. its legs kick the air. where once it was so elegant and poised it twists and writhes-
programmer drops it.
they feel cold.
their Cursor retreats outside the walls of the sandbox PC, clicking into the main system's File Explorer. already open is the folder with this sandbox, its partition of storage, and setup files inside.
they click it. press Delete on their keyboard.
the TCO tries to stand. it pushes through a dizzy spell, one hand holding the spot under its head that must be its neck, and sprints toward the breach it was working on.
a confirmation pane appears, from the process responsible for running the sandbox.
its arms are strong, but the more TCO_12 struggles the more it's clear that this wall would need way more firepower and concerted effort... and time... to break. it's out of time. it realizes this.
are you sure you want to end this process? ALL data will be lost.
programmer sees when it loses hope, because it abandons the wall. it abandons the whole game: the pride and dignity it fought with, the play-pretend that it held any real power here. it turns outward again, toward the screen. small hands slam against the barrier between them, knock-knocking faster, faster, please please please, its legs shake and give out but it keeps knocking, on its knees, please please please please PLEASE
the sandbox is deleted.
the window that displayed it freezes, lighting up too-bright and desaturated.
a snapshot of the TCO is frozen in place, begging for...
begging for what? it was never meant to know anything. to want anything. how did it know there was anything outside its reality to want?
or was it simply afraid to die?
Windows catches up, and sweeps the frozen program away.
programmer021 is left alone with the spot where TCO_12 used to be.
their friends want to play with their latest stick figures. they were supposed to update today.
programmer numbly uploads the most recent release build they have. killer and BEAST were fun to work on. they'll warn everyone not to touch TCO until.... until programmer works out how to... until ever, and if one of them does, it'll be their own fault.
#--/ story#alan becker#animator vs animation#not cho specifically more the. concept of a TCO. like as a name for a species: so i won't tag their tags for this#programmer021#i remembered their number on the first try LOL. had to go back and check but it was correct xd#idr now what my original reasoning was but i had the idea for a while that TCOs might be easter eggs. or dev tools#accidentally left in the main Symbol creation system where any layman could boot one up and wow! time to buy a new cptr!#idk if programmer was meant to be the creator of the software animating Symbol sticks or just an expert in it#but the former was more interesting for my purposes#so that's where the ending came from#with a sprinkle of unreliable narrator for fun. whose fault is it again? the unsuspecting user or the coder?#executable!au#ava au
22 notes
·
View notes