Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
As for the Bin folder, I would just re-name it like b_n and not deleate it. What if you dump the mod in and the bin folder that came with the mod conflicts with the games dbase files or something and won't run, Here you can delete the mod bin and data file and rename the old B_n to Bin..
That way you won't have to uninstall and re-install the entire game. Uninstalling will not remove the data file, and if the bin file uses edited dll's or exe's and dosen't reconize them, it will leave them behind too turning everything into a mess and only hope it will re-write it over. See what I am saying?
Also, about the other thread. If it's low shadow quality, how would I increase it?
Dose the readme file state what the game adds. Sometimes a mod will use its own bin file because the modder decomplied it to add other options to it. For example, SOC is written for vehicles, so all the vehicles that was available for the game will function properly, were COP dose not, so you can use a spawn mod to have the vehicles, but you need the bin file that has been edited to make the cars work, see what I am saying?
Now the bin folder is in the main SOC folder its self, remember to re-name it first before you drag and drop the mod version...