Pickysaurus

Thanks for providing more information on this. It's definitely a weird one. Are you registered as a business in some way? A VAT number is usually something required for business accounts (as I understand it). It could somehow be related to the protection on your account. You may need to ask the bank for assistance on this one! If you want to use someone else's card that's fine. Just please remember that by default a recurring subscription is created, so if you are borrowing a friend's card you may want to cancel that renewal once the first payment is taken.

There's a bug in the beta. It should be fixed in the next build.

The conflicts Vortex is referring to are unrelated to plugins. These conflicts (as Vortex tries to explain in the UI boxes you're seeing) are related to multiple mods providing the same file(s) and you need to decide which ones to use. Making changes to the plugins will do nothing to solve this, so the two problems are unrelated. If you really want to ignore what Vortex is telling you, just open the tool directly from the EXE file rather than using the Vortex shortcut.

I've split your post into its own topic as it's not really related to the one you posted in. What is the error you are seeing? Quite often it's an issue at your card provider or your browser addons breaking the form.

It's something we definitely want to add. It's difficult now to add it because the comments on the website are straddled across two systems. Once the majority of comments are on our new system it'll be easier to show all your comments in one place.

This is basically the answer. Thanks

This issue should now be resolved!

No, Vortex is intended to be used on a clean game install.

If you're getting told there's a conflict, you must resolve it or your mods may not work as expected. Perhaps if you provided more detail we could help you with this.

Saves are not managed for Starfield at the moment.

Which page are you trying to download it from? There are no known problems with this at the moment.

Hopefully it'll get looked at in the next few days

This release makes some refinements to the Stardew Valley modding experience based on user feedback, improves various UI elements and includes a number of back-end bugfixes. Fixes Fixed the "SMAPI is disabled"-diagnostic for multiple SMAPI installations (#1674). Fixed Loadout disappearing when applying (#1737). Fixed un-managing a game removing all Loadouts instead of just the ones for the current game (#1738). Fixed sorting in the Mod Library and the "Completed Downloads"-section (#1690). Fixed SVGs not loading and rendering properly in the markdown viewer (#1661). Fixed SVGs throughout the App (#1622, #1681). Fixed not disposing services on close correctly (#1679). Windows: Fixed log file creation failing due to illegal character in path (#1728). Thanks, @ZeeWanderer! Linux: Fixed protocol registration (#1691, #1689, #1683). Linux: Upgraded GameFinder to fix an issue with not being able to find Steam installed as a Flatpak or Snap (#1720). Cyberpunk 2077 - EXTREMELY EXPERIMENTAL This version of the app adds Cyberpunk 2077 to the Games section (#1719). We are now actively working on supporting this game but the implementation is still very experimental and may not work for all types of mod. Further improvements are planned for future updates. Other Features Added support for ignoring game assets when backing up the game files. For Cyberpunk 2077, this can result in 98.75% less disk space used: 1 GB instead of 80 GB (#1713). The logs directory can be opened from the help menu in the top bar (#1675). Miscellaneous Improved user documentation for Workspaces, Health Checks and Stardew Valley. Reworked protocol registration to set the App as the default on startup (#1691). Reworked out data model to use our new source generator (#1626). Reworked out synchronizer to a simpler 3-way merge approach. (#1707). Began working on adding Loadout Items, Library Items, and reworking Downloads (#1336). This release contains some major changes for package maintainers. See the new docs for details. External Contributors @ZeeWanderer: #1728, #1746

This is almost certainly caused by a broken .NET 6 install. See this post:

Something on your PC must've broken Vorttex's deployment manifest. You should be able to restore from the backup as prompted.

This is caused by browser addons or privacy settings.

Try fully logging out and log back in. You can test this in an incognito tab.

The error message you describe indicates that your bank is denying the payment. Please contact your payment provider. It's also possible that browser addons or privacy settings are breaking the form and making the payment widget untrusting of your traffic.

The previously mentioned documentation https://modding.wiki/en/nexusmods/collections/create/mod-options#bundle-with-collection

@Cerberry I've merged your report into the list of known issues as it has already been reported.

rsk22 has been given a warning with a posting restriction for their conduct here. They can open a new thread if they still need help after the restriction has expired.

These all look like PC config issues. Your temp directory folders may be broken, which means Vortex doesn't have permission to use it. The issues with Blade and Sorcery or Witcher 3 are because your PC is blocking Vortex from talking to GitHub.

Doesn't sound like this is a Vortex problem, but more likely an issue with your connection. The I/O error is just the result of Vortex being unable to write data to your HDD.

Good catch. I middle mouse click the forums out of habit anyway so I never noticed!

No. Your version is so far out of date it can't auto update anymore. For context we had to update our security certificate (which tells your PC that Vortex is safe). Originally the certificate was issued to "Black Tree Gaming Limited", however, when we renewed it they changed the name to "Black Tree Gaming LTD". Vortex assumes the name must be an exact match to the first one. We released an intermediate version which accepts both names, but if you never updated for the several months that version was live, this error will occur. It's annoying but it's just a couple of extra clicks as a one off and you'll be back in business