-
Posts
23 -
Joined
-
Last visited
Everything posted by SP3CNAZ
-
Hi. The "mod0BiA_FAP_Patch.zip” was added to the collection as "Bundled Asset" so that's why there is warning, just ignore it - it works fine. Regarding the installation, do you have any red notification, if so, can you show?
-
I like the new design the only thing I would change is to minimize everything.
-
Hello @Nagev @insomnious @Pickysaurus My Vortex issues: 1. Failed to upload to API. I wanted to post a new collection but I keep getting the error posted below with the path to the javascript in the Vortex files. I have never had this before what should I do to fix it? 2. Witcher modding. There has been a lot of bad stuff going on with Vortex lately when it comes to W3 modding, first the issue of my collection users: Installing the collection goes fine, all mods install correctly but when you close Vortex and later come back to it it shows this window: “Mods have been changed on disk... Modifying the staging folder is strongly discouraged”. The problem is that users do not touch the mod staging folder.... So you are left with one option, to apply changes in this window which causing all mods removal. Users are furious about this, they pay for Premium and Vortex does these things. 2.1. Adding/removing new mods - bad impact on the load order file. After the recent Vortex updates, deleting/adding a new modification to Vortex causes a complete reset of the mod loading order. This is very annoying, I have to replace this file with my mods.settings (manually set) everytime i made some changes in Vortex. I am hoping for a quick respond.
-
Yes, now installs correct. Thanks @insomnious & @Nagev
-
Any response?
-
Vortex installs wrong, mods packed like this one: Restored High Quality Weather Icons and Moon Phases MOD FILE CONTENTS: High Quality Weather Icons-7558-1-1-1672958308.zip mods modHighQualityWeatherIcons The mod is packed in the “mods” folder and Vortex installs it with this folder, which is wrong - should only install “modHighQualityWeatherIcons” to: The Witcher 3 Wild Hunt/Mods Hope for a quick fix! @insomnious @Nagev
-
This is an ss from a user of my collection, I don't know which versions. Why are you asking? Is it already fixed in latest Witcher extensions?
-
@insomnious Another thing that should be fixed - the Next Gen version does not need a "Mod Limit Patch", because the developers of the game added it when the Next Gen version was released, so it is completely unnecessary.
-
Thanks for fixes @insomnious@Nagev and @Phaz42 for the discussion.
-
I agree with @Phaz42
-
I think we should agree on this way and test it.
-
@Phaz42 Yes. Taking TW3 Mod Manager as an example, which works ~99% flawlessly in installing mods for W3 and never adds dlc to the loading order.
-
@el0quenz That's because they don't matter so why should they mix with other mods that actually need to be set in the proper loading order. As for me it's enough that you make sure the dlc is installed and not that it shows up in the LO tab.
-
THAT'S HOW: If dlcSomeModName mod doesn't also have a regular modSomeModName, then Vortex doesn't add it to the loading order and mods.settings file. and If dlcSomeModName does have a modSomeModName counterpart, then only the modSomeModName will appear in the load order and mods.settings file.
-
DLC folders do not matter in the load order for The Witcher 3, they simply should not be there. Vortex should only mark folders starting with: 'modABCD' to the loading order (mods.settings)
-
@Phaz42 Hmm, I guess you're right, I got confused because a year ago it was in the load order tab as a whole mod, not separately dlc and mods like now. Only in this way is it correct: [modBrothersInArms] Enabled=1 Priority=1 VK=BIA - TW3 Bug Fix and Restored Content Collection-7329-2-2-1683912038
-
@insomnious So we need another update.
-
@Nagev @insomnious @Pickysaurus Hi. I have to report this again. If a mod contains multiple subdirectories/parts, for example Brother In Arms contains dlcBrothersInArms and modBrothersInArms. Vortex sets both of these directories as priority in mods.settings, i.e. dlcBrothersInArms and modBrothersInArms. We need a patch that restores this to the previous state when everything was working properly, as you can see in the image below: Vortex should mark the entire mod for the loading order, i.e. “Brothers In Arms Mod”, not the modification folders.
-
+1 @shitaro @insomnious @Nagev Vortex should mark the entire mod for load order i.e. "Brothers In Arms Mod" and not the modification folders.
-
I'll add that before the updates it worked fine. I don't remember the Vortex version, but the “load order” tab looked like this:
-
Ok, after new update now 1.11.7 Vortex install mods correctly but does not mark final folders for load order. so another patch is necessary.. MOD EXAMPLE: https://www.nexusmods.com/witcher3/mods/4242 now it mark this ----> Mods/mod_hoods <----correct now it mark this ----> dlc/dlc_hoods <----correct should be: 192 mod_hoods 193 dlc_hoods hope for a quick fix..
-
Thanks. I look forward to the update.
-
I have a question. What have you done to Vortex in the latest updates that it suddenly can't install mods for The Witcher 3? in previous versions it installed them correctly now it does not recognize the simplest folder structures, what is the problem that this mod installs correctly: https://www.nexusmods.com/witcher3/mods/7554?tab=files and this not: https://www.nexusmods.com/witcher3/mods/4242?tab=files It puts everything into the “Mods” folder instead of separating and putting the final folders into Mods and dlc when installing hoods mod: when installing all containers glow mod: The path is correct so why doesn't it recognize it?! In previous Vortex versions the mod worked, now it does not. Users of my mod collection are clamoring for these mods so what do I do now? Other mods work, nothing works from this author even though I can't see the differences