Page 4 of 4 FirstFirst ... 234
Results 31 to 39 of 39

Thread: [CoD2] Install CoD2 on your VDS much faster!

  1. #31
    Corporal voron00's Avatar
    Join Date
    Nov 2014
    Posts
    248
    Thanks
    64
    Thanked 216 Times in 116 Posts
    Old versions of libocd does not registering custom cvars, use my version or use +set sv_cracked 1.
    sudo apt-get rekt

  2. #32
    Private Lonsofore's Avatar
    Join Date
    Oct 2016
    Posts
    86
    Thanks
    82
    Thanked 38 Times in 25 Posts
    Quote Originally Posted by sezing View Post
    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.

  3. #33
    Private Lonsofore's Avatar
    Join Date
    Oct 2016
    Posts
    86
    Thanks
    82
    Thanked 38 Times in 25 Posts
    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.
    Last edited by Lonsofore; 26th February 2018 at 11:55.

  4. The Following User Says Thank You to Lonsofore For This Useful Post:

    kubislav23 (26th February 2018)

  5. #34
    Private CaptainSlow's Avatar
    Join Date
    Nov 2014
    Posts
    76
    Thanks
    38
    Thanked 26 Times in 21 Posts
    Great stuff! Keep up the good work
    Slow and Steady wins the race

  6. The Following User Says Thank You to CaptainSlow For This Useful Post:

    kubislav23 (22nd April 2018)

  7. #35
    ... connecting
    Join Date
    Jul 2013
    Posts
    1
    Thanks
    1
    Thanked 1 Time in 1 Post
    Lonsofore*

    You removed iw_01.iwd & iw_02.iwd.

    Remove localized files too and the servers will still start.

  8. The Following User Says Thank You to teufel For This Useful Post:

    kung foo man (17th March 2019)

  9. #36
    Private Lonsofore's Avatar
    Join Date
    Oct 2016
    Posts
    86
    Thanks
    82
    Thanked 38 Times in 25 Posts
    Quote Originally Posted by teufel View Post
    Lonsofore*

    You removed iw_01.iwd & iw_02.iwd.

    Remove localized files too and the servers will still start.
    Too late answer. I don't support this torrent and repo anymore because of my Docker version, so I highly recommend to use it instead.

    P.S. And we talked about localized two years ago here.

  10. The Following User Says Thank You to Lonsofore For This Useful Post:

    kung foo man (15th April 2022)

  11. #37
    ... connecting
    Join Date
    Jan 2018
    Posts
    5
    Thanks
    6
    Thanked 3 Times in 3 Posts
    Got some follow-up questions about localized strings. Sorry for the necrobump.

    Quote Originally Posted by IzNoGoD View Post
    Save over 1.5gig of disk space by replacing the localized_english 0-10 with this one file:Attachment 1344
    Thanks for sharing this. I have a few questions:

    1. Is it safe to rename this IWD? (Looking to shorten it.)
    2. If it is safe to rename, does it matter where it goes in the load order?
    3. Is it safe to make this IWD be server-side only?


    I think the answers are "yes", "not really", "yes", but I just want to check with someone who'd know better than me.

    If anyone stumbles on this thread while searching for info, for my server, I did the following:

    • Removed localized_english 0-10 from `main`
    • Kept `localized_english_iw11.iwd` in `main`
    • Put this file into a directory sibling to `main` that corresponds to my server's `fs_game`
    • Renamed this file to `zzz_svr_str.iwd` (`_svr_` keeps this file from being downloaded to the client)


    ...and everything seems to be working fine.

    Quote Originally Posted by teufel View Post
    Remove localized files too and the servers will still start.
    I tried this, too. Can confirm that the server starts. I saw the following error in the console:

    ERROR: No languages available because no localized assets were found
    From a previous thread, it seems that I should also be seeing this error:

    Couldn't load default_localize_mp.cfg
    However, I'm not seeing that error, and everything seems to run just fine. I'm running COD2 1.3; confirmed working without libcod.

    Does anyone know definitively if we need the localized IWDs on the server at all?

  12. The Following User Says Thank You to vesicant For This Useful Post:

    kung foo man (15th April 2022)

  13. #38
    Private Paho's Avatar
    Join Date
    Feb 2014
    Location
    Russia
    Posts
    92
    Thanks
    42
    Thanked 40 Times in 31 Posts
    Will result in an error: Unauthenticated client detected - invalid IWD files! path - All files on the server and on the client are compared. If some file is not in the mods or maps on the server to which you are connected, and which are cached somewhere (from somewhere a non-existent file is accessed), then the presence of it in the client in any other downloaded file from other servers will lead to conflict.

  14. The Following User Says Thank You to Paho For This Useful Post:

    kung foo man (15th April 2022)

  15. #39
    ... connecting
    Join Date
    Jan 2018
    Posts
    5
    Thanks
    6
    Thanked 3 Times in 3 Posts
    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:

    Code:
    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:

    Code:
    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:

    Code:
    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:

    Code:
    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.

  16. The Following User Says Thank You to vesicant For This Useful Post:

    kung foo man (15th April 2022)

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •