¶ Applications supporting ModConfig5.0 installers Application Supporting invalid installers should be considered a quirk of the software and it is not in the best interests of the modding ecosystem for applications to replicate each others quirk to remain compatible. Otherwise we end up with an inconsistent "wild west" scenario where each tool uses its own interpretation of the format which would mean that the standard isn't really a standard at all. In development, standards are created so that both users who create content in a particular format and applications that use (consume) the format both know what to expect. ¶ My installer works in some apps, why should I fix it? This means that some applications designed to create them may not output a valid XML or the mod author has written the document by hand, without using an IDE to validate the configuration. While the FOMOD installer format is widely used in the modding community, it is often assumed that there is no defined standard.
There are several legitimate reasons why a mod installer could end up non-functional. When the XML configuration file does not comply with the schema that defines the structure of the document, some tools may reject it. In this article we will discuss how to check a mod installer (also know as a FOMOD) for errors.
0 kommentar(er)
