-The purpose of this Guide is to help you with basic mod problems... You will find a copy of this guide in all three S.T.A.L.K.E.R. games because the information is the same for all 3. Understand clearly, I did NOT create this guide to bash mods in anyway. It was created for you to understand what might cause issues when using mods.

Because regardless what some may claim, the facts are, some mod do have issues, and that is all to it. Some not so bad, some not so great, and there are ones that just work fine. And sometimes the mod issue is really the result of the game failing to bind the mod properly.

-You may even find out, that you can solve your own problems and get better at the understanding of mods and their issues..

-Advanced users will be happy with this tutorial because anywhere you were lost, you will now have direction on what to do..

-This guide was not made to trouble shoot Call Of Chernobyl Or Lost Alpha. These are Game Mods. They stand alone working games mods that do not need to be in the main game directory, and can run on their own.

*Call Of Chernobyl requires a Legal Copy of Call Of Pripyat because the Developers do NOT support illegal Pirate copies of Call Of Pripyat. The Game Mod on start checks for the Legal Copy Of Call Of Pripyat, and then runs..

I keep it in it's own folder on the Hard Drive with a short cut to the desktop, and it runs great. It has been stated that Call Of Pripyat mods may work in Call Of Chernobyl. You will need to check with the Call Of Pripyat Forum community for that.. There are those who have done it, and know what works best.

*The Lost Alpha is also a stand alone mod game. It can be installed as is..
============================================================================

-->The primary understanding what a mod is used for in S.T.A.L.K.E.R....

A mod is used to enhance the game play experience in S.T.A.L.K.E.R. on the bases that you already played the default/vanilla game. What makes S.T.A.L.K.E.R. different than other game mods is, mods not only can enhance the experience just the same, but also alter the game itself, verses other games.

For example, the mod Priboi Story v.3.2.5 by dezowave for the older version of SOC rewrites the entire game play of SOC creating a completely new game. So to use this mod, as a first time play through would be a waste of time because it has absolutely nothing to do with enhancing the original SOC game at all. It takes place after the story. It is like you finished the default/vanilla and now here is a different story to continue with..

Using a mod to enhance the default/vanilla game on a first time play through will take away your ability to experience the "as is" developer made game. Now you will see all the Modder enhancements, but really your not seeing any of the changes. So you are not "awed" or "ooh" in amazement of the mod. It has no meaning except your playing it.

When you play the default/vanilla game, you see and deal what the developers had made, on the re-play with a mod, you see the Modder's take in the game, and all the changes are noticeable on how things are done. And then you are "awed" or "ooh" in amazement of the mod.

>Explaining the help...

On a first time play through with a mod, and the game CTD's, the player will blame the game, and when making the complaint, it is all about the game, because they feel that is the problem because someone else said "use this mod and have fun.".

This is misleading, Mods are not perfect, and tend to crash the game to CTD pending on what mod. Some can play through and work great, some corrupt the files such as save, some just can not play right and have broken code causing players to be stuck. This is the way it is, and anyone that plays other games that uses mods or plugins for others games, know this already...

Many players go to the forums, and cry for help, but fail to give important information to why the game CDT (Crash to Desk Top).

A CTD can be for any reason, so when your asking for help with a statement like, "My game crashed" and this is all. You gave nothing for anyone to help you. No one here in the zone is a mind reader, so you will never get the help. And refunding the game because you blame it on the game is not the games fault, mainly if you are using a mod.. All you are doing is fixing no one in the Zone, or the developers, just yourself.

*Remember, Not all Mods are not prefect, and some may cause a CTD..

-Because something was missing in the mod the Modder forgot to put in.

-Because the Modder resourced another file for another mod, and did not disable the extra lines that is needed in the resource mod, but not available in his own mod..

-Because he is adding code lines that the game engine can not do.

-Because he is adding code lines that accidently invoke the windows operating system to do, and the OS security system blocks it, and forcing the game to stop working causing a crash.

-A game object is missing, mislabeled, or corrupted..

-A game setting is out of bounds of what the game is designed to do.

-A game setting is incorrect

-The game has mistaken a setting as a cheat, and it's secret stop block has stopped the game, or has locked the player in a cheat box. (this is where your trapped in a grey box labeled cheat everywhere inside it. Common in SOC...)

-The mod script is incomplete causing the game to freeze, or stop, or a black screen...

-The mod script is making a request directed to it's mod controller script, but the line is missing, incomplete, wrong code line, function dose not exist, or the request is invalid so it returns back and makes the request to the dbase script, and the dbase script takes action but dumps it as invalid, and the x-ray engine can not run it.

- The demand of the mod is too much for the game system to bind properly and stops.

-The game when made was for the console version, but interfaced for PC, making the game not work correctly to bind the mod, and not mod friendly. (Clear Sky DVD only. Steam download version can run it better, but still has problems, not as bad as the DVD).

-this list can go on forever and clutter this guide...
==========================================================================

>>>>HELP ME!!!

When asking for help you need to state right out of the gate, "TALK"....

*Tell if you have mods in the game, or not, and what kind of mods.

This information is important because this will determine what kind of help you will get. If it is just the default/vanilla game, then any stalker here can help. If it is a mod, there are stalkers that can help, and some of them are part of the modding community, and even maybe responsible for the mod your having issues with.. This is why the information is important..

-Tell what kind of system do you have.

If you meet the requirements for the game, then this information will not be needed, but the OS type maybe needed.

*Laptop players, if your having issues but your system meets the requirements, even though all three can work off 2 gigs, keep in mind, your graphics adapter requires the use of the system memory to make it work. So if it is a 512mb video memory, it will be using 512mb of the system memory. It is the nature of the beast with laptops. You will need to either added the extra memory yourself, or send it in to the shop for it.

*Celeron CPU's and variants of this type of CPU may not work well either. They are not gamming made. It is a cheap CPU with only one thing in mind, get you online and something to use. Older games tend to mistaken this as a old Pentium 133Mhz CPU, in short a old CPU that can run WIN95. CPU's that are real Pentium's or equal to this type of CPU such as AMD, will run the game better.

Mod conflicts are the result of one mod over writing another if they use the same files. A mod merger is NOT a "in file writing tool". It will NOT write in the changed lines into the other file. "Mod Mergers" just basically copy into the directory like drag and copy in windows explorer. YOU have to go through the separate files between the mods to determine if they are using the same files or not. There is no way around it...

*dbase file mods tend to use a exe file and is written into the game's main dbase files or added or both, and can not be viewed. So if you are using a different mod, you will have to uninstall the game completely, then find the games main directory and delete it yourself. Steam tends not to do this because there are unknown files inside that are not part of it's registry when it checks it for uninstall. These games are commonly found in...

-->Program Files(x86)\Steam\steamapps\common\Stalker Call of Pripyat

-->Program Files(x86)\Steam\steamapps\common\STALKER Clear Sky

-->Program Files(x86)\Steam\steamapps\common\STALKER Shadow of Chernobyl

Uninstall the game first and then go back to delete the game directory if it is present..

Why the exe install? In SOC, gamedata mods caused the game to load slow on newer OS's such as WIN7, WIN8, WIN10, taking forever to bind and ready the game. The exe install was direct to the dbase, making the loading time faster. You can still use the gamedata, it will just take a bit of time to load.

Sometimes a mod can be too big for the game to bind to the dbase information, and cause it to run out of memory. All S.T.A.L.K.E.R. games are 32bit games. There for are limited to 4gigs to use between the system memory and the page file.

>>>>The due processes of Gamedata mods and errors...

The gamedata mods is were you can view what is what. And you need to put it in the directory..

-->Program Files(x86)\Steam\steamapps\common\Stalker Call of Pripyat\gamedata

-->Program Files(x86)\Steam\steamapps\common\STALKER Clear Sky\gamedata

-->Program Files(x86)\Steam\steamapps\common\STALKER Shadow of Chernobyl\gamedata

These kind of mods can be easy to resolve if something happens, other time can not. Sometimes player will mix a mod that dose a rewrite over a existing file, and causes the crash. What makes it easer is if it is something simple, then you can look into it yourself and see what was the cause through the debugger and the file location.

If it is using the same file, a advanced user can see if they determine that...

-A walk around can fix the problem..

-They can see they can add in the missing lines from one script to another or ltx files.

A walk around is were you do a fix that makes the game work. Mods can be very complex, and simple walk around maybe all you need. And some problems are bonded in the script with errors that the mod can not be fix, it requires for the Modder to do it. Some walk around can be simple enough that it can.

-Example..

The debugger says it can not find a certain NPC. You look at the name of the NPC in the debugger, go into the Mesh directory to the NPC faction folder that the debugger says it is suppose to be at, and see if it is there. If it is there, make sure the spelling is the same as the folder and the debugger. If it is misspelled. Then rename the NPC mesh the same name the debugger is looking for. It doesn't matter which one maybe wrong or right. The game is running, and what it is looking for is what is important. Go back into the game, the game will play. This action will not cause a restart for a new game because it already is looking for a mesh file, and just stop because it was missing. Nothing more.

The debugger says a animation is missing from a weapon file. You must go into the weapon name mesh to see if it exist. If it dose, you must check the ltx file to see if that mesh the debugger claims to be missing is in the weapon's ltx file, if that line is there, but disabled, you will have to re-enable it, and maybe start a new game. If it still crash with the same claim, the file mesh was taken from one of the other S.T.A.L.K.E.R. games and is not supported in the one your playing, it is programed wrong or it is corrupted.

To resolve this is done in two ways....

One way is to disable the gun, it will have to be done in all files that use this gun. I personally re-do load outs for all stalker characters. So if I do this, other Modders do this too. So you would have to go through all the existing files for that. And this can get messy if the weapon with the issue can also be a quest item..

The other way is just do a quick change in the existing file so the game can run the mod. For example, lets say this is a rifle, delete everything in the file but leave the rifle property name.

[wpn_problem_Rifle]:identity_immunities,weapon_probability,default_weapon_params

Go to another rifle file and use that settings, for example the svd, select everything, but not the property name, just everything after that, then past it in the wpn_problem_Rifle ltx file. Then set the property name so it can work..

[wpn_problem_Rifle]:wpn_svu

(Svd configurations)

This might require a new game start, now the rifle should work. in the game the name will be listed as the problem rifle, but really it will be a svd. It doesn't matter now if you will use it or not, what matters is now the game will play. If your a advanced user you probably can do more with it..

*Remember, when dealing with mods, they have to be in the specific directory that they came in. This is how the game reads....

-It checks first for mods, then checks for errors at start and prepares to bind the mod to the dbase files and starts the server..

-Once the sort is done, the server is started, and the mod is bonded, it begins the game build, and spawns everything.

-the game is running...

-If there is a error that was not discovered at start, it will be found once that is triggered.

-once the error is triggered, the debug will go active and display the issue that caused it to stop.

*If the script issue is that complex and even as a advance user, you can not solve it, leave, go to the download sight and past the error message there so the Modder can resolve this. The Modder may past back instructions on what to do to get around this, and this can be very helpful if it is a mod that the Modder cares about, The Modder will make a patch for it..
============================================================

It is a very simple tool, it automatically debugs and writes the reason to the clip board memory. You do not have to do anything or copy anything, it is all automatic. Once the game has crashed, open a text editor like notepad, and go to -> Edit and -> select paste. Or use Ctrl+V and the information will past. ALL S.T.A.L.K.E.R. games in the series do this for developer debugging.

==========================================================================
->Example...

Expression : fatal error
Function : CScriptEngine::lua_error
File : E:\stalker\sources\trunk\xr_3da\xrGame\script_engine.cpp
Line : 73
Description : <no expression>
Arguments : LUA error: ...ow of chernobyl\gamedata\scripts\bind_stalker.script:57: attempt to call field 'uptabc' (a nil value)
--------------------------------------------------------------------------------------------------------------------------

->What this means...

Expression : fatal error <--The result

Function : CScriptEngine::lua_error <- the module that was processing..

File : E:\stalker\sources\trunk\xr_3da\xrGame\script_engine.cpp <-The engine that was processing at the time (E is a virtual drive...)

Line : 73 <- the line that was working with in the X-ray main files....

Description : <no expression> <- something is missing..
--------------------------------------------------------------------------------------------------------------------------
Arguments : LUA error: ...ow of chernobyl\gamedata\scripts\bind_stalker.script:57: attempt to call field 'uptabc' (a nil value)

>>A command line run in the dbase or mod script could not call to the next or needed script file, so the needed script is nil or can not run.
--------------------------------------------------------------------------------------------------------------------------

Expression : wave&&wave->length()
Function : CSoundRender_Source::LoadWave
File : E:\priquel\sources\engine\xrSound\SoundRender_Source_loader.cpp
Line : 65
Description : Can't open wave file:
Arguments : c:\program files (x86)\steam\steamapps\common\stalker clear sky\gamedata\sounds\weapons\tooz34_shot.ogg
--------------------------------------------------------------------------------------------------------------------------

->What this means...

Expression : wave&&wave->length() <-controller that was effected

Function : CSoundRender_Source::LoadWave <- the module that was processing..

File : E:\priquel\sources\engine\xrSound\SoundRender_Source_loader.cpp <-The engine that was processing at the time (E is a virtual drive...)

Line : 65 <- the line that was working with in the X-ray main files....

Description : Can't open wave file: <- the file has a problem or it is missing..
--------------------------------------------------------------------------------------------------------------------------
Arguments : c:\program files (x86)\steam\steamapps\common\stalker clear sky\gamedata\sounds\weapons\tooz34_shot.ogg

>>>The location of the problem file that needs to be fixed/replaced/resolved..
--------------------------------------------------------------------------------------------------------------------------

Expression : fatal error
Function : CModelPool::Instance_Load
File : D:\prog_repository\sources\trunk\Layers\xrRender\ModelPool.cpp
Line : 117
Description : <no expression>
Arguments : Can't find model file 'actors\stalker_hero\stalker_heero_1.ogf'.
--------------------------------------------------------------------------------------------------------------------------

->What this means...

Expression : fatal error <--The result

Function : CModelPool::Instance_Load <- the module that was processing..

File : D:\prog_repository\sources\trunk\Layers\xrRender\ModelPool.cpp <-The engine that was processing at the time (D is a virtual drive...)

Line : 117 <- the line that was working with in the X-ray main files....

Description : <no expression> <- something is missing..
--------------------------------------------------------------------------------------------------------------------------
Arguments : Can't find model file 'actors\stalker_hero\stalker_heero_1.ogf'.

>>>The location of the problem file that needs to be fixed/replaced/resolved....
--------------------------------------------------------------------------------------------------------------------------

As you see in all three examples, what is important is the "Arguments" section. This is telling YOU what is wrong. Sometimes script files can be resolved pending on your knowledge of modding, but between the sound file and the model file, you will be able to fix it.

Usually a easy fix, is by copying a file that is equal to the one that needs to be fixed, and give it the same name that is listed in the debugger Arguments. And this will resolve it so you can move on in your life in the game.

Because the mistake is in a existing ltx file, and your fix is in the folder location for the sound or Mesh, a new game should not need to be needed. When adjusting fixes in the ltx file, this will usually result in starting a new game. This is because the information is saved in the save file and it effects everything, the actor (YOU), including NPCs, weather, levels, and AIlife zone animals, pending what that change is.. That is the way it is..

*If the page is blank or you get a "STACK TRACE" only, the CTD was bad enough the debugger could not debug the problem..

Also a "STACK TRACE" could mean you ran out of memory..

*Trader files are exempt from restarts only if your changes are applied what is to be sold or what is not to be sold and amount of that item.

==========================================================================

The default game may CTD when going to Yantar, because of a error that apperntly still exsist even in the newer verison update.. I even pointed this out to GSC a long, long time ago, and I can see it never got fixed still. The error is 3 ammo items are miss spelled for the Yantar trader, since the ammo dose not exsist, the game is attempting to open them because they are listed in the trader file as available. These are the error names..

ammo_11.5x70_buck
ammo_11.5x76_dart
ammo_11.5x76_zhekan

->They should be these names...

ammo_12x70_buck
ammo_12x76_dart
ammo_12x76_zhekan

Set your windows explorer option by unchecking the box for "Hide extensions for known file types" and hit ok..

go to -> Folder and search options -> Folder options -> veiw tab..

After you set that, then find the main game directory, it is located here...

Program Files (x86)\Steam\common\STALKER Clear Sky

In the clear sky look in the folder for this file..

fsgame.ltx

Open it useing a text editor and find this line..

$game_data$ = false| true| $fs_root$| gamedata\

Edit this by changing it to this..

$game_data$ = true| true| $fs_root$| gamedata\

Close and save.

*Make sure the OS didn't save it as -> fsgame.ltx.txt
-If it did, you have to correct the extention to -> fsgame.ltx (LTX)
---------------------------------------------------------------------------------------------------
In the main game directory create the fallowing folders..

->gamedata folder in side the Clear sky folder

Program Files (x86)\Steam\common\STALKER Clear Sky\gamedata

->configs folder inside the gamedata folder

Program Files (x86)\Steam\common\STALKER Clear Sky\gamedata\configs

->misc folder in the configs folder

Program Files (x86)\Steam\common\STALKER Clear Sky\gamedata\configs\misc

->and finally a trade folder in the misc folder...

Program Files (x86)\Steam\common\STALKER Clear Sky\gamedata\configs\misc\trade

->go in the trade folder, right click go to -> New -> Text Document. And rename it including the extention..

trade_saharov.ltx

-open with the text program like note pad to edit... Once open, in the next 2 post below, copy the fix and past it into your trade_saharov.ltx file you made.

-Save and make sure the extention was not changed by the OS to -> trade_saharov.ltx.txt

-> If it was, rename the extention back to -> trade_saharov.ltx..
==========================================================================

[trader]
buy_condition = trade_generic_buy
sell_condition = trade_generic_sell
buy_supplies = supplies_generic


[trade_generic_buy]
;Àðòåôàêòû
af_cristall = 0.8, 0.8
af_fireball = 0.8, 0.8
af_dummy_glassbeads = 0.8, 0.8
af_eye = 0.8, 0.8
af_fire = 0.8, 0.8
af_medusa = 0.8, 0.8
af_cristall_flower = 0.8, 0.8
af_night_star = 0.8, 0.8
af_vyvert = 0.8, 0.8
af_gravi = 0.8, 0.8
af_gold_fish = 0.8, 0.8
af_blood = 0.8, 0.8
af_mincer_meat = 0.8, 0.8
af_soul = 0.8, 0.8
af_fuzz_kolobok = 0.8, 0.8
af_baloon = 0.8, 0.8
af_glass = 0.8, 0.8
af_electra_sparkler = 0.8, 0.8
af_electra_flash = 0.8, 0.8
af_electra_moonlight = 0.8, 0.8
af_dummy_battery = 0.8, 0.8
af_dummy_dummy = 0.8, 0.8
af_ice = 0.8, 0.8

;Àììóíèöèÿ
ammo_9x18_fmj = 0.05, 0.05
ammo_9x18_pmm = 0.05, 0.05
ammo_9x19_pbp = 0.05, 0.05
ammo_9x19_fmj = 0.05, 0.05
ammo_11.43x23_hydro = 0.05, 0.05
ammo_11.43x23_fmj = 0.05, 0.05
ammo_12x70_buck = 0.05, 0.05
ammo_12x76_dart = 0.05, 0.05
ammo_12x76_zhekan = 0.05, 0.05
ammo_5.45x39_ap = 0.05, 0.05
ammo_5.45x39_fmj = 0.05, 0.05
ammo_9x39_sp5 = 0.05, 0.05
ammo_9x39_ap = 0.05, 0.05
ammo_9x39_pab9 = 0.05, 0.05
ammo_5.56x45_ss190 = 0.05, 0.05
ammo_5.56x45_ap = 0.05, 0.05
ammo_7.62x54_7h14 = 0.05, 0.05
ammo_7.62x54_7h1 = 0.05, 0.05
ammo_7.62x54_ap = 0.05, 0.05
ammo_og-7b = 0.05, 0.05
ammo_vog-25p = 0.05, 0.05
ammo_vog-25 = 0.05, 0.05
grenade_f1 = 0.05, 0.05
grenade_rgd5 = 0.05, 0.05
ammo_m209 = 0.05, 0.05
ammo_pkm_100 = 0.05, 0.05

;Îðóæèå
wpn_pm ;NO TRADE
wpn_pb ;NO TRADE
wpn_fort ;NO TRADE
wpn_hpsa ;NO TRADE
wpn_beretta ;NO TRADE
wpn_walther ;NO TRADE
wpn_sig220 ;NO TRADE
wpn_colt1911 ;NO TRADE
wpn_usp ;NO TRADE
wpn_desert_eagle ;NO TRADE
wpn_bm16 ;NO TRADE
wpn_toz34 ;NO TRADE
wpn_wincheaster1300 ;NO TRADE
wpn_spas12 ;NO TRADE
wpn_ak74u ;NO TRADE
wpn_mp5 ;NO TRADE
wpn_ak74 ;NO TRADE
wpn_abakan ;NO TRADE
wpn_l85 ;NO TRADE
wpn_lr300 ;NO TRADE
wpn_sig550 ;NO TRADE
wpn_groza ;NO TRADE
wpn_val ;NO TRADE
wpn_vintorez ;NO TRADE
wpn_svu ;NO TRADE
wpn_svd ;NO TRADE
wpn_rg-6 ;NO TRADE
wpn_rpg7 ;NO TRADE
wpn_g36 ;NO TRADE
wpn_fn2000 ;NO TRADE
wpn_pkm ;NO TRADE

;ADDONS
wpn_addon_scope ;NO TRADE
wpn_addon_scope_susat ;NO TRADE
wpn_addon_silencer ;NO TRADE
wpn_addon_grenade_launcher ;NO TRADE
wpn_addon_grenade_launcher_m203 ;NO TRADE

;Áðîíèêè
novice_outfit = 0.5, 0.5
bandit_outfit = 0.5, 0.5
specops_outfit = 0.5, 0.5
military_outfit = 0.5, 0.5
stalker_outfit = 0.5, 0.5
scientific_outfit = 0.5, 0.5
exo_outfit = 0.5, 0.5
svoboda_light_outfit = 0.5, 0.5
svoboda_heavy_outfit = 0.5, 0.5
svoboda_exo_outfit = 0.5, 0.5
cs_light_outfit = 0.5, 0.5
cs_heavy_outfit = 0.5, 0.5
dolg_outfit = 0.5, 0.5
dolg_heavy_outfit = 0.5, 0.5

;Ìåäèêàìåíòû
bandage ;NO TRADE
medkit ;NO TRADE
medkit_scientic ;NO TRADE
medkit_army ;NO TRADE
antirad ;NO TRADE

;Åäà
bread ;NO TRADE
kolbasa ;NO TRADE
conserva ;NO TRADE
vodka ;NO TRADE
energy_drink ;NO TRADE

;Ïðåäìåòû
device_torch ;NO TRADE
detector_simple ;NO TRADE
detector_advanced ;NO TRADE
detector_elite ;NO TRADE
device_pda ;NO TRADE
hand_radio ;NO TRADE
guitar_a ;NO TRADE
harmonica_a ;NO TRADE

;Êâåñòîâûå ïðåäìåòû
af_compass ;NO TRADE
device_pda_fang ;NO TRADE
esc_trader_habar ;NO TRADE
device_pda_military ;NO TRADE
device_pda_old ;NO TRADE
device_pda_garbage_traitor ;NO TRADE
device_pda_comendant ;NO TRADE
device_pda_freedom ;NO TRADE
device_pda_bloodsucker ;NO TRADE
device_pda_digger ;NO TRADE
mar_quest_wpn_pm_1 ;NO TRADE
mar_quest_wpn_ak74u_1 ;NO TRADE
mar_quest_af_cristall_flower_1 ;NO TRADE
mar_quest_scout_pda ;NO TRADE
mar_quest_novice_outfit_1 ;NO TRADE
mil_quest_af_fuzz_kolobok ;NO TRADE
mil_device_pda_lost_squard ;NO TRADE
esc_device_pda_driver ;NO TRADE
esc_mechanic_flash_card_1 ;NO TRADE
esc_mechanic_flash_card_2 ;NO TRADE
esc_mechanic_flash_card_3 ;NO TRADE
esc_mechanic_flash_card_4 ;NO TRADE
agr_mechanic_pda ;NO TRADE
agr_pda_for_secret_trader ;NO TRADE
agr_map_animals ;NO TRADE
red_forest_pda_map ;NO TRADE
red_forest_pda_map_2 ;NO TRADE

;Óíèêàëüíûå ïðåäìåòû
wpn_ak74_up ;NO TRADE
wpn_ak74_up2 ;NO TRADE
wpn_abakan_up2 ;NO TRADE
wpn_colt1911_up2 ;NO TRADE
wpn_pm_up ;NO TRADE
wpn_pm_9x19 ;NO TRADE
wpn_lr300_up2 ;NO TRADE
wpn_fort_up ;NO TRADE
wpn_sig550_up2 ;NO TRADE
wpn_vintorez_up ;NO TRADE
stalker_outfit_up_stalk = 0.01, 0.01
wpn_pm_arena ;NO TRADE
wpn_mp5_arena ;NO TRADE
wpn_toz34_arena ;NO TRADE
wpn_spas12_arena ;NO TRADE
wpn_ak74_arena ;NO TRADE
wpn_bm16_arena ;NO TRADE
wpn_ak74u_arena ;NO TRADE
wpn_val_arena ;NO TRADE
wpn_groza_arena ;NO TRADE
wpn_fn2000_arena ;NO TRADE
wpn_g36_arena ;NO TRADE

;*********************************************************
;****************** generic sell *************************
;*********************************************************
[trade_generic_sell]
;Àðòåôàêòû
af_cristall ;NO TRADE
af_fireball ;NO TRADE
af_dummy_glassbeads ;NO TRADE
af_eye ;NO TRADE
af_fire ;NO TRADE
af_medusa ;NO TRADE
af_cristall_flower ;NO TRADE
af_night_star ;NO TRADE
af_vyvert ;NO TRADE
af_gravi ;NO TRADE
af_gold_fish ;NO TRADE
af_blood ;NO TRADE
af_mincer_meat ;NO TRADE
af_soul ;NO TRADE
af_fuzz_kolobok ;NO TRADE
af_baloon ;NO TRADE
af_glass ;NO TRADE
af_electra_sparkler ;NO TRADE
af_electra_flash ;NO TRADE
af_electra_moonlight ;NO TRADE
af_dummy_battery ;NO TRADE
af_dummy_dummy ;NO TRADE
af_ice ;NO TRADE

;Àììóíèöèÿ
ammo_9x18_fmj = 1.2, 1.2
ammo_9x18_pmm ;NO TRADE
ammo_9x19_pbp ;NO TRADE
ammo_9x19_fmj = 1.2, 1.2
ammo_11.43x23_hydro ;NO TRADE
ammo_11.43x23_fmj = 1.2, 1.2
ammo_12x70_buck = 1.2, 1.2
ammo_12x76_dart = 1.2, 1.2
ammo_12x76_zhekan = 1.2, 1.2
ammo_5.45x39_ap = 1.2, 1.2
ammo_5.45x39_fmj = 1.2, 1.2
ammo_9x39_sp5 ;NO TRADE
ammo_9x39_ap = 1.2, 1.2
ammo_9x39_pab9 = 1.2, 1.2
ammo_5.56x45_ss190 = 1.2, 1.2
ammo_5.56x45_ap = 1.2, 1.2
ammo_7.62x54_7h14 = 1.2, 1.2
ammo_7.62x54_7h1 = 1.2, 1.2
ammo_7.62x54_ap ;NO TRADE
ammo_og-7b ;NO TRADE
ammo_vog-25p ;NO TRADE
ammo_vog-25 = 1.2, 1.2
ammo_pkm_100 = 1.2, 1.2
grenade_f1 = 1.2, 1.2
grenade_rgd5 = 1.2, 1.2
ammo_m209 ;NO TRADE
ammo_pkm = 1.2, 1.2

;Îðóæèå
wpn_pm ;NO TRADE
wpn_pb ;NO TRADE
wpn_fort ;NO TRADE
wpn_hpsa ;NO TRADE
wpn_beretta ;NO TRADE
wpn_walther ;NO TRADE
wpn_sig220 ;NO TRADE
wpn_colt1911 ;NO TRADE
wpn_usp ;NO TRADE
wpn_desert_eagle ;NO TRADE
wpn_bm16 ;NO TRADE
wpn_toz34 ;NO TRADE
wpn_wincheaster1300 ;NO TRADE
wpn_spas12 ;NO TRADE
wpn_ak74u ;NO TRADE
wpn_mp5 ;NO TRADE
wpn_ak74 ;NO TRADE
wpn_abakan ;NO TRADE
wpn_l85 ;NO TRADE
wpn_lr300 ;NO TRADE
wpn_sig550 ;NO TRADE
wpn_groza ;NO TRADE
wpn_val ;NO TRADE
wpn_vintorez ;NO TRADE
wpn_svu ;NO TRADE
wpn_svd ;NO TRADE
wpn_rg-6 ;NO TRADE
wpn_rpg7 ;NO TRADE
wpn_g36 ;NO TRADE
wpn_fn2000 ;NO TRADE
wpn_pkm ;NO TRADE

;ADDONS
wpn_addon_scope ;NO TRADE
wpn_addon_scope_susat ;NO TRADE
wpn_addon_silencer ;NO TRADE
wpn_addon_grenade_launcher ;NO TRADE
wpn_addon_grenade_launcher_m203 ;NO TRADE

;Áðîíèêè
novice_outfit ;NO TRADE
bandit_outfit ;NO TRADE
specops_outfit = 1.1, 1.1
military_outfit = 1.1, 1.1
stalker_outfit ;NO TRADE
scientific_outfit = 1.1, 1.1
exo_outfit ;NO TRADE
svoboda_light_outfit ;NO TRADE
svoboda_heavy_outfit ;NO TRADE
svoboda_exo_outfit ;NO TRADE
cs_light_outfit ;NO TRADE
cs_heavy_outfit ;NO TRADE
dolg_outfit ;NO TRADE
dolg_heavy_outfit ;NO TRADE

;Ìåäèêàìåíòû
bandage = 1, 1
medkit = 1, 1
medkit_scientic = 1, 1
medkit_army = 1, 1
antirad = 1, 1

;Åäà
bread ;NO TRADE
kolbasa ;NO TRADE
conserva ;NO TRADE
vodka ;NO TRADE
energy_drink ;NO TRADE

;Ïðåäìåòû
device_torch ;NO TRADE
hand_radio ;NO TRADE
detector_simple = 1.1, 1.1
detector_advanced = 1.1, 1.1
detector_elite = 1.1, 1.1
device_pda ;NO TRADE
guitar_a ;NO TRADE
harmonica_a ;NO TRADE

;Êâåñòîâûå ïðåäìåòû
af_compass ;NO TRADE
device_pda_fang ;NO TRADE
esc_trader_habar ;NO TRADE
device_pda_military ;NO TRADE
device_pda_old ;NO TRADE
device_pda_garbage_traitor ;NO TRADE
device_pda_comendant ;NO TRADE
device_pda_freedom ;NO TRADE
device_pda_bloodsucker ;NO TRADE
device_pda_digger ;NO TRADE
mar_quest_wpn_pm_1 ;NO TRADE
mar_quest_wpn_ak74u_1 ;NO TRADE
mar_quest_af_cristall_flower_1 ;NO TRADE
mar_quest_scout_pda ;NO TRADE
mar_quest_novice_outfit_1 ;NO TRADE
mil_quest_af_fuzz_kolobok ;NO TRADE
mil_device_pda_lost_squard ;NO TRADE
esc_device_pda_driver ;NO TRADE
esc_mechanic_flash_card_1 ;NO TRADE
esc_mechanic_flash_card_2 ;NO TRADE
esc_mechanic_flash_card_3 ;NO TRADE
esc_mechanic_flash_card_4 ;NO TRADE
agr_mechanic_pda ;NO TRADE
agr_pda_for_secret_trader ;NO TRADE
agr_map_animals ;NO TRADE
red_forest_pda_map ;NO TRADE
red_forest_pda_map_2 ;NO TRADE

;Óíèêàëüíûå ïðåäìåòû
wpn_ak74_up ;NO TRADE
wpn_ak74_up2 ;NO TRADE
wpn_abakan_up2 ;NO TRADE
wpn_colt1911_up2 ;NO TRADE
wpn_pm_up ;NO TRADE
wpn_pm_9x19 ;NO TRADE
wpn_lr300_up2 ;NO TRADE
wpn_fort_up ;NO TRADE
wpn_sig550_up2 ;NO TRADE
wpn_vintorez_up ;NO TRADE
stalker_outfit_up_stalk ;NO TRADE
wpn_pm_arena ;NO TRADE
wpn_mp5_arena ;NO TRADE
wpn_toz34_arena ;NO TRADE
wpn_spas12_arena ;NO TRADE
wpn_ak74_arena ;NO TRADE
wpn_bm16_arena ;NO TRADE
wpn_ak74u_arena ;NO TRADE
wpn_val_arena ;NO TRADE
wpn_groza_arena ;NO TRADE
wpn_fn2000_arena ;NO TRADE
wpn_g36_arena ;NO TRADE

-Before you blame it on the default/vanilla game, tell the whole deal, are you using a mod? If you don't, you won't get help, us stalkers are not being rude, it is just we do not read minds...

-Some mods may conflict with other mods because they are using the same files..

-Some times regardless what is said, some mods may cause a problem, and others do not, it is what it is..

-Some errors is the result of the game not binding them right..

-did you try to check the compatibility and admin rights on your newer OS? On some system you may need to..

-On some system may run into a resolution setting problem, and may have to lower your fancy graphics card down. Majority do not.

-If the mod is not binding right, are all the folders in the right spot? Did you set the root gamedata string in the fsgame.ltx file?
--------------------------------------------------------------------------------------------------------------------------

Location to were the gamedata will go, in the game directory folder....


-->Program Files(x86)\Steam\steamapps\common\Stalker Call of Pripyat\

-->Program Files(x86)\Steam\steamapps\common\STALKER Clear Sky\

-->Program Files(x86)\Steam\steamapps\common\STALKER Shadow of Chernobyl\

--------------------------------------------------------------------------------------------------------------------------

Location of the fsgame.ltx file, inside the main game directory folder...


-->Program Files(x86)\Steam\steamapps\common\Stalker Call of Pripyat\fsgame.ltx

-->Program Files(x86)\Steam\steamapps\common\STALKER Clear Sky\fsgame.ltx

-->Program Files(x86)\Steam\steamapps\common\STALKER Shadow of Chernobyl\fsgame.ltx

--------------------------------------------------------------------------------------------------------------------------

>>>>Use a text editor and find this string..

$game_data$ = false| true| $fs_root$| gamedata\

>>>>and change it to this..

$game_data$ = true| true| $fs_root$| gamedata\

--------------------------------------------------------------------------------------------------------------------------

To see the extensions you will need to go to -> Folder options -> View tab -> and uncheck "Hide extensions for known file types". This way if you change things in a ltx file or script, and your OS will not try to save it as a txt extension for text file. If it does, rename the extention back.

Example

m_poltergeist.ltx.txt

This file will never work, the game will use the dbase file instead.


>>>It has to be this for the game to use it in the mod instead...

m_poltergeist.ltx

--------------------------------------------------------------------------------------------------------------------------
If you want to know what mods are the best to use, go ahead and ask on the fourms!


I hope this helps you in any way..Thank you..

==========================================================================

-Steam versions for those who are intressted, will work with the old data unpackers for the older version on retail DVD...

-->SOC dbase extractor --> STALKER_Data_Unpacker.zip
Has both English version and Russian version...

--> Clear Sky AND Call Of pripyat --> stalker_CS_unpacker.zip or stalker_CS_COP_unpacker.zip
This is pending on the name. either will work regardless..

*When useing the SOC extractor you must create a new folder and have it unpack to there.

Example:

Program Files(x86)\Steam\steamapps\common\STALKER Shadow of Chernobyl\unpack

Unpacking it directly in the SOC main game folder will just make a mess and might over write exsisting files..

*The CS\CS_COP\ is one of the same and will unpack both. It will create its own unpack directory. Just unzip, and copy the folder holding the needed unpacking files into the directory and then click on the bat file. everything else is automaticly..

Example:

Program Files(x86)\Steam\steamapps\common\STALKER Clear Sky\unpacker\CS_COP_unpack.bat or CS_unpack.bat

Program Files(x86)\Steam\steamapps\common\Stalker Call of Pripyat\unpacker\CS_COP_unpack.bat or CS_unpack.bat

-->These extractor are "back in the day" before any of these games were on steam. But you should still be able to find them. If you happen to find it, and it is in good copy. Burn it to a CD. I have alot of old Stalker tools burned to CD and DVD including my faveriot mods..

===========================================================================

-There has been complaints that the Misery mod for COP tends to mess up save files, to resolve this the user Martial.Lore in one post has suggested, do not quick save, but only manual/hard saves..

===========================================================================