Far Cry 4 (List of Unplayable Builds)
Far Cry 4 (List of Unplayable Builds) | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
|
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 (however, if the executavles of a certain build don't start, that build will have to stay here). Also, do not include install data as these prototypes are always incomplete.
A list of such prototypes can be found below.
May 23, 2014 prototype
- Dumped by anthony -ultimatefarcrymodder and launched by the same on September 6, 2024. That build came from a hdd belongs to mrpinball64.
- The build name is MTL-FCC-STABLE-58.9.
- Not all nfo, dep, and dpv files have been dumped by dumped option (they do not be needed to make the build functional).
- Despite the prototypes world having all the archives, all xexs give a black sceen. The reason is Unknown. It should be noted that the multicommon world and fcc_main are incomplete making multiplayer and singleplayer non-functional.
Jul 3, 2014 prototype
The build name is MTL-FCC-MAIN-501.2 . This build can be found on the "xdk 6.2.2024" hdd (with manifest), but only 25 files were recovered and 228 files were lost (including all executable files). This prototype, if complete, would have the worlds for singleplayer/co-opp mode, the world for multiplayer mode and map editor, qamap, fcc_render_test and prototypes. Furthermore, all xexs have an associated pdb.
Jul 7, 2014 prototype
The build name is MTL-FCC-MAIN-503.4 . This build can be found on the "xdk 6.2.2024" hdd (with manifest), but only 4 files were recovered and 249 files were lost (including all executable files). This prototype, if complete, would have the worlds for singleplayer/co-opp mode, the world for multiplayer mode and map editor, qamap, fcc_render_test and prototypes. Furthermore, all xexs have an associated pdb.
Jul 9, 2014 prototype
The build name is MTL-FCC-MAIN-508.8 . This build can be found on the "xdk 6.2.2024" hdd (with manifest), but only 23 files were recovered and 230 files were lost (including all executable files). This prototype, if complete, would have the worlds for singleplayer/co-opp mode, the world for multiplayer mode and map editor, qamap, fcc_render_test and prototypes. Furthermore, all xexs have an associated pdb.
Jul 14, 2014 prototype
The build name is MTL-FCC-MAIN-513.3 . This build can be found on the "xdk 6.2.2024" hdd (with manifest), but only 4 files were recovered and 272 files were lost (including all executable files). This prototype, if complete, would have the worlds for singleplayer/co-opp mode, the world for multiplayer mode and map editor, qamap, fcc_render_test and prototypes. Furthermore, all xexs have an associated pdb.
Jul 28, 2014 prototype
The build name is MTL-FCC-MAIN-527.2 . This build can be found on the "xdk 6.2.2024" hdd (with manifest), but only 6 files were recovered and 300 files were lost (including all executable files). This prototype, if complete, would have the worlds for singleplayer/co-opp mode, the world for multiplayer mode and map editor, qamap, fcc_render_test and prototypes. Furthermore, all xexs have an associated pdb.
Aug 22, 2014 prototype
- Build version is MTL-FCC-MAIN-553.3 (a more complete dump is in progress).
- This build can be found on multiple images, devkit2605 (badly deleted) and xdk 6.2.2024.
- Only executables were recovered by kabojnk.
- Released on March 23, 2024;
Aug 23, 2014 prototype
- Build version is MTL-FCC-MAIN-555.0 (a more complete dump is in progress).
- This build can be found on Ubisoft_20.5.2024.
- Only executables, the gameconfig folder, the UplayMedia folder and the media folder were recovered.
- Executables can be used in Far Cry 4 (Aug 27, 2014 prototype) however.
- Released on March 23, 2024 and recovered by kabojnk;
~Aug 24, 2014 prototype
- Released on Oct 2024 by James2452 on Alphaarchive.
- It only contains the qamap world and it doesn't seem to correspond to any other known build.
- It will probably work on builds with close build dates.
Aug 26, 2014 prototype
- Build version is currently unknown. It is a different build than the Far Cry 4 (Aug 26, 2014 20.06 prototype) and the Far Cry 4 (Aug 26, 2014 23.20 prototype).
- This build can be found on Ubisoft_20.5.2024.
- Only executables, the gameconfig folder, the UplayMedia folder and the media folder were recovered.
- Executables can be used in Far Cry 4 (Aug 27, 2014 prototype) however.
- Released on March 23, 2024 and recovered by kabojnk;
Sep 5, 2014 prototype
- Build version is MTL-FCC-MAIN-567.3.
- This build can be found on xdk 6.2.2024.
- Only executables, the multicommon folder, the gameconfig folder, the UplayMedia folder and the media folder were recovered.
- Released on March 23, 2024 and recovered by kabojnk;
Oct 20, 2014
- Build version is MTL-FCC-MAIN-607.0.
- This build can be found on xdk 6.2.2024.
- Only executables, the gameconfig folder, the UplayMedia folder and the media folder were recovered.
- Released on March 23, 2024 and recovered by kabojnk;
~Jan 6, 2015 A
Released January 24, 2024 by James2452 on Alphaarchive. Although he mentions that the build contains xexs, in reality there are no xexs in it. The build itself is extremely incomplete and it appears that the files are not structured correctly (it is unknown whether this is on purpose or not). Contains a Patch Data.
~Jan 6, 2015 B
- Released on Oct 2024 by James2452 on Alphaarchive.
- The build date is inaccurate and probably incomplete.
- Contains the following DLCs:
- Behind Enemy Lines: This DLC was last updated on MTL-FCC-MAIN-620.3 which means it has a similar build date to October 2014;
- Overrun: This DLC was last updated on MTL-FCC-MAIN-621.1 which means it has a similar build date to October 2014;
- Overrun: This build does not contain toc.rml which makes it impossible to know its build name and perhaps a more precise build date.