Far Cry 3 (List of Unplayable Builds)
Jump to navigation
Jump to search
| ||||||||||
| Far Cry 3 (List of Unplayable Builds) | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
-title.png){kind=link}
| Download Far Cry 3 (List of Unplayable Builds) (info) |
The Hidden Palace wiki contains several prototypes of Far Cry 4, however, there are some builds that are completely unplayable due to missing files. For organizational purposes, all items that have the above characteristics will be listed here. Please note that a build that allows access to one of the various gamemodes should not be included here as it is not unplayable but partially playable.
Regarding incomplete or unplayable prototypes, we have the following:
Mar 23, 2011 prototype
- This is the oldest build so far (although it is incomplete).
- Originally found on a Terarelease 1.0 hdd Ubisoft Massive HDD #1 - Far Cry 3, Assassin's Creed 4.rar.
- It is unknown whether it is an internal multiplayer build or not.
- The build date is not accurate as it was based on the file creation date on the HDD.
- This build only contain one world (by itself) which translates into an extremely incomplete build. This World is pvp_kas06_pitaya. pvp_kas06_pitaya.dat has a medium chance of being corrupted and other files are not corrupted.
Apr 11, 2011 prototype
- Originally found on a Terarelease 1.0 hdd Ubisoft Massive HDD #1 - Far Cry 3, Assassin's Creed 4.rar.
- It is unknown whether it is an internal multiplayer build or not.
- The build date is not accurate as it was based on the file creation date on the HDD.
- This build only contain one world (by itself) which translates into an extremely incomplete build. This World is pvp_jas16_durian. pvp_jas16_durian.dat has a medium chance of being corrupted and other files are not corrupted. pvp_jas16_durian_english.dat is not corrupt. The remaining files have a low chance of being corrupted.
Sep 12, 2011 Multiplayer prototype
- Originally found on a Terarelease 1.0 hdd Ubisoft Massive HDD #1 - Far Cry 3, Assassin's Creed 4.rar.
- The build extracted from HDD is quite incomplete, containing only the files fcx.exe, fcx.xdb and fcx.xex, which goes without saying that the build in its current state cannot be reproduced (there are even older files that the build date, but even then they would be insufficient to work).
- Looking at its build name, it is possible to say that it is an internal multiplayer build.
- The build name is FLINT-MSV-MAIN-PACKAGE-580.0
Jan 14, 2012 prototype
- Originally found on a Terarelease 1.0 hdd Ubisoft Massive HDD #1 - Far Cry 3, Assassin's Creed 4.rar.
- It is unknown whether it is an internal multiplayer build or not.
- The build date is not accurate as it was based on the file creation date on the HDD.
- This build only contains two worlds (by themselves) which translates into an extremely incomplete build. These two worlds are:
- coop_press: coop_press.nfo and coop_press_english.dat have a high chance of being corrupted according to fatx. coop_press.dat has a medium chance of being corrupt. coop_press.fat, coop_press_english.fat and coop_press_english.nfo have a low chance of the files being corrupted and the rest not being corrupted;
- pvp_jas21_ginger: pvp_jas21_ginger'.dat has a high chance of being corrupted. All files named "english" have a low chance of being corrupted and other files are not corrupted.
Feb 2, 2012 prototype
- As fc3_main (campaign mode) world exists in this build, it is possible to say that it is not an internal multiplayer build.
- Originally found on a Terarelease 1.0 hdd Ubisoft Massive HDD #1 - Far Cry 3, Assassin's Creed 4.rar.
- Only the worlds could be recovered, as it seems that everything else (including executables) no longer exists. This makes the build unplayable.
- Supposedly all worlds are recovered and according to fatx:
- coop_pvp_sof04: All the files that have "english" and "vistas" in the name have a low chance of being corrupted. The remaining files are not corrupted;
- coop_skadi: All the files with name "vistas" have a high chance of being corrupted, coop_skadi.dat has a medium chance of being corrupted and the remaining ones have a low chance of being corrupted;
- coop_sleipnir The coop_sleipnir_english.dat, coop_sleipnir.nfo and coop_sleipnir_vistas.nfo have a high chance of being corrupted. coop_sleipnir.dat has a medium chance of being corrupted and the other files have a low chance of being corrupted;
- coop_vidar: The coop_vidar_english.fat and the coop_vida_english.nfo have a low chance of being corrupted. coop_vidar.dat has a medium chance of being corrupted and the rest have a high chance of being corrupted;
- fc3_main: fc3_main_english.dat has a high chance of getting corrupted. fc3_main.dat has a low chance of being corrupted and the other files are not corrupted;
- frontendworld: frontendworld.dat and all files with "english in the name" have a low chance of being corrupted. The remaining files are not corrupted;
- multicommon: multicommon_english.dat has a high chance of getting corrupted. multicommon.dat has a medium chance of being corrupt and the remaining files have a low chance of being corrupt;
- pvp_jas18_buddhashand: pvp_jas18_buddhashand.nfo and pvp_jas18_buddhashand_english.dat have a high chance of being corrupt. pvp_jas18_buddhashand.dat has a medium chance of being corrupt. pvp_jas18_buddhashand.fat, pvp_jas18_buddhashand_english.fat, and pvp_jas18_buddhashand_english.nfo have a low chance of becoming corrupted. The remaining files are not corrupted;
- pvp_jas19_wat: All files with "vistas" in the name have a high chance of becoming corrupted. pvp_jas19_wat.dat has a medium chance of being corrupted and the other files have a low chance of being corrupted;
- pvp_lee01_pear: pvp_lee01_pear.dat has a medium chance of getting corrupted and all other files have a low chance of getting corrupted.
- Using xenia and adding the main world files to the build Far Cry 3 (Mar 30, 2012 Multiplayer prototype), xenia will give a black screen due to the lack of devkit support. using a modified version it is possible to solve this however the build will stay infinitely loading. this may be a problem with this modified version of xenia.