Yakuza 4 Screenshots and Images - PS3

  • Publisher: SEGA
  • Genre:Action, Adventure
  • Developer: SEGA
  • Release Date:Mar 15, 2011
  • # of Players:1 player
  • ESRB:M - Mature (Blood, Sexual Themes, Strong Language, Violence)
  • Platforms:
Game Description:Yakuza 4 picks up the story of Yakuza 3 one year later and takes the player back to Tokyo. The story starts when a man is shot to death in the ruling territory of the Tojo Clan, the organization that has featured in all games in the series to date. A small gang which belongs to Tojo Clan try to establish what happened and their leader is soon found stabbed to death. These events cause a heated battle between four men over money, power, status and honor. The truth becomes apparent as the lies, betrayals and entwined stories are revealed and when these 4 unflinching men get together, the new legend of Kamurocho is born.
G4TV Rating
3 / 5
  • Avg User Rating
    (8 Ratings)
    3.5 / 5
  • Rate This Game

Yakuza 4 Screenshot & Image Galleries

  • Forza Horizon And Forza 4 DLC Interview

    Posted: March 6, 2012

    7,324 Views | 02:48

  • Yakuza 4 Video Review

    Posted: April 12, 2011

    8,913 Views | 02:47

  • Sexy Moments In Yakuza 4

    Posted: April 5, 2011

    26,130 Views | 08:26

  • Yakuza 4 "Kamurocho Locations" Trailer

    Posted: March 10, 2011

    1,537 Views | 01:42

  • Yakuza 4 Hands-On Preview

    Posted: February 16, 2011

    7,946 Views | 03:24


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