X

LEGO Star Wars II: The Original Trilogy Latest News - XBX

  • Publisher: LucasArts
  • Genre:Action
  • Developer: Traveller's Tales
  • Release Date:Sep 11, 2006
  • # of Players:2 players
  • ESRB:U - Unknown (Titles rated "Everyone 10+ (E10+)" may be suitable for ages 10 and older. They may contain cartoon, fantasy, or mild violence, mild language, and/or minimal suggestive themes.)
  • Platforms:
Game Description:The war between the Galactic Empire and Rebel Alliance has left a galaxy far, far away in pieces! Thankfully, with LEGOs, rebuilding is easy! Experience the magic of the original Star Wars trilogy as you play through Star Wars, The Empire Strikes Back, and Return of the Jedi, all re-created with LEGO bricks! Play as over 50 favorite characters. In a LEGO Star Wars first, you can even get out of vehicles and ride creatures! Other new features include a game save from the first LEGO Star Wars that doubles the amount of characters, adjustable difficulty, the ability to switch ships anytime in Free Play Mode, and more!
G4TV Rating
N/A
  • Avg User Rating
    N/A
  • Rate This Game

LEGO Star Wars II: The Original Trilogy News

  • No results

 

 

 


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>