Directory

Encyclopedia

NodeWorks
                              ENCYCLOPEDIA

Link Checker

Home
Encyclopedia : G : G0 : G0- :

G0-T0

 

G0-T0

G0-T0 is an droid from the 2003 video game Star Wars: Knights of the Old Republic II: The Sith Lords.

Bio


To oversee and aid in the planetary reconstruction of the planet Telos, the Republic spent a great deal of credits to design a technical droid to handle the immense data that was produced daily: climate changes, shield management reports, etcetera. This protocol droid was known as G0-T0. Known to few, however, was that the droid also had a secondary duty: to aid the reconstruction of the Republic, wounded itself from the aftermath of the Jedi Civil War. To accomplish this task, it had two directives:

  • Produce options to rebuild the Republic
  • Follow all the laws of the Republic.

Working for quite a long time to accomplish its duties on Telos, the droid found itself unable to follow both of the directives for rebuilding the Republic. Every logical option wound up breaking a law of the Republic. In that moment, the droid broke. Choosing to follow the first directive, the droid began to enact plans to save the Republic, regardless of their legality.

Eventually building a jet-black orb of a body, G0-T0 began to set up as a smuggling ring on the planet of Nar Shadda. Since few would believe a droid could run an elaborate smuggling operation, G0-T0 used a hologram emitter to create the identity of "Goto". Instead of being the smuggling operator itself, G0-T0 would simply be Goto's liason. G0-T0 set up the hologram by studying the mannerisms of famous holovid actors. Taken together, the illusion was so effective that few, if any, knew of Goto's true existence.

G0-T0's actions, while illegal, did aid the Republic in rebuilding itself. Its smuggling ring caused the deaths of destabilizing persons or organizations, developed unoffical profits for entire sectors, and strengthened Republic worlds that would otherwise be poor and ignored. Believing also that the major source of the Republic's problems resolve around the Jedi/Sith conflict, it also enacted bounties for live Jedi and Sith. Many bounty hunters simply killed Jedi and Sith instead of capturing them, but the outcome remained: less Jedi or Sith to fight against each other meant less fighting peroid.

G0-T0's plans were foiled by a Jedi, captured under the Jedi Bounty: the Jedi Exile. Uncloaking Goto's private ship, it was destroyed by the many enemies of Goto, formerly unable to locate the mysterious ship before. Goto presented himself to the Exile on the Ebon Hawk, but as Goto's "gift" - not Goto himself. G0-T0 found himself increasingly annoyed by another spheroid droid onboard the Hawk: Bao-Dur's tiny remote droid.

This annoyance came to a head on the planet of Malachor V. G0-T0 guessed that Bao-Dur's remote was intended to re-charge the Mass Shadow Generator on the planet, destroying it entirely. The smuggling robot felt that the planet contained too many priceless artfiacts to destroy, and attempted to stop the Remote from activating the weapon.

Much to the chagrin of some, the outcome of this conflict is shown, instead of spelled out. If the Exile has played the game as a Jedi, it is assumed that G0-T0 fails in his attempt to destroy the Remote: the planet is destroyed by the Mass Shadow Generator. If the Exile has played the game as a Sith, the planet remains intact; G0-T0 is dead.

It is believed that some of this outcome would have been longer, had the "Droid Planet" levels in The Sith Lords remained in-game. In those deleted levels, it is believed that G0-T0 reveals he himself used HK-50 assassin droids to hunt for the Exile. In the Droid Planet levels, also, HK-47 was supposed to come to an agreement with the HK-50s, and that these droids would destroy G0-T0 during the finale's G0-T0/Remote standoff.


NodeWorks boosts web surfing!
Page Returned in 0.267 seconds - HTML Compressed 65.9%

This article is from Wikipedia. All text is available
under the terms of the GNU Free Documentation License.
 GNU Free Documentation License
© 2008 Chamas Enterprises Inc.