Ahplla Posted February 7 Share Posted February 7 The latest version of Vortex is causing errors in Mods with FOMODS that use images. Error message: Invalid XML: The element 'plugin' has incomplete content. List of possible elements expected: 'files, conditionFlags, typeDescriptor'. (Line x, Pos x) The Vortex stopped recognizing the image element, such as: <image path="fomod\option1.png" /> This is affecting almost all MODS with Fomods. Link to comment Share on other sites More sharing options...
ChemBoy1 Posted February 7 Share Posted February 7 I just used a FOMOD installer on latest Vortex version and it works just fine. It has at least one image. Mod is linked below. What you are describing sounds like an issue with specific mods. Probably ones that are using a deprecated FOMOD version. There was a deprecation that occurred about a year ago IIRC. https://www.nexusmods.com/stalker2heartofchornobyl/mods/99 Link to comment Share on other sites More sharing options...
Ahplla Posted February 8 Author Share Posted February 8 (edited) 19 hours ago, ChemBoy1 said: I just used a FOMOD installer on latest Vortex version and it works just fine. It has at least one image. Mod is linked below. What you are describing sounds like an issue with specific mods. Probably ones that are using a deprecated FOMOD version. There was a deprecation that occurred about a year ago IIRC. https://www.nexusmods.com/stalker2heartofchornobyl/mods/99 This problem did not occur with the same fomods a month ago, suddenly users are reporting this error that only affects Vortex and not MO 2. Edited February 8 by Ahplla Link to comment Share on other sites More sharing options...
ChemBoy1 Posted February 8 Share Posted February 8 Your ModuleConfig.xml file is not correct. You are missing the parameters indicated in the error message. I think typeDescriptor is required. The image path is not the problem. Did you use the FOMOD Creation Tool to make this? I highly recommend it as it generates this file automatically. https://www.nexusmods.com/fallout4/mods/6821 Your file: <group name="Vortex" type="SelectAtMostOne"> <plugins order="Explicit"> <plugin name="Instalar Vortex"> <description>Copia o arquivo automaticamente para a pasta correta.</description> <files> <folder source="Data" destination="Data" priority="0" /> </files> <image path="fomod\images\aviso.png" /> </plugin> </plugins> </group> Example file: <group name="Spawn chance" type="SelectExactlyOne"> <plugins order="Explicit"> <plugin name="Every hit"> <description>Spawn blood on every single shot</description> <image path="logo.jpg" /> <conditionFlags> <flag name="every_hit">Active</flag> </conditionFlags> <typeDescriptor> <type name="Optional"/> </typeDescriptor> </plugin> </plugins> </group> Link to comment Share on other sites More sharing options...
Ahplla Posted February 8 Author Share Posted February 8 I didn't understand. It's not one of my mods that has this problem. As far as I know, there is no problem with them beyond that lol But I don't doubt that this must be affecting them as well. A month ago, Vortex handled the images very well just as they are; it can't simply update this and stop being compatible, which is why MO 2 is light years ahead. Link to comment Share on other sites More sharing options...
ChemBoy1 Posted February 9 Share Posted February 9 MO2 hasn't even been updated since August, but sure.... Link to comment Share on other sites More sharing options...
Solution Pickysaurus Posted February 10 Solution Share Posted February 10 The FOMOD is invalid (as the error says). Here's a more in-depth explanation. https://modding.wiki/en/vortex/developer/mod-installer-repair 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