Vortex is trying to install infinite number of same extension

[Dorennor]

This ticked is related to #23339

I am still not sure where exactly I need to create ticked so same as previous time I will create in both places - Vortex repo and extension Nexus page.

Problem - once again Vortex is trying every run update and install one another (outdated BTW) version of Star Wars Jedi Survivor Extension

As you can see on screehshot, it already had installed 1.07 (newest one), just installed 1.06 and require one more restart to install one more SQ extension. As I said in mentioned ticket, I already removed 4-5 extensions when I created ticket about deploying.

@Pickysaurus , can you please help me with that?

[Dorennor]

Additional info: re-installing of extension/re-initializing of game leads to this:

ReferenceError: path is not defined
at prepareForModding (C:\Users\vovar\AppData\Roaming\Vortex\plugins\Vortex Extension Update - Star Wars Jedi Survivor Support v1.0.7\index.js:1897:46)
at Proxy. (D:\Programs\Vortex Mod Manager\resources\app.asar\renderer.js:2:2855720)
at D:\Programs\Vortex Mod Manager\resources\app.asar\renderer.js:2:919292
at wrappedFulfilled (D:\Programs\Vortex Mod Manager\resources\app.asar\renderer.js:2:2451868)
at tryCatcher (D:\Programs\Vortex Mod Manager\resources\app.asar\node_modules\bluebird\js\release\util.js:16:23)
at Promise._settlePromiseFromHandler (D:\Programs\Vortex Mod Manager\resources\app.asar\node_modules\bluebird\js\release\promise.js:547:31)
at Promise._settlePromise (D:\Programs\Vortex Mod Manager\resources\app.asar\node_modules\bluebird\js\release\promise.js:604:18)
at Promise._settlePromise0 (D:\Programs\Vortex Mod Manager\resources\app.asar\node_modules\bluebird\js\release\promise.js:649:10)
at Promise._settlePromises (D:\Programs\Vortex Mod Manager\resources\app.asar\node_modules\bluebird\js\release\promise.js:729:18)
at _drainQueueStep (D:\Programs\Vortex Mod Manager\resources\app.asar\node_modules\bluebird\js\release\async.js:93:12)
at _drainQueue (D:\Programs\Vortex Mod Manager\resources\app.asar\node_modules\bluebird\js\release\async.js:86:9)
at Async._drainQueues (D:\Programs\Vortex Mod Manager\resources\app.asar\node_modules\bluebird\js\release\async.js:102:5)
at Async.drainQueues (D:\Programs\Vortex Mod Manager\resources\app.asar\node_modules\bluebird\js\release\async.js:15:14)

[Dorennor]

i fully reverted Vortex folder in AppData (I make full backup from time to time) and it reverted SW Extension to 1.0.6 - it works but it's trying to update it. Update leads to problems I already mentioned.

Also, as additional request if possible @IDCs
It would be good idea to have:

1. Possibility to stop tracking the game (basically remove/unlink vortex support for game) for game without any kind of deployment. You see, it is BIG pain in the ass to re-install extension or re-initialize it in case if something broken. One of the solutions to fix some problems is re-install extension/re-initialize game but you can't do it via Vortex UI because it basically require purging. And it does not work because something is broken.

2. Possibility to stop auto-updates for extensions/Vortex itself. I am tired AF from fixing freaking SW modpack just because all this updating hell. I have stable 1.0.6 version with my workaround, I would prefer stay on it some time until all these updates/fixes will be done and finalized.

[Pickysaurus]

Additional info: re-installing of extension/re-initializing of game leads to this:

ReferenceError: path is not defined at prepareForModding (C:\Users\vovar\AppData\Roaming\Vortex\plugins\Vortex Extension Update - Star Wars Jedi Survivor Support v1.0.7\index.js:1897:46) at Proxy. (D:\Programs\Vortex Mod Manager\resources\app.asar\renderer.js:2:2855720) at D:\Programs\Vortex Mod Manager\resources\app.asar\renderer.js:2:919292 at wrappedFulfilled (D:\Programs\Vortex Mod Manager\resources\app.asar\renderer.js:2:2451868) at tryCatcher (D:\Programs\Vortex Mod Manager\resources\app.asar\node_modules\bluebird\js\release\util.js:16:23) at Promise._settlePromiseFromHandler (D:\Programs\Vortex Mod Manager\resources\app.asar\node_modules\bluebird\js\release\promise.js:547:31) at Promise._settlePromise (D:\Programs\Vortex Mod Manager\resources\app.asar\node_modules\bluebird\js\release\promise.js:604:18) at Promise._settlePromise0 (D:\Programs\Vortex Mod Manager\resources\app.asar\node_modules\bluebird\js\release\promise.js:649:10) at Promise._settlePromises (D:\Programs\Vortex Mod Manager\resources\app.asar\node_modules\bluebird\js\release\promise.js:729:18) at _drainQueueStep (D:\Programs\Vortex Mod Manager\resources\app.asar\node_modules\bluebird\js\release\async.js:93:12) at _drainQueue (D:\Programs\Vortex Mod Manager\resources\app.asar\node_modules\bluebird\js\release\async.js:86:9) at Async._drainQueues (D:\Programs\Vortex Mod Manager\resources\app.asar\node_modules\bluebird\js\release\async.js:102:5) at Async.drainQueues (D:\Programs\Vortex Mod Manager\resources\app.asar\node_modules\bluebird\js\release\async.js:15:14)

This was a mistake on my end which is fixed