Pickysaurus

You probably need to press "report and quit" so that a detailed log of the issue is sent to the team.

This usually means the AppData folder for Vortex has been corrupted. Considering your very unusual setup it's hard to say what would've done this. You can try renaming the "Vortex" folder in AppData but this will unfortunately means Vortex will "forget" all the mods you've installed until you point it back to the correct staging/download folders in settings.

For help with downloads, please see this post: https://help.nexusmods.com/article/92-im-having-download-issues-what-can-i-do

My best guess is you have a super outdated version of Vortex. Try reinstalling the latest version.

The editor for posting on the forums has been tweaked to provide better contrast.

The App is not suited for any game other than Stardew Valley and is not suitable to be daily driver at all yet. I'd suggest not using it for serious modding.

The block feature on the site means "Don't show this users mods or media in the search" it's not intended to block them anywhere else.

A fix for this has been deployed. Please let us know if you're still seeing issues.

You're looking at the rules in the mods tab. The article you're reading is about rules in the plugins tab (Bethesda games only!)

@DaxtremeAs this is a known issue I've merged your thread into the existing one monitoring this issue.

The point around knowing if the mod is tracked is definitely valid. I'll pass that on.

As part of the upgrade to 1.10 Vortex needs to do a full purge and redeploy of your mods. If you keep interrupting it, it will try again next time it needs to do something with a mod.

I think if you're just linking to ban threads you found amusing that's fine. There was a topic like this before

No, there's no API for the image share section of the website (yet?). The new API which powers use profile can get a list of images attached to an account but no details about the media objects themselves or a way to add new objects at the moment. If you add it to the feedback board it will allow others to vote on it and reflect the priority of the idea.

It's a good idea to allow this kind of data to be accessed. Worth putting on the feedback board?

Try installing the latest Vortex app. You may have a really outdated copy which is causing problems with the latest version of an extension.

As an update on this. Our team have been working on the Media issues for the last couple of days and are making good progress.

In the mods tab, use the "Import from..." menu and select Mod Organizer. This only works for the main games MO2 supports (and not any unofficial addons). Kind regards

Unfortunately, there's no distinction between "has mod manager download buttons" and "is supported by Vortex". It's a known issue.

This usually means your PC's install of .NET is complete borked up. Please see the pinned thread

Click "Suggest" and then "Apply" in Settings -> Mods -> Mod Staging Folder. Your staging folder must be on the same drive as the game, but not inside the game folders.

If Vortex discovers it automatically the game store will be specified and can be retrieved from the state. If the user manually sets the game path it'll be marked as "Unknown".

That's just a list of games with the "Mod Manager Download" button enable. Mass Effect is the only case where Vortex doesn't support it but the buttons are turned on (because ME3Tweaks pulls files using the same method).

You can report issues with the extension here: https://www.nexusmods.com/site/mods/110?tab=files From what I can see this could only happen if "Fallout76.exe" doesn't exist in your game folder. This is the function. function findExecutable(discoveryPath) { const steamExe = 'Fallout76.exe'; const xboxExe = 'Project76_GamePass.exe'; if (!discoveryPath) return steamExe; try { // Steam version fs.statSync(path.join(discoveryPath, steamExe)); return steamExe; } catch(err) { // Could not stat to Steam path } try { //Xbox version fs.statSync(path.join(discoveryPath, xboxExe)); return xboxExe; } catch(err) { // Could not stat the Xbox path } log('error', 'Neither the Steam or Xbox EXE paths exist for Fallout 76'); return steamExe; // throw new Error('Neither the Steam or Xbox EXE paths exist for Fallout 76'); } Based on that code it should only ever look for the Xbox Game Pass EXE if the Steam one doesn't exist and the Xbox one does.

There are a few other threads like this. You need to update Vortex to the latest version by manually downloading it from the site again. Your version is too old to update automatically.