-
Posts
130 -
Joined
-
Last visited
Community Answers
-
ChemBoy1's post in Invalid Extension for Binding of Issac was marked as the answer
The extension is not packaged correctly. There should be no folder above the index.js and info.json files. The author needs to remove that folder and re-upload a new version of the extension. There is already a bug report on the mod page about this. Perhaps @Pickysaurus or another moderator needs to correct this if the author is no longer active in the community.
https://www.nexusmods.com/site/mods/516?tab=bugs
-
ChemBoy1's post in Nexus won't load my mods after an accidental external hard drive disconnect. was marked as the answer
The lack of NTFS formatting is definitely the issue. Was just talking with another user here on the forum that had a similar setup with an external drive not formatted in NTFS.
I would highly recommend reformatting your external drive. if you have drive laying around you can backup your files, reformat the drive, then copy the files back to it.
-
ChemBoy1's post in Profiles Tab Missing was marked as the answer
You need to enable the "Enable Profile Management" setting.
-
ChemBoy1's post in VORTEX Cannot Authenticate was marked as the answer
If you are getting corrupted save game files, that suggests a hardware failure. Skyrim won't give you a corruption message for missing mods. Corruption message means the actual save file was damaged. Missing mods just give a warning before loading the save and may lead to crashes if critical mod data is missing.
-
ChemBoy1's post in No compatible game being managed was marked as the answer
Make sure you are downloading from the correct site for your game (Skyrim vs Skyrim SE).
You have to be managing the game for the mod you're downloading or you will get the prompt. This is by design.
-
ChemBoy1's post in BG3 - Why does Vortex add subfolders when it causes mods to not work? was marked as the answer
@Mortasi - This is happening because an installer for another game extension in Vortex is "hijacking" the installer. This happens when the extension author does not properly check the game ID when testing if the installer should be used.
What 3rd party game extensions do you have installed? The culprit would be an extension for an Unreal Engine based game
-
ChemBoy1's post in Vortex update 1.12.0 borked all my LOOT metadata! was marked as the answer
Yes, the blue banner is just letting you know there is no metadata, but there never was before the update either. That is why it is not an issue and is purely cosmetic. LOOT cannot sort plugins with no metadata anyway.
-
ChemBoy1's post in Getting the Javascript extension to launch through the game store was marked as the answer
So the thing you need is the function call to the "RequiresLauncher" function in the registerGame function:
requiresLauncher: makeRequiresLauncher(context.api, gameSpec),
If you are not using the "Add Game Wizard" structure, you can literally just skip the function call and write this:
requiresLauncher: () => { launcher: 'steam' }, This should work in this case since steam launcher requires no additional parameters to function. If it were Epic or Xbox app, you would need to have additional parameters there.
You also need to have the "findGame" function return an arrow function to the value, like below. Notice the arrow function after "return".
function makeFindGame(api, gameSpec) { return () => util.GameStoreHelper.findByAppId(gameSpec.discovery.ids) //.catch(() => util.GameStoreHelper.findByName(gameSpec.discovery.names)) .then((game) => game.gamePath); }