Jump to content

help with fomod xml script

nisen

By nisen
in Discussion

 Share

Recommended Posts

nisen Rising Star

nisen

Posted
Posted (edited)

Hi, ive got nyrb's 'guide to fomod scripts' (for the xml type) but dont understand alotof it, and know to do a basic scripts, but want it to detect other mods installed to decide which version of a an optional file installs

 

say theres 3 sets of 5 optional files (15 files) but only want 5 options shown, so have the script decide which version from the 3 sets get installed depending on the esps detected

 

or better yet, if it shows the specific set of 5 accociated with the esp detected (that way could have different preview pics)

 

Havent found other xml script guides around, so hoping someone would point out the relevant sections in nyrbs guide to focus on, mabye thatd help

 

cheers

Edited by nisen
Link to comment
Share on other sites
Gribbleshnibit8 Mentor

Gribbleshnibit8

Posted
Posted

I don't know of a way to do exactly what you're talking about. My suggestion though is to just find a bunch of scripted installers and see how they do things. The Blackwolf backpack mod from FO3 has a good script, and there are lots of scripts in the PFP installer pack for both FNV and FO3.

 

What you're trying to do would require that the individual options have a <visibility> tag. That's not available at that level. What you can do instead is use the <installStep> section which does have that tag. An alternative would be to use the <conditionFlags> tag in the option, and do your file installation based on the flags selected. The Blackwolf mod has a good example of the <conditionFlags> tag.

 

For a really good example of the <conditionFlags> tag, take a look at the PN Patches for DLC. I also suggest that (if you aren't already) you use the FOMM built in script editor, since it will tell you if it has errors as you type, and will do tag auto-completion.

Link to comment
Share on other sites
nisen Rising Star

nisen

Posted
  • Author
Posted (edited)

Ok have worked it out, needed to get rid of the InstallSteps bit inbetween sections.

 

Heres a working script with visibility tags mentioned above, does exactly what i wanted

 

the first 5 options show up if it detects the pipboy 2500 esp is installed

the third 5 options show up if it detects the pipboy readius esp installed

the second 5 options show up if it doesnt detect either of those

 

 

<?xml version="1.0" encoding="UTF-16" ?>
<config xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="http://qconsulting.ca/fo3/ModConfig5.0.xsd">
 <moduleName>This script is broken</moduleName>
 <installSteps order="Explicit">
   <installStep name="Options">
<visible>
<dependencies operator="And">		
	<fileDependency file="pipboy2500_fo3_edisleado.esp" state="Active"/>
</dependencies>
</visible>
     <optionalFileGroups order="Explicit">
       <group name="Xml 2500" type="SelectAtMostOne">
		<plugins>	
			<plugin name="Step 1 - 2500">
				<description><![CDATA[]]></description>
				<image path="fomod/images/step1_2500.jpg"/>
				<files>
					<folder source="menus\step1_2500" destination="menus"/>
				</files>
				<typeDescriptor>
					<type name="Optional"/>
				</typeDescriptor>
			</plugin>

			<plugin name="Step 2 - 2500">
				<description>
					<![CDATA[]]>
				</description>
				<image path="fomod/images/step2_2500.jpg"/>
				<files>
					<folder source="menus\step2_2500" destination="menus"/>
				</files>
				<typeDescriptor> 
					<type name="Optional"/>
				</typeDescriptor>
			</plugin>

			<plugin name="Step 3 - 2500">
				<description>
					<![CDATA[]]>
				</description>
				<image path="fomod/images/step3_2500.jpg"/>
				<files>
					<folder source="menus\step3_2500" destination="menus"/>
				</files>
				<typeDescriptor>
					<type name="Optional"/>
				</typeDescriptor>
			</plugin>

			<plugin name="Step 4 - 2500">
				<description><![CDATA[]]></description>
				<image path="fomod/images/step4_2500.jpg"/>
				<files>
					<folder source="menus\step4_2500" destination="menus"/>
				</files>
				<typeDescriptor>
					<type name="Optional"/>
				</typeDescriptor>
			</plugin>

			<plugin name="Step 5 - 2500">
				<description>
					<![CDATA[]]>
				</description>
				<image path="fomod/images/step5_2500.jpg"/>
				<files>
					<folder source="menus\step5_2500" destination="menus"/>
				</files>
				<typeDescriptor> 
					<type name="Optional"/>
				</typeDescriptor>
			</plugin>				
	     </plugins>

	</group>
					
  </optionalFileGroups>
  
</installStep>    

   <installStep name="Options">			
<visible>	
<dependencies operator="And">		
	<fileDependency file="pipboy2500_fo3_edisleado.esp" state="Active"/>		
	<fileDependency file="1PipboyPDA.esp" state="Active"/>
</dependencies>
</visible>	
			
  <optionalFileGroups>
			
	<group name="Xml 3000" type="SelectAtMostOne">
		<plugins>

			<plugin name="Step 1 - 3000">
				<description>
					<![CDATA[]]>
				</description>
				<image path="fomod/images/step1_3000.jpg"/>
				<files>
					<folder source="menus\step1_3000" destination="menus"/>
				</files>
				<typeDescriptor>
					<type name="Optional"/>
				</typeDescriptor>
			</plugin>

			<plugin name="Step 2 - 3000">
				<description><![CDATA[]]></description>
				<image path="fomod/images/step2_3000.jpg"/>
				<files>
					<folder source="menus\step2_3000" destination="menus"/>
				</files>
				<typeDescriptor>
					<type name="Optional"/>
				</typeDescriptor>
			</plugin>

			<plugin name="Step 3 - 3000">
				<description>
					<![CDATA[]]>
				</description>
				<image path="fomod/images/step3_3000.jpg"/>
				<files>
					<folder source="menus\step3_3000" destination="menus"/>
				</files>
				<typeDescriptor> 
					<type name="Optional"/>
				</typeDescriptor>
			</plugin>

			<plugin name="Step 4 - 3000">
				<description>
					<![CDATA[]]>
				</description>
				<image path="fomod/images/step4_3000.jpg"/>
				<files>
					<folder source="menus\step4_3000" destination="menus"/>
				</files>
				<typeDescriptor>
					<type name="Optional"/>
				</typeDescriptor>
			</plugin>

			<plugin name="Step 5 - 3000">
				<description><![CDATA[]]></description>
				<image path="fomod/images/step5_3000.jpg"/>
				<files>
					<folder source="menus\step5_3000" destination="menus"/>
				</files>
				<typeDescriptor>
					<type name="Optional"/>
				</typeDescriptor>
			</plugin>				
	     </plugins>

	</group>
					
  </optionalFileGroups>
  
</installStep>	  

   <installStep name="Options">
			
<visible>	
<dependencies operator="And">		
	<fileDependency file="1PipboyPDA.esp" state="Active"/>
</dependencies>		
</visible>
			
  <optionalFileGroups>
			
	<group name="Xml Readius" type="SelectAtMostOne">
		<plugins>

			<plugin name="Step 1 - Readius">
				<description>
					<![CDATA[]]>
				</description>
				<image path="fomod/images/step1_readius.jpg"/>
				<files>
					<folder source="menus\step1_readius" destination="menus"/>
				</files>
				<typeDescriptor> 
					<type name="Optional"/>
				</typeDescriptor>
			</plugin>

			<plugin name="Step 2 - Readius">
				<description>
					<![CDATA[]]>
				</description>
				<image path="fomod/images/step2_readius.jpg"/>
				<files>
					<folder source="menus\step2_readius" destination="menus"/>
				</files>
				<typeDescriptor>
					<type name="Optional"/>
				</typeDescriptor>
			</plugin>

			<plugin name="Step 3 - Readius">
				<description><![CDATA[]]></description>
				<image path="fomod/images/step3_readius.jpg"/>
				<files>
					<folder source="menus\step3_readius" destination="menus"/>
				</files>
				<typeDescriptor>
					<type name="Optional"/>
				</typeDescriptor>
			</plugin>

			<plugin name="Step 4 - Readius">
				<description>
					<![CDATA[]]>
				</description>
				<image path="fomod/images/step4_readius.jpg"/>
				<files>
					<folder source="menus\step4_readius" destination="menus"/>
				</files>
				<typeDescriptor> 
					<type name="Optional"/>
				</typeDescriptor>
			</plugin>

			<plugin name="Step 5 - Readius">
				<description>
					<![CDATA[]]>
				</description>
				<image path="fomod/images/step5_readius.jpg"/>
				<files>
					<folder source="menus\step5_readius" destination="menus"/>
				</files>
				<typeDescriptor>
					<type name="Optional"/>
				</typeDescriptor>
			</plugin>				
	     </plugins>

	</group>
			
  </optionalFileGroups>
</installStep>
 </installSteps>
 
</config>

 

 

btw technically the mods for FO3 im making, but has some cross over with FNV, and its a ModConfig5.0 script

Edited by nisen
Link to comment
Share on other sites
nisen Rising Star

nisen

Posted
  • Author
Posted (edited)

yea visibility does what i wanted, managed to finish setting it up, and even able to use three sets of screenshots :D

 

if any o'yall still wastelandering over in FO3, it was for my map mod here,

 

the need for visibility was firstly cause id configured the map_menu to show the map screen the whole size of pipboy display, but theyre different size displays, and with the other tweak to alter the brightness, meant i wanted 5 versions for each display,; wouldve been a mess to have them all load each time you activated it

Edited by nisen
Link to comment
Share on other sites
nisen Rising Star

nisen

Posted
  • Author
Posted (edited)

I have the latest version of FOMM posted on NEXUS and every time I try to install a mod with a .xml in it the program crashes.

 

If it doesnt crash till you try to activate them, try clicking 'Edit Script' then the 'Ok' button to see if it warns about errors which'll be the parts underlined red, but usually errors just stop those mods from activating. Also the majority of xml scripts for Fallout3 are written with ModConfig2.0, but for Fallout NewVegas FOMM only knows the 5.0 language so if somones mistakenly uploaded a New Vegas mod with 2.0 script, it wont know how to read it, but you can copy the ModuleConfig2.0.xsd in Program Files (x86)/GeMM/data/Fallout3 to GEMM/data/FalloutNV and 2.0 scripts will then work

Edited by nisen
Link to comment
Share on other sites
 Share
Go to topic listing

  • Recently Browsing   0 members

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