Sulhir Posted November 15 Share Posted November 15 Vortex 1.12.6 (10/3/2024) Windows 10 Skyrim Anniversary Edition from Steam An invalid child element will cause Vortex to be unable to install a FOMOD despite the "ignore" error button. In this specific case the "invalid child element" is an image path with no path or image. Vortex goes even further to suggest that the "image" element itself is invalid and only files or typeDescriptor are valid. Untrue since image elements with the file path and file are also in the FOMOD and none of those lines are mentioned in the line by line error report. Vortex had no problems with a files element with no path or file, something that upset the August 4th 2024 version of Mod Organizer 2. Link to comment Share on other sites More sharing options...
Pickysaurus Posted November 18 Share Posted November 18 Vortex follows the FOMOD standard. If it's reporting an error, that generally means it's not part of the standard. This is covered in detail here: https://modding.wiki/en/vortex/developer/mod-installer-repair Link to comment Share on other sites More sharing options...
Solution Sulhir Posted November 21 Author Solution Share Posted November 21 I figured it out. I was right and Vortex is wrong. Even worse is Vortex's error message is wrong. There isn't anything wrong with having images in fomods. The fomod in question had 199 other image links that worked just fine. Just 20 of them didn't. If a FOMOD has conditionFlags between the description and the files then the image line has to be above it, for absolutely no reason other than Vortex doesn't like it. MO2 doesn't care what order you put them in, only Vortex. Link to comment Share on other sites More sharing options...
Pickysaurus Posted November 21 Share Posted November 21 13 hours ago, Sulhir said: I figured it out. I was right and Vortex is wrong. Even worse is Vortex's error message is wrong. There isn't anything wrong with having images in fomods. The fomod in question had 199 other image links that worked just fine. Just 20 of them didn't. If a FOMOD has conditionFlags between the description and the files then the image line has to be above it, for absolutely no reason other than Vortex doesn't like it. MO2 doesn't care what order you put them in, only Vortex. Vortex may care about this because it's invalid against the FOMOD standard, as I said before. Link to comment Share on other sites More sharing options...
Sulhir Posted November 24 Author Share Posted November 24 Against its FOMOD standard It's also screwing up the install process by including the folders it's installing from now instead of just installing from the folders The error message is still wrong and its not doing what it should be with the install so it is a bug, not a feature as you are suggesting Link to comment Share on other sites More sharing options...
Pickysaurus Posted November 26 Share Posted November 26 On 11/24/2024 at 3:15 PM, Sulhir said: Against its FOMOD standard It's also screwing up the install process by including the folders it's installing from now instead of just installing from the folders The error message is still wrong and its not doing what it should be with the install so it is a bug, not a feature as you are suggesting The standard is defined by the creators of the FOMOD standard, it's not something Vortex specifically created. There's not much point in there being a standard if other apps just ignore all the rules. If you can give a few quick steps to replicate this, we'll be able to take a look at the error and see if any improvements can be made. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now