You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Since the latest extension update, an error pops up every time when I try to deploy mods. B&S was updated to 1.0.1 so maybe the extension isnt detecting the update properly.
To Reproduce
Download a mod
Attempt to deploy
????
Profit
Expected behavior
No popup or error when deploying mods
Screenshots
Platform (please complete the following information):
OS: Windows 10
Vortex Version 1.11.7
Additional context
The extension is definitely not detecting the version right, as Vortex is mismatching the version, and deploying some mods as a legacy mod when they arent
The text was updated successfully, but these errors were encountered:
I think it's time to remove support for the legacy versions of the game. In the meantime you can manually fix this on your end through the mod panel on the mods page. Just double click any mod entry and set the ModType dropdown button to the official version; the mods should then deploy just fine.
I think it's time to remove support for the legacy versions of the game. In the meantime you can manually fix this on your end through the mod panel on the mods page. Just double click any mod entry and set the ModType dropdown button to the official version; the mods should then deploy just fine.
Agreed. Theres no need for legacy support anymore anyways. And yes, changing the mod type fixed the issues for me. :)
Describe the bug
Since the latest extension update, an error pops up every time when I try to deploy mods. B&S was updated to 1.0.1 so maybe the extension isnt detecting the update properly.
To Reproduce
Expected behavior
No popup or error when deploying mods
Screenshots
Platform (please complete the following information):
Additional context
The extension is definitely not detecting the version right, as Vortex is mismatching the version, and deploying some mods as a legacy mod when they arent
The text was updated successfully, but these errors were encountered: