X

Star Wars: Jedi Starfighter Latest News - XBX

  • Publisher: LucasArts
  • Genre:Action, Adventure
  • Developer:
  • Release Date:May 14, 2002
  • # of Players:2 players
  • ESRB:T - Teen (Titles rated "Teen (T)" may be suitable for ages 13 and older, and may contain violent content, mild, or strong language, and/or suggestive themes.)
  • Platforms:
Game Description:The Starfighter series continues with Star Wars Jedi Starfighter. You play a dual role as Jedi Master Adi Gallia and alien pilot Nym, who team up to stop Captain Cavik Toth and his Sabaoth Squadron. You'll pilot Obi-Wan Kenobi's spaceship from Episode II, equipped with Force powers for combat, including Force lightning, Force shield, and Force wave. Fly in more than 20 intense, richly designed one-player or cooperative two-player missions, exploring the planets and space zones featured in Episode II: Attack of the Clones.
G4TV Rating
N/A
  • Avg User Rating
    N/A
  • Rate This Game

Star Wars: Jedi Starfighter News

Displaying 1–1 of 1 articles

  • Mark Hamill Was Never Asked To Voice A Star Wars Video Game

    You'd think it'd be natural for LucasArts to ask Mark Hamill, aka Luke Skywalker, to be part of one of the many Star Wars video games that have been produced over the years. PC Zone recently spoke with the former member of the Force, however, and said it's never happened. Post-Star Wars, Hamill has made a name for himself as a prominent voice...

    Posted January 5, 2010

    Mark Hamill Was Never Asked To Voice A Star Wars Video Game

 


Runtime Error

Server Error in '/' Application.

Runtime Error

Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".


<!-- Web.Config Configuration File -->

<configuration>
    <system.web>
        <customErrors mode="Off"/>
    </system.web>
</configuration>

Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.


<!-- Web.Config Configuration File -->

<configuration>
    <system.web>
        <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
    </system.web>
</configuration>