[CoD2] Install CoD2 on your VDS much faster!

[Lonsofore]

PARAMS="+set fs_homepath $HOME/.callofduty2_$ver Created but -bash: cd: /home/userme/.callofduty2_1_2: No such file or directory

+set fs_game $srv_fs

my $srv_fs : fs_game_dosya2 -> /home/userme/cod2/servers/fs_game_dosya2

-bash: cd: /home/userme/cod2/servers/fs_game_dosya2: No such file or directory


what is for fs_homepath and +set fs_game ?

Well... fs_homepath is a home path of your server. You can find there console log and you can create there some files. Useless place, if you're beginner (or just don't use files lol).
fs_game is a path of your mod, where you should have your server cfg and your mod folders (like maps/mp/gametypes).

In this case you had to upload your mod to the server, and as I see, you did it. So, this path (/home/userme/cod2/servers/fs_game_dosya2) should be in your .sh file (instead $srv_fs).

[sezing]

Well... fs_homepath is a home path of your server. You can find there console log and you can create there some files. Useless place, if you're beginner (or just don't use files lol).
fs_game is a path of your mod, where you should have your server cfg and your mod folders (like maps/mp/gametypes).

In this case you had to upload your mod to the server, and as I see, you did it. So, this path (/home/userme/cod2/servers/fs_game_dosya2) should be in your .sh file (instead $srv_fs).

is this script for only ubuntu 14.04 ?

i tried on 14.04 everything is working. However on my 16.06 server is not working. i had to download Latest cod2 linux binaries from Mitch then it worked.

i liked the idea enable cracked 1-0.

can original user join my server if i use Mitch cod2 linux binaries?

[Lonsofore]

is this script for only ubuntu 14.04 ?

i tried on 14.04 everything is working. However on my 16.06 server is not working. i had to download Latest cod2 linux binaries from Mitch then it worked.

I haven't tried it with other versions, so I wrote 14.04 only. I wanna try it on 16.04 soon, so I'll write about it after.

[voron00]

You don't need to use any custom binaries, just use libcod +sv_cracked 1 or sv_noauthorize 1.

[sezing]

You don't need to use any custom binaries, just use libcod +sv_cracked 1 or sv_noauthorize 1.

i was using libcod +sv_cracked 1 but couldnt join the server.

[voron00]

Old versions of libocd does not registering custom cvars, use my version or use +set sv_cracked 1.

[Lonsofore]

A big update.

- Now you can use Ubuntu 16.04 aswell
- Edited .torrent file - removed iw_01, iw_02 (it's just for SP). Now it's just 1.8G for all versions.
- Now you can migrate from your old host (you can move your all fs_game, maps from Library, mysql, libcod files). Only if your last server was also installed with this cod2install!
- chmod +x is now default for start.sh, so you don't have to write it after clone
- A lot of small fixes

One time I should make a tutorial - how to use it. Because as I think, a lot of users don't even know, what is fs_game, Libruary, etc.

[CaptainSlow]

Great stuff! Keep up the good work

[vesicant]

Thanks for the response. I was expecting that error too! But I think that the localization files might be treated differently clientside.

Intuitively, this makes sense. If the game didn't have special handling in place for localization files, then players with e.g. `localized_german` IWDs wouldn't be able to connect to servers running with `localized_english`.

Try it. Host a remote server with the `localized_english` IWDs removed and try to connect to it. In my experience, everything works just fine.

On the client, your console will show something like this:

Current language: english
Current search path:
E:\COD2\main\iw_15.iwd (85 files)
    on the pure list
E:\COD2\main\iw_14.iwd (4038 files)
    on the pure list
E:\COD2\main\iw_13.iwd (22624 files)
    on the pure list
E:\COD2\main\iw_12.iwd (1016 files)
    on the pure list
E:\COD2\main\iw_11.iwd (1462 files)
    on the pure list
E:\COD2\main\iw_10.iwd (1936 files)
    on the pure list
E:\COD2\main\iw_09.iwd (2142 files)
    on the pure list
E:\COD2\main\iw_08.iwd (2723 files)
    on the pure list
E:\COD2\main\iw_07.iwd (3384 files)
    on the pure list
E:\COD2\main\iw_06.iwd (990 files)
    on the pure list
E:\COD2\main\iw_05.iwd (928 files)
    on the pure list
E:\COD2\main\iw_04.iwd (698 files)
    on the pure list
E:\COD2\main\iw_03.iwd (26 files)
    on the pure list
E:\COD2\main\iw_02.iwd (40 files)
    not on the pure list
E:\COD2\main\iw_01.iwd (16 files)
    not on the pure list
E:\COD2\main\iw_00.iwd (102 files)
    on the pure list
E:\COD2/main
E:\COD2/raw
E:\COD2/raw_shared
E:\COD2/devraw
E:\COD2/devraw_shared
E:\COD2\main\localized_english_iw11.iwd (1 files)
    localized assets iwd file for english
    not on the pure list
E:\COD2\main\localized_english_iw10.iwd (414 files)
    localized assets iwd file for english
    not on the pure list
E:\COD2\main\localized_english_iw09.iwd (98 files)
    localized assets iwd file for english
    not on the pure list
E:\COD2\main\localized_english_iw08.iwd (8 files)
    localized assets iwd file for english
    not on the pure list
E:\COD2\main\localized_english_iw07.iwd (1014 files)
    localized assets iwd file for english
    not on the pure list
E:\COD2\main\localized_english_iw06.iwd (3110 files)
    localized assets iwd file for english
    not on the pure list
E:\COD2\main\localized_english_iw05.iwd (5310 files)
    localized assets iwd file for english
    not on the pure list
E:\COD2\main\localized_english_iw04.iwd (6240 files)
    localized assets iwd file for english
    not on the pure list
E:\COD2\main\localized_english_iw03.iwd (6580 files)
    localized assets iwd file for english
    not on the pure list
E:\COD2\main\localized_english_iw02.iwd (6404 files)
    localized assets iwd file for english
    not on the pure list
E:\COD2\main\localized_english_iw01.iwd (5510 files)
    localized assets iwd file for english
    not on the pure list
E:\COD2\main\localized_english_iw00.iwd (4764 files)
    localized assets iwd file for english
    not on the pure list

Note how the `localized_english` files are recognized as "localized assets iwd files" even though they are marked as impure.

Let's do a few experiments to better understand this behavior.

First, let's try renaming `localized_english_iw09.iwd` to something else. This is a good file to experiment with because it contains localized strings for multiplayer.

If you rename that file to `localized_blah_iw09.iwd`, you'll still be able to connect to your server (which is missing `localized_english` files), but you'll see the following error in the console:

WARNING: Localized assets iwd file E:\COD2/main/localized_blah_iw09.iwd has invalid name (bad language name specified). Proper naming convention is: localized_[language]_iwd#.iwd
Current language: english

Additionally, when you connect, most of the strings you see in the UI won't be localized:

cod2.jpg

Now, let's try renaming `localized_english_iw09.iwd` to `zzz_foo.iwd`.

Interestingly, you'll still be able to connect! Your UI text will still be broken. You'll see this error in the console:

E:\COD2\main\zzz_foo.iwd (98 files)
    not on the pure list

It looks like the game only loads `localizedstrings` files from IWD archives named after the current language.

Next, let's rename `localized_english_iw10.iwd` to `zzz_bar.iwd`. I want to test this because this IWD contains `images` and `materials`, including `loadscreen_toujane.iwi`, so it should be loaded when we connect to the server.

Now, we get the error you mentioned:

ERROR: Impure client detected. Invalid .IWD files referenced!
E:\COD2\main\zzz_bar.iwd

To me, this suggests that the game does not do pure checks for files that follow the `localized_[language]_iwd#.iwd` naming convention.

I'm guessing that it will only read specific types of files from localized asset IWDs, and ignore any other files in there. I'd have to do more testing to be sure.

Regardless, it seems like leaving out `localized_[language]` IWDs from your server should have no impact on your players. The COD2 client seems to treat these localized IWDs differently.