FANDOM


OverviewEdit

Far Cry 4 is Stephen's forty-seventh Let's Play, and the first Far Cry game Stephen has done as a Let's Play on StephenPlays. This marks the third Let's Play of a video game that was published by Ubisoft, following Assassin's Creed, and Assassin's Creed 2 in chronological order, though Stephen has covered Ubisoft games in general on the channel including a few Demo Fridays and First20 videos.

The game was first seen on StephenPlays via the Death By Far Cry 4 video which was explained on Day 1806 of StephenVlog. The story was Ubisoft invited Stephen and 24 YouTube users including JoshJepson to come to their studio in San Francisco and play an early copy of Far Cry 4 while recording the game to use in their separate videos that covered their experiences of the game. The game was later confirmed for a Let's Play on StephenPlays ten days later, the day Stephen's Death By Far Cry 4 video game out.

Similar to Grand Theft Auto V, Far Cry 4 is a game rated M for Mature by the ESRB, and as such this marks the second Let's Play of an M-rated game in which Stephen includes a viewer discretion warning at the beginning of each video, and as such, a different variety of methods to emphasize the warning.

Far Cry 4 debuted on November 26th, 2014 and concluded on March 29th, 2015.

EpisodesEdit

StephenPlays Far Cry 4 1 - "Welcome to Kyrat"-024:21

StephenPlays Far Cry 4 1 - "Welcome to Kyrat"-0

Thumbnail for the first episode of StephenPlays: Far Cry 4.

PlaylistEdit

NotesEdit

  • Ubisoft provided Stephen the PlayStation 4 and PC copies of Far Cry 4, and Far Cry 4 was originally going to be a PC Let's Play, though Stephen ran into some problems trying to record the PC version of the game. After getting a PlayStation 4 on Day 1827, he decided to record the PlayStation 4 version of Far Cry 4.

Ad blocker interference detected!


Wikia is a free-to-use site that makes money from advertising. We have a modified experience for viewers using ad blockers

Wikia is not accessible if you’ve made further modifications. Remove the custom ad blocker rule(s) and the page will load as expected.