X

Star Wars Jedi Knight II: Jedi Outcast Latest News - GC

  • Publisher: LucasArts
  • Genre:Action, Shooter
  • Developer: Raven Software
  • Release Date:Nov 19, 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:Jedi Outcast builds on the award-winning first-person action of Jedi Knight. As the rebel jedi Kyle Katarn, you come out of retirement to fight the mounting Dark Side of the Force. Your Jedi powers include Jump, Push, and Jedi Mind Tricks, and you'll be armed with new lightsaber attacks and combos. You'll also find weapons like the stun baton, Bryar blaster, and blaster rifle. Jedi Outcast uses id's groundbreaking Quake III engine to bring the world of Star Wars to life, including Yavin 4, Nar Shaddaa, Cloud City, and exclusive new Star Wars locales. Co-op and deathmatch multiplayer options add hours of gameplay.
G4TV Rating
N/A
  • Avg User Rating
    N/A
  • Rate This Game

Star Wars Jedi Knight II: Jedi Outcast 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>