Collection publishing error and Witcher 3 modding

[SP3CNAZ]

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.

 

[Nagev]

Thanks for bringing this to our attention - I'll investigate.

[Nagev]

Ok so just re-iterating what we discussed on Discord + responding to other points you raised in your original post.

- The error you were getting was down to a corrupt MergeInventory.xml file which is generated by the script merger itself. The Script Merger does not write files atomically like Vortex does, which means that if interrupted during writing it can potentially corrupt the file.

- The Load Order issue has been noted and fixed https://github.com/Nexus-Mods/Vortex/pull/16857 we were reluctant to release it so close to the holiday period and potentially shuffling a working environment. We've also only received 2 confirmed reports of this issue which said it only happens intermittently. Are you able to reproduce this constantly?

> Edit: a beta version with the fix has been generated and can be found here: https://github.com/Nexus-Mods/Vortex-Staging/releases/download/v1.13.4-beta.1/vortex-setup-1.13.4-beta.1.exe

- About the mods disappearing from the staging folder - Vortex will absolutely never remove its own mods unless instructed to do so or if an external application interferes with its functionality. A potential culprit could be that Vortex 1.13.2 was using an older version of 7zip which had a known vulnerability causing anti-virus software to go haywire. This was patched in 1.13.3

Alternatively I guess it's possible for the mods to be removed when using a cloud based service provider.

Please also note that nothing in that dialog says that the mods were removed - it simply states that Vortex found and added a new folder it did not know about; (that is indeed a bug as that folder is generated by Vortex) but the mods should still be in the staging folder.