Posts by paies

    Don't worry about it, though I appreciate the effort ^ ^. -I found out the cause, and I suspect your files would have the exact same corruption in them (Specifically, chance values being set to null values), so the worst of the issues should be slain. ..At least for a little while >->;

    As Promised, google drive finally decided to update, Pre 2.2.1 and pre latest AI update, maybe this will shine some light on some issues ;p

    GoogleDriveHere

    Fin added a new version:

    Fin

    So it's been a few days, google drive still hasn't updated the space, I will still pass it to you just for you to see probably out of curiosity :p

    I haven't yet played the new version, but hopefully all of the issues are gone.

    Cheers Fin

    Sure! I will do my best and see where I can upload it.

    And Not quite, last time I tested the durability I didn't actually get into a raid - Just saw if I get any errors in the console so technically - the first time I started the raids that's the error I got.

    I will edit this when I get all the things you needed.

    So, with the 1.22.1b it seems it absolutely borked my game, it doesn't launch and I believe the server crashes as it becomes unresponsive (not in task manager but just no pings, no updates nothing) Although only second try after.
    On the first try it overloaded the server with errors along the lines of (didn't catch it in time and I thought I could replicate it apologise):ERROR: "mod_muzzle".

    after the second relaunch the game just freezes after starting it, leaving you stuck on the game menu screen with "Tarkov Beta(0)" Bottom left and not progressing since I imagine the server is by all means dead.

    Removing the 1.22.1b seems to fix the issue and everything goes back to normal.

    Re-adding the same (which broke the server) 1.22.1B results in the server freezing once more. (I will upload it)

    Google drive for (hopefully not) Future de-bugging: (I will add it when my google space updates)

    I heard from someone recently that the errors are being caused by 'null' tpls. -If you see an error message like that, I'd love to have that confirmed.

    As promised!

    And I believe... this is quite the bigger issue than I expected so big indeed, that it's endless example:


    Day time factory, not a singular AI spawned. Hash:

    Customs same story:

    And hey if you find it easier you can DM me on Discord, you will also get a faster reply from me there :p
    paies12 | MiceGang#9406

    Cheers for lighting fast response!

    Yep and completely my bad, I missread the instruction as well and changed the wrong False to true etc.

    From the Bot generation it seems the weapons are nice and 100 again!

    Although I'm seeing some minor warnings about magazines (most likely modded weapons)
    Examples:

    Updated Hash:

    Tomorrow I will check if the weaponless bug persist for some bots, most likely it's SamSWAT weapons.

    Cheers once more!

    Hey Fin!

    Fast bug check!
    Durability weapon values still seem to be ignored (Unless I'm a complete buffoon and looking at the wrong thing):

    Hash:

    Config: config - Copy.txt

    Cheers and bless your patience!

    Hey Fin!

    God I must be slowly annoying with the amount of issues I'm having.

    As of 1.21.1,
    I'm getting the error of:

    Followed by a very long list of Warnings, Example:


    Base settings nothing changed in the Config, completely re-added the mod and removed the old version.

    Cheers once more for doing gods work!


    Hey Fin!
    To put it down more properly with screenshot and everything.
    Here's the:
    1. Backup config (which is my base config 100% saved and applied to the game) backupConfig - Copy.txt
    2. Screenshot proof as lame as it sounds for PMC weapons not being in their appropriate durability range (70-100 + Current 70-100).
    3. The mod list.

    Cheers for the amazing work as your AI mod helps the SP being much better!
    If you need anything else please feel free to ask.

    Have a nice day :)