Star Wars: Republic Commando Latest News - XBX

  • Publisher: LucasArts
  • Genre:Shooter
  • Developer:
  • Release Date:Mar 1, 2005
  • # of Players:10 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:Star Wars: Republic Commando is an action-packed stealth-tactical, first-person shooter set in the early days of the Clone Wars, as glimpsed at the end of Star Wars: Episode II. Using an enhanced Unreal engine, LucasArts brings to bear the thrilling designs and storyline of Star Wars while taking fans far into a more brutal battle experience. As an elite squad member of a Republic Special Operations unit you will penetrate deep behind enemy lines on a series of missions involving cooperative gameplay between Jedi Knights and Clone Troopers.
G4TV Rating
  • Avg User Rating
    (2 Ratings)
    5 / 5
  • Rate This Game

Star Wars: Republic Commando 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 -->

        <customErrors mode="Off"/>

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 -->

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