Pickysaurus

Gazzover67 banned Reason: Sending an abusive (but nonsensical) email to our support team. "Why are you f@&#!ts because deleted mods substitution in Spider Man game flag LGBT on USA flag?"

It is quite strange, when does this message appear? Unless it blocks the entire extension you should still be able to use it but you won't be able to detect the EXE version of the SkyrimSE.exe used by Enderal.

I think the other challenge you'll find asking for help with the old release is that the majority of the community have moved to Special Edition. The LOTD release for that version is effectively unsupported and provided "as-is".

Have you tried asking on the LOTD mod page comments? There's a few helpful folks there. You should also consider that your save may simply have become corrupted. If you can start a new game and don't get the problem, that might be the cause.

ahmedkhayry has received a formal warning. This user has now received 1 formal warnings. The warning was given for the following reason: Reference This warning was issued for what took place here Restrictions in place As part of the warning, ahmedkhayry has had the following restrictions placed on his or her account: This user cannot upload images to the Image Share for 7 days Important links: Our terms of service

queerCatXeno3 banned Reason: A Throwaway account registered to upload a mod you know is not permitted. Reference post

As far as I recall, the Enderal SE extension uses the exe-version library built into Vortex. If it's saying it's missing that's often caused by security software interfering. If you look in your games tab and click the little menu on each managed game tile, can you see a version? That library is used in many places to get the version info. I have been able to load this extension in Vortex 1.9.5 without problems.

Your post doesn't contain any information we can use to help you. Please try explaining your problem in more detail and check the pinned posts in this forum

Make sure you do all required Windows updates. It could also be your local security software has stripped some of the required files from Vortex or the extension

As the architect of the entire script system that powers displays in LOTD I'd ask that you present some kind of proof before accusing the core mod of being a problem. "I've heard folks having problems" is not helpful, not least without providing some examples. I'm not above criticism but that system has been tweaked and refined for years and there's not really any known problems with it other than users overloading it (it can support about 5k+ displays before papyrus starts to come crashing down) or using poorly constructed patches. I'm a little out of the loop but I am aware of an entire new gallery add-on and patches that are not supported or endorsed by the creators of LOTD and they frequently cause all kinds of weird problems. At this point there are too many of these patches for the LOTD team to look through but if it can be nailed to a specific one there could be a mistake in the setup. Creating a patch for the gallery is documented but it's not particularly simple thanks to all the systems that hook into it.

It's pretty much this process described on the wiki https://modding.wiki/en/vortex/users/migrating-to-a-new-pc

Make sure you do actually send an email. Our Facebook account is not monitored for support issues.

If you still can't log in it's your adblock or browser settings breaking the website.

Your tests show no issue downloading so unfortunately it looks like an ISP fault blocking downloads specifically.

You've set a different app to handle downloads. Go into Settings -> Download to correct it back to Vortex

We're actually doing some work on the forums at the moment and we're going to be upgrading/reorganising them to try and re-ignite the conversation a bit :) Happy to hear any suggestions you have for improving things!

Thanks, it was changed by accident, sorry about that!

billdrat123 has received a formal warning. This user has now received 1 formal warnings. The warning was given for the following reason: Reference This warning was issued for what took place here Restrictions in place As part of the warning, billdrat123 has had the following restrictions placed on his or her account: This user cannot post comments on the sites or forums for 7 days This user cannot send private messages for 7 days Important links: Our terms of service

I'm not sure what you mean, perhaps you can be more specific? Some game sites have a theme colour but this is a legacy thing so it only impacts older game sections.

BigDickSlanger banned Reason: Inappropriate username

Sounds like you're using Symlink deployment. That's probably the source of your problems as some mods just don't work with it. It's going to be disabled in the next update

gunnerforhire202301 banned Reason: Intentionally uploading content to troll/get a rise from the community. Specifically picking a file that you know is not allowed in this community and boasting about it on the mod page. Reference post

You can use a Vortex utility function to get that path dynamically. import { util } from 'vortex-api' // TypeScript version const { util } = requires('vortex-api') // JavaScript version const docPath = path.join(util.getVortexPath('localAppData'), 'Starfield'); // Results in "C:\Users\<username>\AppData\Roaming\Starfield" Example from Starfield: https://github.com/Nexus-Mods/game-starfield/blob/master/src/util.ts#L64

teratism has received a formal warning. This user has now received 1 formal warnings. The warning was given for the following reason: Reference This warning was issued for what took place here, here, here, here, here Restrictions in place As part of the warning, teratism has had the following restrictions placed on his or her account: This user cannot post comments on the sites or forums for 14 days This user cannot send private messages for 14 days Important links: Our terms of service

This thread will be updated when a fix is released. It might take a week or two to get it scheduled in depending on what needs to be done to fix the problem. For now you can view the mod page to see the media.