Pickysaurus

Ah, the meta files from Thunderstore, yes they can be annoying. Those probably need to be added to the exception list for that game. The page for that extension is here: https://www.nexusmods.com/site/mods/210 I've put a PR in for that change here: https://github.com/Nexus-Mods/game-valheim/pull/11 Edit: icon.png, and manifest.json are already ignored, but CHANGELOG.md was not.

@Zorkaz I've merged your thread with this one as it's about the same thing (unless I'm misunderstanding).

Sorry to hear that. Can you please be more specific on what feels slow to you? That can mean quite a few different things. Page load times, scrolling, items loading in, etc.

This release features an improved game version detection system, a way to manage extra files in loadouts and additional UI refinements. Better game versioning We've made some major changes to how we identify the games installed on your PC in order to deliver a better modding experience. Games installed from GOG.com and Steam have been indexed and the app will match the files on your PC to those included with these releases. The app will now be able to tell if your game folder is unmodded on first managing the game and identify any mod files already in your game folder. In future, we hope to use this system to integrate with GOG.com to allow users to quickly swap between game versions on demand. External Changes Within your loadout, there can often be changes made to your game or mod files that aren't part of your mods. These are now collated into the new ["External Changes" page](https://nexus-mods.github.io/NexusMods.App/users/features/ExternalChanges/) shown in your loadout. Files that have been created, modified or deleted in the game folder will be listed here and allow users to manage them. When managing your game for the very first time, any files that aren't part of the base game will be displayed here and can be quickly removed if you want to clean your game folder for a fresh start. Future development of this feature will allow you to add these files to your loadout as mods. More Features Collections from Nexus Mods are now installed in a read-only state to ensure the collection is as the curator intended it. Cloning and editing collections will be added in future. The Collection Download page now includes an Instructions tab with both collection and mod instructions. Collections can now be removed from loadout without deleting them from the Library using the menu option in the header. The header has been redesigned to be more compact. The Settings UI has been updated to match the latest brand guidelines. Stardew Valley mods that are packaged without a top-level folder will now install correctly. Added more information to the Health Check diagnostics for Stardew Valley. Technical Changes All games except Stardew Valley have been moved behind the "Unsupported Games" flag in Settings. If you were modding Cyberpunk, Baldur's Gate 3 or Mount & Blade II:Bannerlord in a previous release, you will need to enable this option to continue managing your mods. The app can now differentiate between a mod installed as part of a collection and the same mod installed directly from the Library. When installing collections for Stardew Valley, any unrecognised mods are now installed relative to the "Mods" folder instead of the game folder. Conflicting mods within a collection are now installed in an order that respects the rules set by the curator. Large numbers are now displayed with comma separation or abbreviations. File sizes now only show decimal places above 1GB. Edits to mod files are now saved to External Changes instead of merging into the source mod. Added a new "Give Feedback" button to the bottom of the main window. When two different versions of the same SMAPI mod are installed into the loadout, diagnostics will use the most up to date version to display messages. Errors communicating with the SMAPI server will now silently be recorded in the logs rather than showing a pop up. Bug Fixes Mod updates now correctly show the number of mod files with updates rather than the number of new versions between the current and latest releases. The left menu now displays the correct name of a collection if the internal manifest and website don't match. A Command Prompt window will no longer be open behind the app on Windows. The Success Rating for a collection now shows the correct value. If a collection has less than 3 votes on the Success Rating, it shows as grey instead of red. Collections with no required mods can now be installed. Fixed multiple places where the app UI would freeze when making large numbers of changes in quick succession. Fixed an issue where the workspace could be broken by a saved page no longer being available. Fixed an issue where the SMAPI version and game version comparison diagnostic was not running correctly. Known Issues The sort order for some columns does not work as expected. The game version is not checked when adding a collection meaning you can install outdated mods without being warned. The table header sorting and collapsible section states are not saved and reset each time the view is loaded.

This should be resolved now. https://nexusmods.statuspage.io/incidents/ypwsrpx8gwv1

Sorry to hear that. We need more info to feed this back https://help.nexusmods.com/article/100-how-to-report-bad-or-inappropriate-ads

Sorry about that; we discovered this bug ourselves this morning. There's a task to fix it.

I've checked with our team, and the best way to fix this is to install Vortex at the default location under C:\Program Files and use the normal Appdata location rather than a symlink. Without doing that, you may not be able to make Vortex work with your setup.

As the errors say, this is a permission problem. I'm afraid you just need to resolve that issue to continue. You might be able to reinstall the game outside of Progarm Files to fix the issue.

Your symlinks are causing this problem. Vortex is likely looking for a specific path, and your symlinks are probably breaking this. Semver is part of the core Vortex app, so it can't really be missing unless your install is corrupt.

Did not realise this thread was still going. It can be locked now.

That message you're seeing (if you read it) it should tell you the plugin or BSA file is not intended for the game you're playing. If you try and load a Skyrim SE mod into "old Skyrim", it will just crash. If you do the inverse, you'll get similar issues. Make sure the mods you're using are for the version of Skyrim you are playing. On Nexus Mods that's ensuring the mods are from the Skyrim or Skyrim Special Edition game site.

If the plugin is being edited or is locked or in any other way is being interfered with when the built-in LOOT library tries to parse it, you'll get an error. If the error goes away next time Vortex sorts your load order, there's nothing to worry about.

Just want to point out that this particular thing is a bug, and we're aware of it. Hopefully, it'll get fixed soon.

All the known solutions to this are in the help article in your screenshot (https://help.nexusmods.com/article/109-why-am-i-not-seeing-the-captcha-challenge) This is almost always a problem on the users end. In a staggering majority of cases it's your system date and time (first item from the troubleshooting guide).

If you search for this in the forum you'll find previous threads. You've basically got something breaking the script extender or any mod that installs to the game root. Try reinstalling anything that puts files in the top level folder instead of data or overwrites the files from SKSE

Have you tried the "Having Issues?" Section in your screenshot? Login issues are almost always caused by your PC/Browser setup

If Vortex couldn't match it to a file on the website it either isn't on Nexus Mods or your PC is preventing Vortex from talking to our servers.

This particular error means you're not signed in properly. Log out and back in. If the problem persists check your firewall settings.

Did you check the load order tab? You may need to enable the mod there

You will have something in your load order conflicting with something in your game folder. This is most often caused when another mod directly edits SKSE scripts (which is just bad mod design IMHO)

I'm afraid beyond trying that I'd have to defer to @ChemBoy1 as they built the extension for this game.

Those logs don't appear to show anything useful. You could try installing Python, but that isn't a requirement for Vortex to work. Ultimately, your internal Vortex state is probably corrupted- this is often caused by applications outside of Vortex modifying it or locking the state it at the wrong time (common with anti-virus apps). The only real solution would be to head to %appdata% and rename the Vortex folder. It means you'd have to start over as far as installing a collection goes, but the mods you've already downloaded are still on your PC.

I am not sure what would be causing it. What I would suggest you try is this. On the Mods toolbar, click "Purge Mods" (this temporarily removed the mods from your game folder) If the "External Changes" window comes up, revert all changes. Open the Mods folder on your PC (Mods toolbar Open -> Open Game Mods folder) Delete anything in that folder. On the Mods toolbar in Vortex, click "Deploy Mods". This will ensure that the only files in the mods folder are the ones controlled by Vortex.

Does it happen after doing anything specific? After running the game? Running some other modding tool? etc? Vortex can't tell you what edited the files, as Windows doesn't keep a record of the last app to modify a file.