Always get errors when deploying an .archive mod (REDmod)

[BitGrub]

Describe the bug
Every single time I deploy a new mod (or disable one) where a shell (or twenty) pops up for a moment, Vortex will always say deployment failed. I'm not sure if it did or not since I usually deploy again and the error does not show up the second time. Game seems to have imported the mods correctly.

To Reproduce
Steps to reproduce the behavior:

1. Download a REDmod compatible mod
2. Install the REDmod compatible mod
3. Deploy the REDmod compatible mod
4. Deploy the REDmod compatible mod again.

Expected behavior
It should work the first time without clogging Vortex notifications with bogus error messages that have to be manually dismissed

Vortex log, filtered by Warnings and Errors only

Tue, 31 Jan 2023 00:32:44 GMT - warn: child process exited with code: 2
Tue, 31 Jan 2023 00:32:44 GMT - error: [cyberpunk-2077-vortex-support] V2077 Load Order: REDmod deployment 1675124715635 failed! {"exitCode":2}
Tue, 31 Jan 2023 00:32:44 GMT - warn: error notification message=Oh no! Something went wrong with the REDmod deployment. Check Diagnostic Files for details!, title=REDmod Deployment Failed!
Tue, 31 Jan 2023 00:33:41 GMT - warn: failed to get mod info err=UserCanceled: canceled by user
Tue, 31 Jan 2023 08:09:57 GMT - warn: failed to get mod info err=UserCanceled: canceled by user
Tue, 31 Jan 2023 08:12:08 GMT - warn: child process exited with code: 2
Tue, 31 Jan 2023 08:12:08 GMT - error: [cyberpunk-2077-vortex-support] V2077 Load Order: REDmod deployment 1675152685612 failed! {"exitCode":2}
Tue, 31 Jan 2023 08:12:08 GMT - warn: error notification message=Oh no! Something went wrong with the REDmod deployment. Check Diagnostic Files for details!, title=REDmod Deployment Failed!
Tue, 31 Jan 2023 08:29:39 GMT - warn: child process exited with code: 2
Tue, 31 Jan 2023 08:29:39 GMT - error: [cyberpunk-2077-vortex-support] V2077 Load Order: REDmod deployment 1675153771125 failed! {"exitCode":2}
Tue, 31 Jan 2023 08:29:39 GMT - warn: error notification message=Oh no! Something went wrong with the REDmod deployment. Check Diagnostic Files for details!, title=REDmod Deployment Failed!
Tue, 31 Jan 2023 08:58:18 GMT - warn: failed to get mod info err=UserCanceled: canceled by user
Tue, 31 Jan 2023 08:59:14 GMT - warn: child process exited with code: 2
Tue, 31 Jan 2023 08:59:14 GMT - error: [cyberpunk-2077-vortex-support] V2077 Load Order: REDmod deployment 1675155537848 failed! {"exitCode":2}
Tue, 31 Jan 2023 08:59:14 GMT - warn: error notification message=Oh no! Something went wrong with the REDmod deployment. Check Diagnostic Files for details!, title=REDmod Deployment Failed!
Tue, 31 Jan 2023 09:41:09 GMT - warn: child process exited with code: 2
Tue, 31 Jan 2023 09:41:09 GMT - error: [cyberpunk-2077-vortex-support] V2077 Load Order: REDmod deployment 1675158055385 failed! {"exitCode":2}
Tue, 31 Jan 2023 09:41:09 GMT - warn: error notification message=Oh no! Something went wrong with the REDmod deployment. Check Diagnostic Files for details!, title=REDmod Deployment Failed!
Tue, 31 Jan 2023 09:49:14 GMT - warn: child process exited with code: 2
Tue, 31 Jan 2023 09:49:14 GMT - error: [cyberpunk-2077-vortex-support] V2077 Load Order: REDmod deployment 1675158544886 failed! {"exitCode":2}
Tue, 31 Jan 2023 09:49:14 GMT - warn: error notification message=Oh no! Something went wrong with the REDmod deployment. Check Diagnostic Files for details!, title=REDmod Deployment Failed!
Tue, 31 Jan 2023 12:44:17 GMT - warn: child process exited with code: 2
Tue, 31 Jan 2023 12:44:17 GMT - error: [cyberpunk-2077-vortex-support] V2077 Load Order: REDmod deployment 1675169047617 failed! {"exitCode":2}
Tue, 31 Jan 2023 12:44:17 GMT - warn: error notification message=Oh no! Something went wrong with the REDmod deployment. Check Diagnostic Files for details!, title=REDmod Deployment Failed!

Environment (please complete the following information):

• OS: Windows 11
• Mod: Any REDmod mod
• Extension Version: 0.9.7

Additional context
Other mods (the ones that don't integrate with REDmod in any way) do not produce erroneous error messages. I thought it has something to do with automatically converted mods, but it happens with native REDmod archives as well.

[E1337Kat]

Hmm, interesting. Would you mind linking a mod that this does happen on? And you have auto-convert turned on with this, right?

Mod: Any REDmod mod

That is really strange.

without clogging with... messages that have to be manually dismissed

That is something I learned recently can be fixed. Hopefully work dies down a bit and I can at least fix that?

[BitGrub]

@E1337Kat Sure, I experimented some more using this mod (old mod style) and this mod, chosen solely because of the existence of a .archive files. I also tested with Sleeves and confirmed that .reds scripts are unrelated to my issue

Behavior is consistent. On my first deploy after enabling (or even disabling, apparently) just one .archive mod, I get a shell script go by faster than I can read it and a red error notification saying REDmod deployment has failed.

Could very-well be some caching weirdness, but I'm too unfamilliar with Vortex to know how how to clear it up

That is something I learned recently can be fixed. Hopefully work dies down a bit and I can at least fix that?

Gosh I hope so. Please prioritize that over my issue.

[BitGrub]

And yes, I have auto-convert on

[BitGrub]

So I deleted and EVERYTHING and started from scratch, which seemed to completely eliminate the issue until I updated this mod (Panam Romanced Enhanced REDmod), which caused the same issue to appear (so, first deployment fails with error code 2, second deployment goes smoothly).

Enabling/disabling any other .archive mod again brings up the error, until I disable this specific mod. Can't verify if the mod itself is actually enabled in game yet.

Also, when installing it and before enabling it in vortex, I manually delete the second mod contained inside (PanamRomancedEnhancedPrivacy) so there's only one folder in the "mods" folder