FANDOM


GrievousactionBFII

More... More... MORE!

It is requested that this article, or a section of this article, be expanded.

See the request on the listing or on this article's talk page. Once the improvements have been completed, you may remove this notice and the page's listing.

SWBountyHunter
Star Wars: Bounty Hunter
Developer(s)

LucasArts

Publisher(s)

LucasArts

Release date

December 5, 2007

Genre

Third person action adventure/shooter

Modes

Single Player

Rating(s)

ESRB: Teen (T)

Platform(s)

Playstation 2, GameCube

Star Wars: Bounty Hunter is a single player game following the story of Jango Fett during and after the events of Star Wars Episode I: The Phantom Menace. Jango Fett is the only playable character.

Key EventsEdit

  • Count Dooku hiring Jango to be cloned
  • The order for an unaltered clone for Jango - Later known as Boba Fett
  • The Death of Montross

CharactersEdit

AlliesEdit

  • Rozatta - a friend of Jango Fett. She was a pink Toydarian who owned the Outland Station which hosted underworld games. She helped Jango find bounties.
  • Zam Wessel - Jango meets Zam on Oovo IV however Zam captures Jango's bounty, Bendix Fust, and they are both forced to work together and escape on a firespray patrol ship, later renamed Slave I.

Enemies (Main Enemies i.e. Boss's)Edit

  • Meeko Ghintee - A dishonest criminal who makes the mistake of rigging pit beast fights in the Outland Station. Meeko is the main objective for the first chapter of the game.
  • Jervis Gloom - Jango hunts down this deathstick dealer to find out what he knows about the mysterious Bando Gora cult
  • Bendix Fust - Jango needs to capture him to get to sebolto, a dug.
  • Komari Vosa - A former apprentice of Count Dooku Jango must kill or capture her to get the reward from count Dooku.

Other Key CharactersEdit

LocationsEdit

Audio ClipsEdit

Ad blocker interference detected!


Wikia is a free-to-use site that makes money from advertising. We have a modified experience for viewers using ad blockers

Wikia is not accessible if you’ve made further modifications. Remove the custom ad blocker rule(s) and the page will load as expected.