Welcome Guest [Log In] [Register]
Welcome to Alex's DBZ RPG 5 Forum. We hope you enjoy your visit.


You're currently viewing our forum as a guest. This means you are limited to certain areas of the board and there are some features you can't use. If you join our community, you'll be able to access member-only sections, and use many member-only features such as customizing your profile, sending personal messages, and voting in polls. Registration is simple, fast, and completely free.


Join our community!


If you're already a member please log in to your account to access all of our features:

Username:   Password:
Add Reply
Digital Vendetta Pt.7; Dragonball Quest 7
Topic Started: Jun 21 2017, 06:31 PM (79 Views)
Bassolarr
Member Avatar
KING OF THE RING
Monitors
Without the aid of his missiles, he would have to find another method of attack—and so far, the only one Rubic could surmise as being supremely effective would be either turning the electricity back on Elecman or finding something else to force his abilities to act awry. The first option was the improvised booby trap they had set up—the electrified bench from earlier. Getting it to spring its own trap seemed highly unlikely, however, but Rubic was unable to penetrate the electrical defenses with certainty—he would have to give it such a course of action some level of attempt in order to overcome. He could deal with any consequences later should it prove successful.

Rubic raised his free hand up, the hand sliding back into the forearm in order to make room for the gattling gun module, the barrels already rotating by the time they were visible, a dull whine audible in the air as the device spun to the ideal rotational speed. A hail of bullets roared forth from the multi-barreled weapon, forcing Elecman to bring up his shield again and retreat from the vicious onslaught, meter by meter as the force of each impact had to be dealt with. Rubic continued the assault, looking to either pierce through the shield through sheer firepower or push Elecman back towards the trap, thereby overloading Elecman’s circuits—hopefully. Rubic’s scanners could not penetrate all the electromagnetic signatures going on in Elecman’s body, making it impossible to determine Elecman’s electrical tolerance. For all Rubic could know, such a maneuver would only boost the opponent’s firepower, which would seal Rubic’s doom. The nearly-intangible quality of electricity on its own usually made for an ineffective barrier--such was the raw power output from Elecman that it was highly probably he possessed some exotic and potent capacitor. Using other knowledge of such devices, it was possible Elecman had to carefully gauge and control the throughput of his systems in order to prevent explosive discharge...

Sometimes, experimentation was required. Rubic kept up the punishing attack until the barrels were too hot to continue, the rotational energy and kinetic friction from so many rounds inevitably causing a heat warning--but just as Elecman dropped his shield to attack, he set his feet upon the ground, one foot touching the bench and the other--there! Even in the instant the mistake was made, Rubic was already calculating the probability of this experiment's success--by the feet landing at such a precise location, Elecman was not just completing a circuit to ground, thereby flooding the mechanical body with extremely high values of voltage and amperage, it was possible that Elecman's own grounds would either be drained or forcibly put into a loop--

A loud sizzling sound could be heard from Elecman, the sound of air popping and fizzing around him as he suddenly went rigid, several hundred gigawatts of energy pouring into the android from tripping his own trap. A true synthetic would not have made such a mistake--surely, it possessed systems necessary to keep track of such things.. but that did not appear to be the case. Suddenly, pieces and limbs of the android burst off of him as capacitors and components exploded violently from the overcharge of electricity. Once the power was spent, the lifeless shell of the enemy android fell to the ground, collapsing in on itself due to the superheated metal of all that energy discharge, enough to power several cities on Earth, ten times over. The station went completely dark—all lights and power breakers tripping from the massive exchange of power through the grid, likely affecting many nearby towns in the process—but with that, Rubic was able to safely remove the Dragon balls from the station and secure them in his internal storage.

At that moment, Rubic contemplated what had become of the seventh android sent to this planet. It was possible that it had retreated to make contact with the other team, confident Elecman would stop Rubic from completing his own objective. However, there was no hard data to back up that assessment—for all Rubic knew, it was highly possible that the enemy was still on this planet, likely plotting an attack or retaliation for what had transpired today. Still, with all seven in tow, Rubic realized that he could now summon the dragon—but Rubic had no desire at the moment, not that he ever did in the first place. His only goal was to stop Unit Orion from making a wish with the orbs, and now that Rubic had them, it was imperative that he render them defunct for a significant length of time—but to what end?

Regardless, with the mission completed, Rubic would have to make an escape from this area back to his ship in order to prepare it for the trip to Namek. Hopefully, Chishan would have received the communication and begun stopping the rogue units from collecting the Dragon Balls there, or, at the very least, the local population would have made it a point to resist against the robotic attackers. No matter the situation, Rubic would have to waste no time in going to planet Namek in order to secure the Dragon Balls from Unit Orion’s grasp—just as he did with the ones on Earth. Rubic emerged from the power station, the area as dark as the night cast it, just in time to notice several craft approaching the facility. Likely, these were what passed for the Earth Defense Force remnants and Saiyan patrols of the planet, likely responding to the high energy levels detected here. Rubic would very well have to fight his way off of this planet if he did not leave right away.

Like a rocket, Rubic took off into the sky at best speed, logging in the location of his ship on his navigation equipment in order to hasten his approach. The patrols did not immediately pursue, preferring to examine the wreckage of the relay station and determine what had occurred there. The remains of Elecman had been destroyed, as with the other five that Rubic had fought against, but the signs of combat would be clear as day to any investigators searching the area. Rubic did not have the time nor the inclination to explain the situation to a possibly hostile military (or paramilitary) force. He needed to be on his way to the next mission after rendering the Dragon Balls inert for a short time—something that would, at the very least, require a safe location.

Thankfully, when Rubic returned to his ship, the Saiyan patrols had moved on, wishing to try and track down the rogue robot. This allowed Rubic at least a little time to settle the task of the Dragon Balls. Once they were placed on the ground and arranged, Rubic summoned forth the great dragon of Earth—Shenron!

With the skies already dark, the presence of such a fearsome beast would merely be heralded by an electrical storm in the air, as if a harbinger of dark times and turbulence to come, but Rubic was neither impressed or intimidated—he was very much incapable of either. The dragon came into being first as a snaking pillar of light until he formed completely, his massive length arranged before the android. And with a voice that shook the heavens and the earth, the dragon spoke, demanding to know why it was summoned and what the wish of an emotionless robot would be.

The droid had to calculate for a long moment before giving his answer.

Sometime later, after the encounter with Shenron, Rubic was finally able to man the helm of his ship, wirelessly guiding the Codex off the ground and towards the heavens, pushing through the darkened skies and towards the star-lit curtains of space. Of course, his departure likely alerted every Saiyan patrol in the area, various signatures showing up on Rubic’s sensors. The Saiyans were proving to be extremely persistent in their pursuit of both the ship and its pilot, but even as Rubic activated the warp engines on the ship, plotting a course for Namek, Rubic was able to facilitate another message for Chishan’s ship—just in case he was able to receive them. It was highly likely that Chishan would be in a region of space that could not receive transmissions or, at worst, be unable to receive them entirely due to damage or death. But…

Rubic’s energy scanner could still pick up the faint energy readings of Chishan’s powerful ki. No… Chishan was still alive and well. Rubic would just have to trust that his messages would reach the former Team Rocket member and keep the both of them in touch and coordinated. He was unsure of Levana’s status, otherwise he would have enlisted her aid as well…

Pan was still missing in action, having left on her own assignment some time ago. Minosha was, unfortunately, still missing as well. This left himself, Chishan, and Levana as part of the original team, with Chishan regularly adding new additions to his own ship—additions that Rubic was now only becoming aware of recently. While Chishan likely took on others onto his ship for support functions and possibly combat functions—Chishan was one of the most powerful individuals Rubic knew of, so he was not sure why he would need assistance in a combative department—Rubic only needed himself to run an entire carrier. It was… interesting how they both differed, yet they called upon one another on a regular basis. However, whether or not Chishan would be able to respond to the situation on Namek was still not known—Rubic would just have to trust he would arrive at Namek in time to stop whatever might be unfolding there.

UNIT CHISHAN,
THIS IS UNIT RBC-411 DESIGNATION RUBIC
THIS UNIT HAS MANAGED TO DEFEAT THE SQUAD DISPATCHED TO EARTH AND HAS RENDERED THE DRAGON BALLS INERT FOR THE TIME BEING. THIS UNIT WILL SET COURSE FOR NAMEK TO DO THE SAME ON THERE AS WELL.
NOTE: ONLY SIX ANDROIDS WERE FOUGHT ON EARTH—THE SEVENTH UNIT HAS RETREATED BACK TO NAMEK IN ORDER TO HELP ENSURE THE SUCCESS OF THEIR OPERATION THERE. IT IS IMPERATIVE THAT THEIR PROGRESS BE HALTED AT ALL COSTS.
UNIT RBC-411 SIGNING OFF.

With that, Rubic activated the warp drives of the ship and made for the planet Namek, already working on repairing his synthetic body of the damage wrought upon it by the six opponents he had faced that day—and to prepare it for the other eight that he would likely encounter upon the planet of Namek. It was imperative that whatever plans Orion had for these orbs of power be stopped—even if Rubic had to sacrifice his own functions in order to do so. He could already hypothesize Chishan’s protests at such a concept, but one thing was for certain with Rubic.

The Steel Legion cannot be allowed to return.

WC: 1807
Offline Profile Quote Post Goto Top
 
1 user reading this topic (1 Guest and 0 Anonymous)
« Previous Topic · Earth · Next Topic »
Add Reply

RPG Chat RPG-D RPGfix eXTReMe Tracker

Back to Alex's DBZ RPG | Back to Main Forum

Black Water created by tiptopolive of the Zetaboards Theme Zone