The Witcher 3
0 of 0

File information

Last updated

Original upload

Created by

Partoutatix and woodbyte

Uploaded by

woodbyte

Virus scan

Safe to use

92 comments

  1. woodbyte
    woodbyte
    • premium
    • 163 kudos
    Locked
    Sticky
    Updated with a small fix for GOG owners:

        - Fixed vanilla EP1 bundles not being used for 3-way merging on the GOG release.

    Please let us know if you experience any other issues.
  2. DontBlnkBadWolf
    DontBlnkBadWolf
    • premium
    • 37 kudos
    Locked
    Sticky
    For those that missed it, it says in the description that this mod is outdated. This patch has been included in the Official Script Merger as of v0.6.4. So this will NOT be updated. Update your Script Merger to v0.6.5, which is the current version.
  3. Kagezod
    Kagezod
    • member
    • 0 kudos

    After it, the merge "game/gui/main_file" ceased to be displayed
  4. Mustang052484
    Mustang052484
    • premium
    • 3 kudos
    Is this still needed for latest version of Script Merger? Anyone know?

    Edit ok nvm. It says for 0.6.2 - 0.6.3

  5. Arcameneled
    Arcameneled
    • supporter
    • 0 kudos
    Weird error running script merger in vortex:
    Invalid Load Order File
    Your mod.settings file is invalid
    Unrecognised Value on line 4
    VK= [THEN WHATEVER MY FIST MOD IS}

    Bare in mind it doesnt matter what i have installed or how many mods i have enabled it always says that line 4 is the problem
    1. Partoutatix
      Partoutatix
      • member
      • 196 kudos
      This is an example of what a mods.settings file looks like:

      [mod0000_MergedFiles]
      Enabled=1
      Priority=0

      [modunfixwhiteorchardsun]
      Enabled=1
      Priority=350

      [modZeBesserwisser]
      Enabled=1
      Priority=400

      [modlegolorefriendlierloot]
      Enabled=1
      Priority=300


      Vortex is not recommended for TW3, it will break things for you sooner or later.

      If your mods.settings file is broken/doesn't respect that format, try not running SM through vortex. Back up your mods.settings file (in your mydocuments\tw3) then delete it and reset a priority for a mod in SM so that it creates a new mods.settings file. If that doesn't work try reinstalling script merger, running it to be sure it's working, then patch it and run it to be sure it's working. You can also try setting mod priority through TW3MM (recommended instead of vortex).
    2. Partoutatix
      Partoutatix
      • member
      • 196 kudos
      Try this: https://www35.zippyshare.com/v/cvQn7bpW/file.html. Let me know if it works.
    3. Arcameneled
      Arcameneled
      • supporter
      • 0 kudos
      So the link doesnt work but ive stopped using vortex to try and mod witcher 3 anyway, just learned how to do it manually, thanks though
    4. Partoutatix
      Partoutatix
      • member
      • 196 kudos
      Apparently it was an issue introduced by the latest/testing version of Vortex. Both SM 0.6.3 and the unofficial patch 4 should fix it. There's also The Witcher 3 Mod Manager as an alternative to manual or Vortex installs.
    5. mcourtney89
      mcourtney89
      • supporter
      • 0 kudos
      Hi, I am having this same problem but I'm not running mod manager or script merger through vortex. I've followed everything step by step and it's just failing at this last part when I come to add mods. Quite frustrating as I'm a n00b and it took me about 2 hours to get to this point.

      I understand it could be an issue with a previous mod as it's saying the same as OP above but it is quoting 'overencumberedbegone' which is not currently in my mod directory path, but it is one that I previously tried to install via Vortex (before I uninstalled it and went the manual way).

      What's the best way for me to go about resetting the mods settings file? I saw you explained it already but as mentioned, this is all pretty new to me so I'm not sure I totally understand.

      Any help appreciated!
    6. thismusician586
      thismusician586
      • supporter
      • 0 kudos
      Same, I'm not using vortex - still having this issue.
    7. FawkingDeathHimself
      FawkingDeathHimself
      • supporter
      • 1 kudos
      This method works for me. What I did was, resolved all conflicts then exit Witcher Script Merger, then delete mods.settings file inside mydocuments\tw3 and re-run the Witcher Script Merger and thats it, no more "Unrecognised Value on line 4". Thanks man!
    8. exploiteddna
      exploiteddna
      • premium
      • 106 kudos
      funny i only get this error when i run SM through "Witcher 3 Mod Manager" .. it seems the mod manager does not add the VK= value to the mods.settings file, but vortex does. And when you run SM through vortex, no error. But running it through W3MM, you do get this error... At least, thats been my experience. But it doesnt seem to affect anything.. just click "ok" and move on.. everything still seems to work

      On a different note, I was recently told that this patch is no longer required.. that v0.6.5 has integrated these changes and so using this is redundant. Is that true?
    9. bigdlah
      bigdlah
      • premium
      • 0 kudos
      Hi guys I  have the  same issue. not using vortex, dont  even have it installed. any known fixes? 
    10. starlo4
      starlo4
      • member
      • 0 kudos
      This totally fixed my problem, thank you! I think Vortex left a little holdover in the mods.settings file that was stopping proper merging.
    11. lucas182
      lucas182
      • premium
      • 14 kudos
      just delete all "Vk=blablabla" lines and save
    12. Tylerdrakes123
      Tylerdrakes123
      • member
      • 0 kudos
      It worked thx :)
  6. TJfisher25874
    TJfisher25874
    • supporter
    • 0 kudos
    This mod is complete garbage, since vortex basically forces you to use it and prevents any mods from working regardless if you use vortex or not. I had zero problems with installing any mods for THW3 about a year ago when the show came out. Yet now that I have returned script manager is just automatically installed and fucks everything up. I dont feel like spending unnecessary time fighting script merger to play the game with simple and small mods when I have already played the s#*! out of the vanilla game on multiple platforms. f*#@ YOU SCRIPT MERGER!!!
    1. dtrail
      dtrail
      • premium
      • 79 kudos
      You are aware of that this is only a patch that requires the main script merger, right? Also for Witcher modding I woudln't recommend Vortex at all, because it WILL break things for sure - regardless of Script Merger! Inform yourself before blaming other people for your own mistakes.
    2. deleted34106890
      deleted34106890
      • account closed
      • 16 kudos
      It's always these Vortex users who cry the loudest. I wonder why lol.

      Here's a protip for you guys: Install mods for w3 manually, you'll have less problems :P
    3. BIGMOMMAPRODS
      BIGMOMMAPRODS
      • member
      • 0 kudos
      Always worked great for me. Oh well
  7. Matejka11
    Matejka11
    • member
    • 0 kudos
    hi i have this errors :
    Error [mod0000_mergedfiles]game\gameplay\damage\damagemanagerprocessor.ws(24): syntax error, unexpected TOKEN_CLASS, expecting '{', near 'class'
    Error [mod0000_mergedfiles]game\player\playerwitcher.ws(8800): Found unexpected '}'
    Error [mod0000_mergedfiles]game\player\playerwitcher.ws(11658): Found unexpected '}'

    can somone help :c pls
  8. theunknownisme
    theunknownisme
    • premium
    • 0 kudos
    Will there be an update for 0.6.5?
  9. KayLaFlare
    KayLaFlare
    • member
    • 0 kudos
    So it's outdated or what ? damn
  10. deleted52278411
    deleted52278411
    • account closed
    • 1 kudos
    Is this still needed for the latest version of script merger?
    1. Partoutatix
      Partoutatix
      • member
      • 196 kudos
      Don't think so.
  11. AlexBraidwood
    AlexBraidwood
    • member
    • 0 kudos
    I'm shocked I didn't hear about this update sooner. Single handedly fixed my game. Endorsed.
  12. Qaz182
    Qaz182
    • supporter
    • 0 kudos
    Packing merged bundle is an infinite loop that never ends
    1. Partoutatix
      Partoutatix
      • member
      • 196 kudos
      Alt+tab to kdiff3.