Pickysaurus

This was a temporary issue due to on going updates. It should be back to normal now.

You may want to try disabling Avast. There isn't anything we can do from our side to change that.

Summary For some users, attempting to load an adult collection (with adult content enabled) results in the "Oops! Something went wrong!" error page. If you are experiencing this issue, please do the following and let us know the output by replying to this thread: Press F12 on your keyboard (if you're using Google Chrome) which will open the developer tools side panel. In the side panel, ensure the "Console" tab is selected. Then, try to load a collection page and see if any red error messages appear. If they do, please provide them here so I can pass them on to our team. Steps to reproduce So far we've found one possible cause Use a browser feature or addon to translate the page from English to any other language. Attempt to view this page: See the error. Turn off translation and see that the page loads correctly. Expected Behaviour Adult collections load successfully. Actual result An error page. Workaround Try disabling any automatic translations that are enabled on the page.

Which forum was this in? The "Mark as solution" is a per forum setting. It's also possible to be set to "Post started and moderator" or "Only moderators".

What it might be worth doing is rename your INI files, then start the game via the launcher (which will recreate the INIs with the default values).

Nexus Mod Manager (now called NMM) was dropped as our official mod manager in 2016. All that can be said about that has been said over the last 7 years. NMM still has a page on the site, it's just not the one you looked at. You can use whatever suits you, but very few people support or recommend NMM these days.

As the message suggests, one of the game INI files is borked. Check the ones in your My Documents folder or inside the Data folder.

This doesn't sound like a problem caused by Vortex. Skyrim recently updated so you need to update all mods or downgrade your game.

This issue has been resolved, we now check for errors related to the security settings which cause this problem.

Moved to the correct forum

1. Once your mod list is set up, you can start the game however you like. 2. That is not expected, no. It could be a bug in the extension for Witcher 3. 3. Best way to do this is to install the mod as normal. Then right-click and pick "Open in File Manager". Fix the structure there and then deploy, accepting all changes in the "External changes" window that appears. 4. If you can give some examples that'd be handy. Vortex doesn't expect non-mod files to be inside mods but they might be easy to ignore in an extension update.

This has been covered multiple times, in multiple threads that are almost identical to this one: It is not a Vortex issue.

Can you be more specific as to which games? Did you check the for notifications?

You've either uninstalled the Script Extender/ASI loader or you've messed up the "Tools" section on the dashboard so it doesn't point to the right application anymore.

Invalid primary tool has a "More" button that tells you why it's invalid. You probably don't have SMAPI installed properly.

For any error related to OneDrive, the place to start would be your OneDrive settings.

It's a temporary problem we're aware of and will hopefully investigate next week.

You should not be backing up anything in Program Files to OneDrive. This is not the default. If you enabled this on purpose I'd be curious to know why?

Just so you're not feeling left out. The poll was specifically for contributor's whose work was shared in releases during October (the month of points are for). The first release with your contributions was in November, which would put you in the next round of contributors

I do agree that it should be split by effort. But it's a difficult thing to quantify. I'm just not entirely comfortable making the call of who gets how much DP - and I don't really think any SFCP project lead should have that power without accountability for their decisions. Turning DP off might be a move to consider - the initial rationale of keeping it on may have been based on a faulty assumption that this mod would generate a lot of DP.

Hi everyone. So this is something we thought I'd try out. The Starfield Community Patch earned 42,595 Donation Points in October which is worth around $42.59 - it's not a massive sum of money, but as the patch is a community project I thought we'd try putting a poll up to decide how you all think the points should be shared. Depending on if this is successful (or if you think it's a fair way of dishing out the points) we may do this every month. It's fair to say a considerable chunk of the DP should be directed to the tool creators for these first few months as the entire patch hinges on them creating things like xEdit, xTranslator and BSArchPro to build and share the mod in the first place. When considering the contributors, take a look at the changelog to see what they shared. October saw versions 0.0.1 and 0.0.2 release. Just in case anyone asks, I am automatically disqualified from earning any DP as I work for Nexus Mods - but even so I'd forfeit my share as I am a humble compiler of fixes contributed by the community. Thanks to @Argonil @ElminsterAU @mcguffin @Noggog @wSkeever @Krevil @Aurelianis @rux616 @Monitor144hz @zilav and all the other contributors to the patch! What do you think is the fairest way to share DP for the project?

Starfield saves are in a different format. No tools currently exist to clean scripts. If you've got your save into a state where you think it's required you have two options: Enter NG+ this resets a lot of script data for your save. Start a new game.

This thread is part of the announcement posted on Nexus Mods here, please check that post if you're unsure of why the BBCode has changed. If you need help with your formatting please include a link to the content you're trying to update as part of your reply. To update a mod page BBCode to ensure it loads correctly after the security update on 20 December 2023, you should follow these general guidelines. Treat each new type of formatting as a "block" and ensure that everything the formatting is intended to apply to is inside that section. Don't close BBCode tags inside other BBCode tags - this will create an invalid hierarchy. When using spoilers, keep any formatting for the spoiler content self-contained so it doesn't "leak" out onto other content. If you want to make your BBCode easier to read, you may want to consider putting the formatting tags on new lines. The most common area for formatting to stop working is with spoilers. Examples These examples show common cases where the page will not display properly and how to fix them. Invalid - Italics tag starts outside the spoiler but ends inside it. [i][spoiler] Text I want inside the spoiler that is italic[/i] [/spoiler] Invalid - Italics tag starts inside the spoiler but ends outside of it. [spoiler] [i]Text I want inside the spoiler that is italic [/spoiler][/i] ✔ Valid - The italics only apply to the text inside the spoiler. Some regular text [spoiler] [i]Text I want insider the spoiler that is italic[/i] [/spoiler] ✔ Valid - The italics apply to everything, including the spoiler. [i]Some regular text [spoiler] Text I want insider the spoiler that is italic [/spoiler] [/i] Here's an example of the error. The spoiler should include all the content down to the red line, but is empty. Editing BBCode directly BBCode can be edited directly by swapping to the BBCode view in the editor. This is not available on mobile devices.

We've rolled back this change as it caused problems with some mod pages that make use of the spoiler tags.

This is fixed in the current beta build (1.9.11) - you can either opt into the beta or wait for the full release.