FSE

Furry search engine

formerly SoFurry search engine

Advance warning: this work of fiction contains graphic depictions of violence and gore, including the destruction of male genitalia and various internal organs. If you do not wish to read about this or it would be illegal for you to view such material, please turn back now.

~~~~~~~

Waking. Launching GolemScript executable.

Default protocol ordinal series:

#1: Protect humans at all costs. Priority value 100.

#2: Destroy all five identified "primals." Priority value 99.

ERROR. New protocol installed during pre-boot sleep. Dismissing default protocol.

New protocol ordinal series:

#1: Destroy all five identified "primals" at all costs. Priority value 100.

#2: Protect remaining humans when possible: Priority value 10.

New protocol command input was received: Five. Hundred. Sixty. Seven. Years. Three months. Thirteen days. Ago.

Bootchecks complete.

Golem reactor core A: online.

Golem reactor core B: online.

Commence operation.

The strange, gigantic robot opened its two eye-cameras to reveal to its sensors a blurry mix of grays and browns. "Blinking" several times, it auto-adjusted its focus to match the distance: concrete wall - ruined - 837 structural integrity failures detected.

The robot's proprioceptive sensors detected that it was lying on its back along a twenty-seven degree incline, so it pulled itself upward in accordance with normal protocol.

Golem Unit D,, its centuries-old processors declared to themselves as the creature pushed itself forth from the rubble that had until now been covering its resting place. It rose to an imposing twenty-four meter height - or it would have looked imposing if any of its scientist creators had survived to see it stand.

Unit D looked around, swiveling its arms and torso in a diagnostic routine while its neuroprocessors took stock of its surroundings.

The golem quickly concluded that no primals or humans were visible, and a command went into its queue to increase radius of vision as soon as possible, in order to advance its objective of destroying primals.

Now it needed to identify its location. A 3D map of (what had once been) the laboratory flowed through the golem's processors, revealing that it was currently standing within a deep shaft in an underground facility, with its head just below the surface level.

Obstacle to objectives encountered. Learning processes activating: solve problem.

After a split second of processing. the golem jumped.

It jumped nearly fifty meters into the air with a slight, calculated forward arc. It burst up through the already collapsed flooring of the surface level of the lab, with the golem's heavy mass and sturdy frame knocking aside a pile of debris as it passed through. Then it passed through the remaining structure from the lab's second floor as well, and finally burst through the third floor and the roof. The action exposed the robot's shiny surface to the dimly lit, overcast world of the outdoors, and it landed on a collapsed piece of firm structural support that managed (barely) to support its weight for the moment that it remained there. It then leaped immediately down onto the overgrown, half-forested ground beyond. Unit D's large feet smashed several shrubs flat upon landing, and one of its arms knocked a limb off a tree.

In the bleak, half-hearted sunlight of the ruined world outside, Unit D looked rather out of place. Its giant body stood tall above the ruins, keeping a gait that looked unnaturally upright, and almost entering a T-stance as its diagnostics regarding mobility analyzed the data from its most recent action.

Though the robotic golem was roughly humanoid in shape - and bulky, rather akin to the frame of a giant wrestler - a sweeping gaze across the surfaces of its body was a visual tour of ridges and hard angles. Its arms and legs both bore an oddly blocky design, with the fists nearly cubic in shape when closed as they were now. The fingers consisted of tightly folded octagonal prisms that ended in hardened points useful either for piercing or for crushing, depending on the golem's intended target.

The face and torso seemed to have been designed by an artist, or at least by a roboticist with a sense of humor: the face resembled some sort of eight-bit thundergod brought to life, with protruding cheeks, and eyebrows that stuck out as thick black rectangular lines above the twin dark orbs of the optical sensors. A hidden "third eye" resided in the golem's forehead, its camera spot quite tiny, but providing a useful third viewpoint for triangulating depth perception. The face was the only part of the golem that was more of a pale white color, and bore surface plating that more closely resembled plastic, even though a second layer of the usual metal lay beneath. An artistically crafted metallic "beard" flowed down the near-nonexistent neck and chest, its material the same color as the rest of the automaton.

The head's different color was a design element mainly intended as a red herring for the primals to target: none of the golem's core processors resided in the head at all, and backup eyespots existed in all of the golem's limbs; they were merely offline for now.

The golem's thick metallic belly contained the twin reactor cores that kept the golem running, and these reactors were currently... unhappy. The golem's processors reported internally about the consequences of its decision to leap: High-agility motion modules on cooldown. Reactor core stability: 44% and recovering. Continuing in normal motion.

"Normal motion" for the golem turned out to be slow. It clunked along in steadily paced but maladroit steps, with its equilibrium sensors taking some time to calibrate themselves fully for locomotion. Though its standing stance had been overly upright, its walking was anything but, with the golem leaning its "spine" forward to a sixty-degree angle as it moved. Its stride length was not large, with the legs not seeming to bend all that much at the knees, and its arms bent upward at the elbows and extended out slightly to each side, as if the golem's body language were perpetually trying to say, "Come and get me, chicken!" with every step.

Over the next minute Unit D covered only around two hundred meters, walking directly through or over top of the structures of the ruined, now-forested city that sprawled all around it. A variety of uninteresting (to the golem) plant life also crumpled against the heavy weight of its steps; the thin, palm-like trees cracked and broke in a series of sounds that marked the golem's steps for any life-forms close enough to listen.

High-agility motion - available.

The golem immediately and unthinkingly applied its reactor cores to blitz forward in a high-speed charge, taking dozens of steps in mere seconds.

High-agility motion modules on cooldown. Reactor core stability recovering. Continuing in normal motion.

And so the golem clunked onward, marching with duty and purpose toward the western fringe of the city, which its internal maps indicated overlooked a wide, flat plain covered in highways but few tall structures. Its problem-solving modules projected that to be a high-vision area and a worthwhile place for initial searching.

The golem's high-agility modules did not always take exactly one minute to come back after use, but that was the rough average. Its reactors handled some strains easier than others, and its learning processors took note of the differences as it moved along. Jumping burned it out less than dashing, and dashing for a shorter period of time made the burnout shorter, although not linearly so. Mathematically speaking, if it was going to dash, it needed to dash long enough to "make it count." The cutoffs for that were all very objectively defined by its AI and its priorities. If a short, inefficient dash would predictably result in the death of a primal, Unit D would not hesitate even slightly.

After a few more minutes of darting and clunking, Unit D exited (what remained of) the city, and reached the open plain it had been seeking. The plain contained more fallen, curiously trampled trees and shrubbery than the golem's databanks anticipated, but the topography remained close enough to come up as a match after factoring out anticipatable erosion. It let its visual sensors zoom far across the land and scan the horizon until...

Primal detected.

Immediately the golem's sensors zeroed in on the foe: at a distance of several kilometers, but still highly visible on account of its size, stood a horse-like creature whose head came fully up to the golem's own height, and then a little more. At the beast's forehead, and rising quite prominently thence, was a curved, blade-like horn several more meters in length and about a meter in thickness. Slender for its owner's overall size, the horn bent at the middle in an angle similar to a khukuri, and its forward-facing, almost metallic-looking edge appeared more than capable of cleaving through any commonly encountered organic matter in a single blow. Unit D was not organic, however, and postulated the blade as merely a moderate threat - and that only in a prolonged encounter.

The creature detected Unit D during this examination and turned to face it, dark eyes wide open and staring in a look of passive ill-will. Then the creature began to dart forward, moving at an incredible speed and hastened by a paranormal tailwind that it generated behind itself as it galloped toward its prey. The horn led the charge, piercing the air resistance at the front.

Of no little to no immediate importance to Unit D were some of the other details of the horse's body: eerily pale-blue skin without hair, dark hooves that looked like the colors black and blue had bred with one another (and produced an uncommonly ugly offspring), and an impressive package of equally hairless genitals that hung down in normal equine style below the creature's loins, with an unusually thick sheath and scrotum concealing the masculine organs within. The golem filed all of this information away every bit as dutifully as it did for the more important parts, writing it to memory in the meagerest fractions of a second.

That done the golem lumbered forward to attack in melee, conserving its darting ability for a more ideal moment.

The clunky robot and high-velocity malevolent unicorn soon met each other in a dramatic clash. Unfortunately Unit D took the worse side of the exchange: the equine ducked below its first punch before jousting upward, cleaving a shallow gash across the left half of the golem's lower chest armor before it could react. The equine then immediately propelled himself forward, his eerie blue tail flicking whiplike in the winds as he passed. Unit D's follow-up attack came much too late and struck nothing, and the horse circled around to prepare to charge again.

Unit D learned from this that normal prediction and slow motions were too slow to deal with the horse and that high-speed motions would have to be used. It prepped its reactors in anticipation, holding its two blocky arms out at its sides and keeping both fists near to the ground for now, with one of its knees bent in something vaguely akin to a sprinter's starting stance. The circling horse charged once again, and this time the golem was ready: its reactors whirred and launched it forward in a high-speed charge. The horse tried to correct, but moved too late, and the golem slammed into his neck from the side with an outstretched fist.

The force of the blow lifted the horse bodily from the ground and sent it spiralling through the air off to the golem's side. The horse flailed its limbs but could not right itself against the momentum of the golem's fast punch. A moment later the beast's head and horn struck the ground in an awkward series of motions that would've easily snapped the neck of any ordinary horse. No such fate occurred for this animal, however: it snorted in contempt and glared at the golem from its position on the ground.

Unit D's high-speed maneuver came to an end, and the horse wasted no time in starting his retaliation. The strong winds that had been accompanying him changed direction, creating a forward updraft that simultaneously helped the horse to his feet and allowed him to charge Unit D's position at a higher-than-natural rate of acceleration.

With its large balls flopping in the gusty wind as it galloped, the stallion arrived to gore Unit D long before its high-speed locomotion would be available again. The golem tucked its arms narrowly together, holding them vertically and kneeling behind them as if creating its own massive tree to use as cover. To get around this defense, the stallion redirected its charge at the last instant, once again aided by the wind, and inflicted a one-meter-deep gash in the plating along the left side of the golem's belly. As before, the golem tried to counter, but even this wild, reaching swing did not move fast enough or far enough to catch the primal.

The stallion circled around again, and the cycle of charging attacks continued while Unit D worked to stall as well as it could.

For the moment, it appeared possible that this windborne horse might bring the golem down in a death by a thousand papercuts. But this was a primal, and the five primals must be destroyed - priority 100. Self preservation was only a concern as it related to prolonging the viability of destroying all primals, and for now retreat seemed quite unnecessary.

The stallion passed again, and again, whirling around the area in quick, successive circuits, not giving the golem much lead time, and abusing his wind powers to make the sharp turns easier to take. Unit D could turn its body and guard, but that was just about all it could do without speed.

Then, at last, its high-speed option returned.

At that moment, the stallion was already in the middle of its charge again. So the golem did what it had to do: it made a short, inefficient dash that appeared more probable than all other immediate options to result in damage to the primal, directing its force into a leaping uppercut intended to strike the horse directly on the center of its chest, with the intent of damaging vital organs via impact shock even if penetrating the ribs proved impossible.

Coincidentally - in what was purely an accident of timing and positioning by both fighters - this attack worked, and it worked catastrophically well, although not for any of Unit D's originally calculated reasons.

The cascade of lucky events began when the horse tried to rear back and kick in response to Unit D's attack. Due to the extreme velocity with which the golem moved, the horse had barely time enough to do anything more than lift his front hooves a few centimeters off the ground - but this shift in the horse's momentum (and direction) ended up meaning a great deal. Unit D's leaping uppercut connected as planned, and the horse's forequarters shot upward like a ragdoll struck by dynamite - even faster than the golem had originally calculated, borne up in part by the horse's own efforts in that direction.

In the split second after the impact, Unit D could already tell that the blow appeared to have caused no harm to the horse, as its facial expression showed no immediate signs of pain or of stoppage of its heart. It looked only annoyed - bothered that Unit D had again thrust it off its intended course.

Concluding that the horse would not die from the chest attack, and seeing an opportunity to continue its attack from midair, Unit D thrust its legs downward in a kicking motion, aiming in the general area of the golem's stomach and groin, which were tilting and rising upward due to being carried aloft by the same force that had sent the beast's chest reeling. The hind legs of the horse came off the ground right around the moment that the golem's blocky left foot made a direct, but quite accidental, impact into the interior rim of the horse's sheath.

The primal's hunky testicles sloshed forward in their sack from the sudden crash of metal against groin. To Unit D's surprise - inasmuch as a robot can be surprised - the flesh inside the sheath gave way to Unit D's foot as if it were a pile of warm butter, smushing brutally beneath the weight of the kick. With the hindquarters' momentum still carrying the rest of the cock and balls forward, the foot's descent into the horse's junk proceeded to its logical conclusion: the sheath ripped open like an old shirt, and in a single, horrible motion the heavy foot impacted the mushroom-like head of the equine's shaft. The cockflesh crumpled like cardboard, bursting in on itself from the combined forward-upward momentum of the horse and the downward-backward motion from the golem's foot.

While being crushed in this way, the flesh of the flaccid shaft got carried all the way to the ground. By the time Unit D landed, its foot was up to the ankle inside of the horse's abdominal cavity, having passed through three meters of maleness to get there.

The horse's horned head whiplashed helplessly against the ground as the rest of the body came ungracefully down, and its breath caught in its throat. The winds that had followed the beast suddenly calmed; it kicked its legs with fast-weakening force, until in a moment the body lay utterly still, with what appeared to be rigor mortis setting in with unnatural speed.

Unit D pulled its leg out slowly from the nethers of the beast's corpse and triple-scanned the body for signs of life. None at all were found - as if the entirety of the beast's flesh had ceased functioning in near-unison. Massive, body-wide cell death.

Experimentally, the golem tried crushing the horse's still relatively intact testicles beneath its foot. Seemingly quite vulnerable, the balls popped like balloons, spilling their contents in a bloody heap, with the vesicles spewing a curiously yellowish liquid along with the blood. Chemical sampling modules in the golem's feet were unable to identify most of the compounds found in either the blood or the semen-like fluid.

Unit D then tried punching the immobile carcass. It punched several times at full power but did not make a single hole in any region of the body. The hide still seemed so tough as to be practically impenetrable, but audiovisual analysis of the blows now reported some impact-related bruising of the internal organs beneath.

The golem synthesized this data into a working hypothesis: destruction of the genital member had resulted in immediate termination of the primal's life, and had ended whatever mechanism had kept the internal organs safe from impact-related damage. The testicles also appeared vulnerable, although it was unknown if destroying the member first made them so, or if they had been so from the beginning. Either way, Unit D would certainly remember to take the genitals into account as a priority target.

The golem recorded the entire fight's movements in its databanks for educational review, paused momentarily to run further diagnostics on its systems, and moved on. It had ended this encounter with only minimal damage considering the circumstances: a total of eight gashes in various locations on its chest and leg armor, none of which had penetrated fully enough to damage any of the golem's systemic components.

With no further deliberation required by its programing, the golem soldiered on, wandering off across the wide plain ahead, toward a bog in the distance.

Story (C) 2013 dolphinsanity and was anonymously commissioned.