*If two seprate mods use the same files such as damage and weapons, unless the one mod is made as a patch, mixing these two will either result in a crash, or the weapons will not work right, such as, seems like shooting blanks or you hit a NPC or get hit by a NPC and your flying across the entire game map in one shot, ect, ect. you can delete the CoP folder, and CoC will continue to work just fine. Call of Chernobyl should NOT be installed over CoP like other mods. In 2007, Ukrainian developer GSC Game World took the bold and counter-intuitive step of using. The program dose not write one file into another to add in the missing code lines. S.T.A.L.K.E.R.: Shadow of Chernobyl and Memory of Utopia. Common to be used by people who do not have the full know how of windows explorer to drag and drop for copying in the game directory themselves. *Mod Mergers just basicly copy all mods into the game directory. Not one file is modded the same as another unless that modder has resourced a modded file from the other mod and made no edits except to add to it. When mixing mods you must make sure they are not useing the same kind of files, if they use the same kind of files, they will always result in a crash. These kinds of add-in maps are not available in COP, so they will not be setup in a mod for COP Unless the mod says it is for "COC", it will probably not work, because COC uses a mix of the old maps from the original presataion version of the game for THQ, maps from Shadow of Chernobyl (the final cut for THQ), Clear sky, Call Of Pripyat including some created by the dev themselves such as the extended version of the real vehicle scap yard. So COC has to work out of it's own folder.
When COC starts up it checks to make sure a legal copy of COP exsist first before loading up. Because the COC dev do not support illegal copies of COP.
COC is not a mod for COP, COC is a stand alone mod game itself that needs to have COP in order to work.
0 kommentar(er)
