Mod name in fomod not recognised

[dizietemblesssma]

Hi All,

 

I just recently tried making some very simple fomods to give 2 alternatives to choose between when installing. I have used the docs to make the two xmls files by hand, and downloaded 3 fomod tools - 'fomod creation tool', 'fomod creatot' and 'fomod designer'.

 

All create installers that work and install the files to the right place, but I just can't get the mod name to be what is in the info.xml or the modconfig.xml,

It makes no difference whether I drag and drop into the 'drop files' area or upload to nexus and use the mod manager button there. The mod name is either the .7z filename, or if downloaded via nexus it is my nexus page name followed by the name of the file (next to the green tick) even though that name can be different to what is specified in the info.xml.

 

Simply removing the modconfig.xml causes the installer to not start of course but the mod does appear with the correct name from the info.xml file whether dragged in to the 'drop files' area or via the nexus 'mod manager download' button.

 

All these mods are morrowind. That game is all this old pc I have to use at the moment can handle so I can't test any other games.

 

I use Vortex 0.17.11.

 

Purging my mods and then using NMM to install one of these fomods shows the proper name from the info.xml

 

Am I the only one with this problem?

[HadToRegister]

The problem could be with how Vortex handles Morrowind, it's basic at best, not like how it deals with Fallout 4, Skyrim SE etc.

[dizietemblesssma]

The problem could be with how Vortex handles Morrowind, it's basic at best, not like how it deals with Fallout 4, Skyrim SE etc.

 

Well I guess I could install skyrimse but not play it (pc would freeze up) create some fake esps and try to get a fomod install working, see what happens.

[Rattledagger]

Just tested with 100x Encumberance from https://www.nexusmods.com/morrowind/mods/46573?tab=files

 

While it at least appears you've got an error in your Info.xml, since VersionMachineVersion does not have a corresponding closing-tag but you're instead using Version as closing-tag, this doesn't seem to be a problem.

 

That is a problem on the other hand is, of the Info.xml information only the mod-name is used, the rest of the information is never used. Also, the name only changes when you've installed the mod, meaning you've install the mod with the long name for so switching to the short name specified in Info.xml after installation. Uninstalling the mod changes back to the original name again.

 

A quick look on original Skyrim gives the same result, despite I've installed a non-Nexus mod with Info.xml (and no FOMOD intaller), only the mod-name from Info.xml is used while the rest of the information is never used by Vortex.

 

So you should report the problems with Info.xml through Vortex.

[dizietemblesssma]

Just tested with 100x Encumberance from https://www.nexusmods.com/morrowind/mods/46573?tab=files

 

While it at least appears you've got an error in your Info.xml, since VersionMachineVersion does not have a corresponding closing-tag but you're instead using Version as closing-tag, this doesn't seem to be a problem.

 

That is a problem on the other hand is, of the Info.xml information only the mod-name is used, the rest of the information is never used. Also, the name only changes when you've installed the mod, meaning you've install the mod with the long name for so switching to the short name specified in Info.xml after installation. Uninstalling the mod changes back to the original name again.

 

A quick look on original Skyrim gives the same result, despite I've installed a non-Nexus mod with Info.xml (and no FOMOD intaller), only the mod-name from Info.xml is used while the rest of the information is never used by Vortex.

 

So you should report the problems with Info.xml through Vortex.

 

Ah:)

 

Wasn't expecting anyone to actually track down my little mods!

in fact those little esps with just an info.xml in the fomod folder haven't given me any trouble with the names that I noticed, I admit to not looking at the other stuff since I noticed that names were a problem when there was a modfconfig.xml in the fomod folder as well.

 

The 'versionmachineversion' thing has me really confused tbh, since I looked at a lot of other info.xml files to compare and contrast; some did not have that just '

<version>.........</version> some had <versionmachineversion...>.........</version> and some had <version machineversion...>....</version>

 

since the docs here:

https://buildmedia.readthedocs.org/media/pdf/fomod-docs/latest/fomod-docs.pdf

have the example:

<Version MachineVersion="1.2.3">1.2.3</Version>

I tried to follow that, I may have missed a space out!

 

I shall use Vortex to report a bug, it would be interesting to know what naming occurred for you or anyone else using either of the two mods in 'optional' on that page since they have modconfig.xml files in the fomod folder, and that is what is giving me the headache at the moment.

 

Thanks for checking this out:)

[dizietemblesssma]

Well my problem gets worse, because having installed SkyrimSE I can now install my mods and others from nexus that have fomods into two games and the only mods that seem to have issues are mine. Logically therefore the cuplrit is probably not Vortex but my mods, BUT I cannot for Bob's sake find what's wrong. Even installing a Skyrim fomod into Morrowind displays properly! So seems not to be the morrowind vortex extension.

 

Is there a forum for fomods that I can go to for help? Any links?

[Rattledagger]

Internet is acting up so doubtful can test the optional mod any time soon.

 

Not sure, but isn't all mods using FOMOD installer including both xml files, meaning chances are the contents of info.xml is always used, but only for mod name and only after installing mod. Just in case you're trying different names in the two files.

 

As for xml syntax, a quick look on Wikipedia shows you are missing a space between first Version and MachineVersion.

[dizietemblesssma]

Not sure, but isn't all mods using FOMOD installer including both xml files, meaning chances are the contents of info.xml is always used, but only for mod name and only after installing mod. Just in case you're trying different names in the two files.

 

As for xml syntax, a quick look on Wikipedia shows you are missing a space between first Version and MachineVersion.

 

I've tried all combinations of names in the both files I can think of.

I've tested and it seems that it is definitely te prescence of a moduleconfig.xml file that prevents the info.xml name taking.

 

Here is an example, I made a fomod version of better heads 2.0 to allow the install of my choices.

 

Without any fomod folder the mod is named as the 7z filename, With the fomod folder and both info.xml and moduleconfig.xml the mod is named after the 7z filename. Note that during the extraction of files the 7x extension is missing in the ui but returns once the ui prompts for enabling the mod. With just an info.xml file in the fomod folder the mod the modname is still the 7z filename minus the 7z extension during the extraction phase but once that is finished the mod is named whatever is specified in the info.xml.With just a moduleconfig.xml file of course the mod name is just the 7z filename again.

 

Here are the two files in the fomod folder:

 

info.xml

 

<fomod>

<Name>Better Heads - fomod</Name>

<Version>2.0</Version>

</fomod>

 

and :

 

moduleconfig.xml

 

<config xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="http://qconsulting.ca/fo3/ModConfig5.0.xsd">

<moduleName>Better Heads - fomod</moduleName>

<requiredInstallFiles>

<file source="Better Heads Bloodmoon addon.esm" destination="Better Heads Bloodmoon addon.esm" />

<file source="Better Heads Tribunal addon.esm" destination="Better Heads Tribunal addon.esm" />

<file source="Better Heads.esm" destination="Better Heads.esm" />

<folder source="Meshes" destination="Meshes" />

<folder source="Textures" destination="Textures" />

</requiredInstallFiles>

</config>

 

 

note that here the moduleconfig.xml isn't strictly necessary since the mod's files are all arranged properly under the root of the zipped mod.

But merely the presence of the moduleconfig.xml prevents the mod from being given the name in the info.xml

And of course the point of my using a fomod in other mods is to allow for a choice during installation.

 

So what could possibly be wrong with that moduleconfig.xml?

 

Is it anything to do with encoding and/or unix versus windows line characters?