Leisure Suit Larry: Box Office Bust Screenshots and Images - PC

Leisure Suit Larry: Box Office Bust
  • Publisher: Codemasters
  • Genre:Adventure
  • Developer: Team17 Software
  • Release Date:Mar 31, 2009
  • # of Players:1 player
  • ESRB:M - Mature (Blood and Gore, Drug Reference, Mature Humor, Strong Language, Strong Sexual Content, Violence)
  • Platforms:
Game Description: The Leisure Suit Larry Box Office Bust video game gives gamers an all-access pass to the glitz, glamour and gorgeous women of Tinseltown. In this third-person adventure game, Larry takes a summer job working on his uncle Larry's movie lot doing odd jobs and trying to uncover a mole from another studio who threatens to air the studio's dirty laundry in the tabloids.
G4TV Rating
  • Avg User Rating
    (2 Ratings)
    2.5 / 5
  • Rate This Game
  • Leisure Suit Larry: Box Office Bust Gameplay Trailer

    Posted: March 27, 2009

    4,752 Views | 01:46 | 1 Comment

  • Leisure Suit Larry: Box Office Bust FMV Trailer

    Posted: March 27, 2009

    1,941 Views | 01:11

  • Leisure Suit Larry: Box Office Bust Jay Mohr Profile

    Posted: March 20, 2009

    3,234 Views | 01:44

  • Things We'd Love To Kill

    Posted: February 13, 2009

    49,492 Views | 05:57 | 42 Comments


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