FOMM and ModConfig2.0 vs 5.0

nisen · February 8, 2012

Hey, I didnt realize the issue with FO3 fomod scripts not being installable on the FONV side but found that simply copying the ModConfig2.0 from Program Files (x86)/GeMM/data/Fallout3 to GeMM/data/FalloutNV allows FOMM and NMM to install them on the FONV side just the same

The question is, would there be some problem using this method, there must be a reason ModConfig's below 5.0 werent included, but on the one mod ive tried, cant see anything wrong

Edited February 8, 2012 by nisen

Gribbleshnibit8 · February 9, 2012

They weren't included because the 2.0 version is very VERY out of date. Alternative would just be to update the header of the 2.0 scripts to say 5.0, which has everything as the 2.0, but is I believe more streamlined and has more options. Lots more options.

nisen · February 9, 2012

if the header's at the start of the script which reads xsi:noNamespaceSchemaLocation="http://qconsulting.ca/fo3/ModConfig2.0.xsd

i tried changing that to ...ModConfig5.0.xsd but didnt work

Gribbleshnibit8 · February 9, 2012

For what mod? I've changed it in mine and never had a problem. I suppose there might be deprecated stuff in there, but I don't think there is.

nisen · February 9, 2012

this mod

the script looks like this

<?xml version="1.0" encoding="UTF-16" ?>

<moduleName>Pipboy Readius Luis Royo Fantasy Art</moduleName>

<![CDATA[This is a model figurine of one of the Paintings, and this ones a lot better than my other in 0.2b - screenshots are 846x634, if they dont show full size use the drag too just above it to enlarge]]>

</description>

<files>

</files>

</typeDescriptor>

</plugin>

<![CDATA[Looks just as good with Clean Pipboy screen mod, so didnt touch it]]>

</description>

<files>

</files>

</typeDescriptor>

</plugin>

<![CDATA[The 0.2b version was mistake. Its a great picture, but dont know what book its from]]>

</description>

<files>

</files>

</typeDescriptor>

</plugin>

<![CDATA[The O.2b version just needed to be cleaned up abit, so darkenes and reduced the colors while at it, might still have too much red]]>

</description>

<files>

</files>

</typeDescriptor>

</plugin>

<![CDATA[Had to redo it, one of my favorites]]>

</description>

<files>

</files>

</typeDescriptor>

</plugin>

<![CDATA[Genrelly cleaned this up, and reduced the colors to work with Clean Pipboy screen mod]]>

</description>

<files>

</files>

</typeDescriptor>

</plugin>

<![CDATA[Cant see anything wrong with this, it looks just as good with Clean Pipboy screen mod]]>

</description>

<files>

</files>

</typeDescriptor>

</plugin>

<![CDATA[Tried to remake this but didnt turn out as well as this this updated version]]>

</description>

<files>

</files>

</typeDescriptor>

</plugin>

<![CDATA[Had to include this, a great effect from noise reduction]]>

</description>

<files>

</files>

</typeDescriptor>

</plugin>

<![CDATA[The 0.2b version had a depth of field effect i couldnt reproduce, so tweaked to reuse it]]>

</description>

<files>

</files>

</typeDescriptor>

</plugin>

<![CDATA[Not much wrong with this, have toned the colors abit, and added some contrast]]>

</description>

<files>

</files>

</typeDescriptor>

</plugin>

<![CDATA[Wanted to see if it could be improved, a difficult image to alter]]>

</description>

<files>

</files>

</typeDescriptor>

</plugin>

<![CDATA[the simplest edit, just recolored and sharpened. The 0.2b version was ultra saturated]]>

</description>

<files>

</files>

</typeDescriptor>

</plugin>

</plugins>

</group>

</optionalFileGroups>

</config>

mabye 5.0 script stopped using certain elements. Idk much about scripts, this was something i pieced together from another mod, its your standard menu script

another reason for asking this, is if theres no negative effect from copying ModConfig2.0.xsd to GeMM/data/FalloutNV folder, then I could just include a copy of it in the NewVegas uploaded fomod, for anyone whos not got a copy of FO3 installed (the mod has texture files usable on both games so its uploaded to both sites)

Edited February 9, 2012 by nisen

Gribbleshnibit8 · February 9, 2012

Not sure then. Does it throw an error besides just saying anything about the ModConfig file?

Gribbleshnibit8 · February 10, 2012

So, I just did my own conversion of an old file and realized what it is. You'll need to load the mod up in FOMM to get the correct syntax highlighting and error reporting, plus it does autocomplete for the tags, which helps a lot.

Ok, so the issues I remember now. 2.0 had a lot of things that weren't required.

<moduleName>Fellout</moduleName>
<moduleDependancies>
<falloutDependancy version="1.0.11.0"/>
</moduleDependancies>

Changed to:

<moduleName>Fellout</moduleName>
<moduleDependencies>
<gameDependency version="1.0.11.0"/>
</moduleDependencies>

See the difference there?

Another issue that I remember is that in the design docs for 2.0 Kaburke misspelled the word dependency as dependancy. This was fixed when he noticed the issue. So:

<dependancyType>
<defaultType name="NotUsable"/>
<patterns>
	<pattern>
		<dependancies>
			<dependancy file="Anchorage.esm" state="Active"/>
		</dependancies>
		<type name="Recommended"/>
	</pattern>
	<pattern>
		<dependancies>
			<dependancy file="Anchorage.esm" state="Inactive"/>
		</dependancies>
		<type name="CouldBeUsable"/>
	</pattern>
</patterns>
</dependancyType>

Becomes:

<dependencyType>
<defaultType name="NotUsable"/>
<patterns>
	<pattern>
		<dependencies>
			<fileDependency file="Anchorage.esm" state="Active"/>
		</dependencies>
		<type name="Recommended"/>
	</pattern>
	<pattern>
		<dependencies>
			<fileDependency file="Anchorage.esm" state="Inactive"/>
		</dependencies>
		<type name="CouldBeUsable"/>
	</pattern>
</patterns>
</dependencyType>

Another change was in the beginning of the files. In order to support more conditions and options, the heading information was expanded. So compare this:

<optionalFileGroups>
<group name="DLC Compatibility" type="SelectAny">
	<plugins>

to this:

<installSteps>
<installStep name="DLC Options">
	<optionalFileGroups>
		<group name="DLC Compatibility" type="SelectAny">
			<plugins>

This last part is obviously a large change. Note that the <installStep> tag has to have a name field. And of course, all of these new tags close at the bottom.

Sorry it took me a while to get this, I myself wasn't even aware of all the changes. But now you know.

nisen · February 13, 2012

thanks for those tips Gribbles, i checked it out again and NMM mentioned one of the possibilities was a missing <installSteps>

so tried changing

to

and the closing

also changed utf to 16 and added the ModConfig5.0 uptop. No more errors :)

and fwiw the stopgap method first tried only worked on FOMM, updating it to 5.0 is much better, and saves a ton of embarrassment

Fallout New Vegas

FOMM and ModConfig2.0 vs 5.0

Recommended Posts

nisen

Link to comment

Share on other sites

Gribbleshnibit8

Link to comment

Share on other sites

nisen

Link to comment

Share on other sites

Gribbleshnibit8

Link to comment

Share on other sites

nisen

Link to comment

Share on other sites

Gribbleshnibit8

Link to comment

Share on other sites

Gribbleshnibit8

Link to comment

Share on other sites

nisen

Link to comment

Share on other sites

Recently Browsing 0 members

Browse

Activity

My Activity Streams

Explore