Jump to content

Vortex FOMOD logical changed after last update its causing crashes


Ahplla
Go to solution Solved by Pickysaurus,

Recommended Posts

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

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

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 by Ahplla
Link to comment
Share on other sites

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

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

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 account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...