Difference between revisions of "NMS:Tutorials/ToyingwithAMUMSS"

From STEP Modding Wiki
(Created page with "__NOTITLE__ {{NMSPage|contentTitle=Toying with AMUMSS}} Category:No Man's SkyCategory:NMS-Tutorial {{TOC_right}} == HeaderText == Page content here... {{NMSPageClose}}")
 
(HeaderText)
Line 3: Line 3:
 
[[Category:No Man's Sky]][[Category:NMS-Tutorial]]
 
[[Category:No Man's Sky]][[Category:NMS-Tutorial]]
 
{{TOC_right}}
 
{{TOC_right}}
== HeaderText ==
+
AMUMSS is a great tool offering a lot of possibilities via a scripting language.<br>
 +
But do you know it also brings very simple features that everyone can use ?
 +
== Detecting mod conflicts ==
 +
Either you downloaded a new mod and can't see the changes ingame, or you have downloaded a lot of them from different authors and are unsure if they are all compatible or not, AMUMSS can help you sort it out.
 +
Indeed, AMUMSS has an integrated feature to compare all mods .pak contents and check if two or more mods edit the same file(s).
 +
How do use it. Very simple :
 +
# download and extract [https://www.nexusmods.com/nomanssky/mods/957 AMUMSS] files.
 +
# Double Click BUILDMOD.BAT
 +
# When AMUMSS ask if you want to check for conflicts, hit the "Y" key (Yes)
 +
# AMUMSS will compare all your mods and generate a report. you can read it in the command line window but it's easier to close AMUMSS and open the file named REPORT.txt in AMUMSS folder.
 +
# Each file found in two or more mods will be listed as CONFLICT as in the exemple below.
 +
<pre>    [CONFLICT]: "TEXTURES\UI\FRONTEND\ICONS\U4SUBSTANCES\SUBSTANCE.FUEL.1.DDS" (Only in User paks below)
 +
[INFO]: is MOD-ified by:
 +
[INFO]:   (==> NMS MODS folder)"Black Carbon 2.1.pak"
 +
[INFO]: +  (==> NMS MODS folder)"True Icons 1.3.pak"</pre>
 +
You now know exactly wich mods are in conflict, here Black Carbon 2.1 and True Icons 1.3. And you can remove one of the two to solve the issue. Or ask in the mod thread if they can be used together (it is the case here, as depite a same texture is edited (SUBSTANCE.FUEL.1.DDS, the right one will be used.
  
Page content here...
+
== Extracting an old mod ==
 +
This first feature can come handy. Imagine you discovered the best mod ever but created 2 years ago and nobody ever updated it since then.<br>
 +
You obviously tested it first but no miracle, game doesn't load or you get weird artifacts instead of the clean mod effect.
 +
You are confident you could update this mod if you could extract its files but if PSARC never changed since the game release, there's no way to know which MBINCompiler version was used to create it.
 +
If you are in such a case, don't worry, just do the following :
 +
# download and extract [https://www.nexusmods.com/nomanssky/mods/957 AMUMSS] files.
 +
# place the .pak file of the mod inside AMUMSS' Modscript folder
 +
# Double Click BUILDMOD.BAT
 +
# When AMUMSS ask if you want to check for conflicts, hit the "N" key (No)
 +
# AMUMSS will try to open your .pak with all the known MBINCompiler version untill it eventualy finds the right one !
 +
# Once AMUMS has finished, you will get some yellow lines. hit a key to close its window
 +
# Open ModScript folder. you now have 2 folders. EXTRACTED_PAK containing the unpacked MBIN file and EXMLFILES_PAK containing the decompiled EXML files !
 +
You can now read the file and maybe recreate it for the current game version.
 +
 
 +
{{Warning Small|text=If when running AMUMSS, you get popup windows saying MBINCompiler has stopped functionning, just hit "close program" for each of them. Indeed, with older MBINCompiler versions, this error was raised. Anyway, AMUMSS will continue to test prior MBINCompiler version up to the right one}}
  
 
{{NMSPageClose}}
 
{{NMSPageClose}}

Revision as of 21:51, August 8, 2020

BannerLogo
Toying with AMUMSS

Contents

AMUMSS is a great tool offering a lot of possibilities via a scripting language.
But do you know it also brings very simple features that everyone can use ?

Detecting mod conflicts

Either you downloaded a new mod and can't see the changes ingame, or you have downloaded a lot of them from different authors and are unsure if they are all compatible or not, AMUMSS can help you sort it out. Indeed, AMUMSS has an integrated feature to compare all mods .pak contents and check if two or more mods edit the same file(s). How do use it. Very simple :

  1. download and extract AMUMSS files.
  2. Double Click BUILDMOD.BAT
  3. When AMUMSS ask if you want to check for conflicts, hit the "Y" key (Yes)
  4. AMUMSS will compare all your mods and generate a report. you can read it in the command line window but it's easier to close AMUMSS and open the file named REPORT.txt in AMUMSS folder.
  5. Each file found in two or more mods will be listed as CONFLICT as in the exemple below.
    [CONFLICT]: "TEXTURES\UI\FRONTEND\ICONS\U4SUBSTANCES\SUBSTANCE.FUEL.1.DDS" (Only in User paks below)
[INFO]: is MOD-ified by:
[INFO]: 		   (==> NMS MODS folder)"Black Carbon 2.1.pak"
[INFO]: 		+  (==> NMS MODS folder)"True Icons 1.3.pak"

You now know exactly wich mods are in conflict, here Black Carbon 2.1 and True Icons 1.3. And you can remove one of the two to solve the issue. Or ask in the mod thread if they can be used together (it is the case here, as depite a same texture is edited (SUBSTANCE.FUEL.1.DDS, the right one will be used.

Extracting an old mod

This first feature can come handy. Imagine you discovered the best mod ever but created 2 years ago and nobody ever updated it since then.
You obviously tested it first but no miracle, game doesn't load or you get weird artifacts instead of the clean mod effect. You are confident you could update this mod if you could extract its files but if PSARC never changed since the game release, there's no way to know which MBINCompiler version was used to create it. If you are in such a case, don't worry, just do the following :

  1. download and extract AMUMSS files.
  2. place the .pak file of the mod inside AMUMSS' Modscript folder
  3. Double Click BUILDMOD.BAT
  4. When AMUMSS ask if you want to check for conflicts, hit the "N" key (No)
  5. AMUMSS will try to open your .pak with all the known MBINCompiler version untill it eventualy finds the right one !
  6. Once AMUMS has finished, you will get some yellow lines. hit a key to close its window
  7. Open ModScript folder. you now have 2 folders. EXTRACTED_PAK containing the unpacked MBIN file and EXMLFILES_PAK containing the decompiled EXML files !

You can now read the file and maybe recreate it for the current game version.

Warning-Logo.png      Warning:If when running AMUMSS, you get popup windows saying MBINCompiler has stopped functionning, just hit "close program" for each of them. Indeed, with older MBINCompiler versions, this error was raised. Anyway, AMUMSS will continue to test prior MBINCompiler version up to the right one