Vortex Can't Handle Empty Image Paths

[Sulhir]

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.

[Pickysaurus]

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

[Sulhir]

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.