Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Blade and Sorcery Extension bug #16000

Closed
BrandonPotter0 opened this issue Jun 25, 2024 · 2 comments · Fixed by Nexus-Mods/vortex-games#120
Closed

Blade and Sorcery Extension bug #16000

BrandonPotter0 opened this issue Jun 25, 2024 · 2 comments · Fixed by Nexus-Mods/vortex-games#120

Comments

@BrandonPotter0
Copy link

BrandonPotter0 commented Jun 25, 2024

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

  1. Download a mod
  2. Attempt to deploy
  3. ????
  4. Profit

Expected behavior
No popup or error when deploying mods

Screenshots
image

Platform (please complete the following information):

  • OS: Windows 10
  • Vortex Version 1.11.7

Additional context
image

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

@IDCs
Copy link
Contributor

IDCs commented Jun 26, 2024

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.

@BrandonPotter0
Copy link
Author

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. :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants