X

50 Cent: Blood on the Sand Screenshots and Images - Xbox 360

  • Publisher: THQ
  • Genre:Action, Shooter
  • Developer: Swordfish Studios
  • Release Date:Feb 23, 2009
  • # of Players:1 player, 2 online
  • ESRB:M - Mature (Blood,Drug Reference,Intense Violence,Strong Language,Suggestive Themes)
  • Platforms:
Game Description:The tracks are as hot as they come and the action's as cold-blooded as it gets in this arcade-style third-person shooter that lets you become the world's biggest hip-hop star. 50 Cent: Blood on the Sand sends you into run-and-gun battles where you'll use a cover system, buddy NPC G-Unit AI, brutal melee counterkills, and more. Build your war chest by making kills and finding caches. Use it to buy 20 more weapons and add more crushing Counterkill Finishing Moves. Fight by 50's side in drop-in/drop-out online co-op play. He's rewarded your loyalty with a soundtrack featuring classic 50 Cent cuts and 16 exclusive new tracks.
G4TV Rating
4 / 5
  • Avg User Rating
    (2 Ratings)
    4.5 / 5
  • Rate This Game
  • Sessler's Soapbox: We Don't Need New Consoles (Yet)

    Posted: October 28, 2009

    40,736 Views | 08:16

  • G-Phoria 09: Best Soundtrack

    Posted: August 5, 2009

    4,552 Views | 01:27

  • Discussion: '09's Biggest Shockers

    Posted: July 23, 2009

    6,470 Views | 02:50

  • X-Play Presents: The Best Games of 2009 So Far

    Posted: May 26, 2009

    8,330 Views | 02:49 | 15 Comments

  • Cheat: 50 Cent Blood on the Sand Collectables

    Posted: March 12, 2009

    4,878 Views | 02:31 | 2 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 -->

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