FOMOD is giving errors on latest beta build

[HippeusOmega]

Not sure if I'm doing something wrong or if something has changed but since the latest Beta build update I'm getting errors for some reason on FOMOD installers for body replacer textures. Tried it with two seperate male texture replacers for SSE that I know have worked for me in the past.

 

Edit: I found out that it is basically doing it with any FOMOD installer.

 

Edit #2: Error Logs from Vortex

 

 

Fri, 12 Mar 2021 06:34:44 GMT - error: install error message=Installation failed, Name=System.Exception, ,
Fri, 12 Mar 2021 06:34:44 GMT - error: Installation failed text=Invalid XML: The element 'plugin' has invalid child element 'typeDescriptor'. List of possible elements expected: 'image, files, conditionFlags'. (Line 313, Pos 16)
Fri, 12 Mar 2021 06:35:08 GMT - error: install error message=Installation failed, Name=System.Exception, ,
Fri, 12 Mar 2021 06:35:08 GMT - error: Installation failed text=Invalid XML: The element 'plugin' has invalid child element 'typeDescriptor'. List of possible elements expected: 'image, files, conditionFlags'. (Line 313, Pos 16)
Fri, 12 Mar 2021 06:36:43 GMT - error: install error message=Installation failed, Name=System.Exception, ,
Fri, 12 Mar 2021 06:36:43 GMT - error: Installation failed text=Invalid XML: The element 'plugin' has invalid child element 'typeDescriptor'. List of possible elements expected: 'image, files, conditionFlags'. (Line 313, Pos 16)
Fri, 12 Mar 2021 06:38:04 GMT - error: install error message=Installation failed, Name=System.Exception, ,
Fri, 12 Mar 2021 06:38:04 GMT - error: Installation failed text=Invalid XML: The element 'plugin' has invalid child element 'typeDescriptor'. List of possible elements expected: 'files, conditionFlags'. (Line 380, Pos 16)

Fri, 12 Mar 2021 06:39:34 GMT - error: install error message=Installation failed, Name=System.Exception, ,
Fri, 12 Mar 2021 06:39:34 GMT - error: Installation failed text=Invalid XML: The element 'plugin' has invalid child element 'typeDescriptor'. List of possible elements expected: 'files, conditionFlags'. (Line 380, Pos 16)
Fri, 12 Mar 2021 07:03:21 GMT - error: install error message=Installation failed, Name=System.Exception, ,
Fri, 12 Mar 2021 07:03:21 GMT - error: Installation failed text=Invalid XML: The element 'plugin' has invalid child element 'typeDescriptor'. List of possible elements expected: 'image, files, conditionFlags'. (Line 309, Pos 16); The element 'plugin' has invalid child element 'typeDescriptor'. List of possible elements expected: 'image, files, conditionFlags'. (Line 362, Pos 16); The element 'plugin' has invalid child element 'typeDescriptor'. List of possible elements expected: 'image, files, conditionFlags'. (Line 416, Pos 16); The element 'plugin' has invalid child element 'typeDescriptor'. List of possible elements expected: 'image, files, conditionFlags'. (Line 469, Pos 16); The element 'plugin' has invalid child element 'typeDescriptor'. List of possible elements expected: 'image, files, conditionFlags'. (Line 522, Pos 16); The element 'plugin' has invalid child element 'typeDescriptor'. List of possible elements expected: 'files, conditionFlags'. (Line 620, Pos 16)

 

 

 

 

[Tannin42]

tl;dr:

This is a known issue, we'll probably have to do a hotfix today.

 

The new version of Vortex, when it encounters an invalid fomod, produces more detailed error reports than previously (including line and position of the error) to help mod authors find the problem.

Unfortunately this validation is too strict and, as it turns out, a huge number of fomods, probably all generated by the same tool, all have the same error in them.

Specifically in the header they set a schema (basically a set of constraints an xml file sets for itself to ensure application compatibility) that they don't actually adhere to.

NMM has always overridden the schema with its own, "relaxed" schema.

[HippeusOmega]

tl;dr:

This is a known issue, we'll probably have to do a hotfix today.

 

The new version of Vortex, when it encounters an invalid fomod, produces more detailed error reports than previously (including line and position of the error) to help mod authors find the problem.

Unfortunately this validation is too strict and, as it turns out, a huge number of fomods, probably all generated by the same tool, all have the same error in them.

Specifically in the header they set a schema (basically a set of constraints an xml file sets for itself to ensure application compatibility) that they don't actually adhere to.

NMM has always overridden the schema with its own, "relaxed" schema.

 

Thanks for getting back with me. I look forward to the hotfix and keep up the great work on Vortex.

[dizietemblesssma]

Unfortunately this validation is too strict and, as it turns out, a huge number of fomods, probably all generated by the same tool, all have the same error in them.

Specifically in the header they set a schema (basically a set of constraints an xml file sets for itself to ensure application compatibility) that they don't actually adhere to.

NMM has always overridden the schema with its own, "relaxed" schema.

Assuming the tool is FOMOD Creation Tool, could you say where it fails to adhere to the schema? What would be a better shema to set? I use FCT for all my fomods and I can edit the xml quite easliy by hand if I need to.

 

diziet

 

[Pickysaurus]

 

Unfortunately this validation is too strict and, as it turns out, a huge number of fomods, probably all generated by the same tool, all have the same error in them.

Specifically in the header they set a schema (basically a set of constraints an xml file sets for itself to ensure application compatibility) that they don't actually adhere to.

NMM has always overridden the schema with its own, "relaxed" schema.

Assuming the tool is FOMOD Creation Tool, could you say where it fails to adhere to the schema? What would be a better shema to set? I use FCT for all my fomods and I can edit the xml quite easliy by hand if I need to.

 

diziet

 

 

 

Basically the FOMOD schema itself is considerably more strict than you'd expect. However, a lot of tools (like NMM/MO2) have been allowing FOMODs that don't adhere to the schema directly. I don't know of the schema itself is still being maintained but it could be relaxed a little to reflect how it is being used by the community.

[Tannin42]

NMM and Vortex do in fact check against a more relaxed schema so it already exists but it's not hosted in a good location (one that we can trust to remain valid indefinitely) atm.

 

To clarify: this part of the second line of the xmls:

xsi:noNamespaceSchemaLocation="http://qconsulting.ca/fo3/ModConfig5.0.xsd"

is what specifies the schema, and this one for example specifies that a "plugin" (which represents an option that can be selected in the fomod) has to have a "files" or "conditionFlags" item whereas I think it's reasonably common practice to use plugins without either to show readmes and credits and such.