Far Cry 4 received a bizarre update on April 3 that many users say censored the nudity out of the game. The update was seemingly only released for the PC version on Steam.
According to players that received this update, the update added clothing to at least one female NPC that was previously topless. The update also added a loincloth to the male player character, Ajay, during a brief scene where he wakes up naked in an arena.
Making this even more odd is the fact that Ubisoft censored this content ten years after the game was released.
This led to immediate speculation that Ubisoft may have been forced to censor the game at Tencent's request. Players were concerned that the China-based Tencent was already pulling some strings behind the scenes to impose censorship on Ubisoft's titles. Tencent recently invested $1.3 billion in Ubisoft in exchange for a 25% share of a newly announced Ubisoft subsidiary.
Ubisoft issued a statement, via community developer Patricia Brochu-Gagne, that the recent update was made in error. Somehow, the update accidentally added in already existing content from the nudity-free Japanese version of the game to the global version.
After looking into it, we confirmed that there was a mistake during a recent update: content meant specifically for the Japanese version of the game was mistakenly uploaded to the worldwide (WW) version on Steam. This resulted in unintended changes, including censored models and assets.
The team has already resolved the issue by re-uploading the correct data to the WW depot on Steam. If you’re still seeing anything off, we recommend restarting Steam and checking for updates.
No worries, there are no plans to censor Far Cry at any time. This was simply an error tied to a specific regional build, and it's now been corrected.
The team has already resolved the issue by re-uploading the correct data to the WW depot on Steam. If you’re still seeing anything off, we recommend restarting Steam and checking for updates.
No worries, there are no plans to censor Far Cry at any time. This was simply an error tied to a specific regional build, and it's now been corrected.
