Hmm, that's odd - I even redownloaded and copied it back in to be sure I hadn't used it wrong. Maybe it's a conflict with something else though I can't see what it would be.
Maybe I'll try seting AMUMSS up again from scratch :/
It said that there was an error on a particular line, but unfortunately I can't give you the exact error as I've now deleted it to re-install AMUMSS
A little further testing showed that if I removed the mod it thought was faulty it would then report a *different* mod as faulty next run, and so on and so on.
I think a fresh AMUMSS install is probably a good starting point as my previous one was upgraded from many versions ago. If I'm still having issues after that I'll havce to try narrowing down the fault.
Thanks for trying to help anyway, I'm now certain it's not your mod that's the problem.
I'm still getting an error after reinstalling AMUMSS.
Report ends with this :
>>> FINAL REPORT <<< [ATTENTION] Failed scripts: [ >>>] - Check Report: Failed to compile some/all files in MODBUILDER\MOD [ATTENTION] 1 [[ERROR]] detected [ >>>] #59/59 [[Unsorted Saves 4.0.lua]] [1] [ATTENTION] ERRORS will NOT produce MBIN files and a complete PAK file may not have been created. [ATTENTION] You need to correct the error first!
And if I look for the actual error I'm getting this :
[[ERROR]] MBINCompiler = [ExmlException]: There is an error in XML document (460, 3) => check your script! [PSARC] The PAK will not include this EXML [ERR] MBINCompiler = [InvalidOperationException] [ERR] MBINCompiler = [XmlException]: The 'Property' start tag on line 110 position 10 does not match the end tag of 'Data'. Line 460, position 3. [ERR] MBINCompiler = [INFO]: E:\NMS Modding\AMUMSS\MODBUILDER\MOD\MODELS\PLANETS\BIOMES\COMMON\BUILDINGS\PARTS\COMMONPARTS\OBSERVATORY\HOLOGRAM.SCENE.EXML Created this PAK: [[~PatchMod_COMBINED_Better Charge Icons+Better Empty Slots+Better Scanning Icons 1.2+New Summon Freighter Icon+No Red Landing .pak]] Ending MBIN/PAK phase... Ended script [[Unsorted Saves 4.0.lua]] in 5.042 sec
This looks like it's actually a different mod causing it but the error is showing up under Unsorted Saves presumably because that's the *last* script?
I have a bunch of your mods in my ModScript folder currently, and no other mods from elsewhere, unfortunately I have no idea which mod might be editing that value. I'll have to do the old half and half method until I find it I guess.
A quick search through the mod lua scripts finds only one reference to that file in ReLight, will confirm if that is the issue.
I'm curious to know if it's possible to give the saves custom names. Like 'expedition 1' or 'archeologist'. As an additional way to keep track of which is which.
No longer appears to function, as of Sep 8, if not earlier. The new expedition 3 save I just created immediately moved to the top of the list, ahead of four much older saves. It only moved down one slot after I loaded and saved another file, so the game is auto-sorting in spite of the mod.
I made certain Disablemods.txt is gone from PCBANKS\Mods I am not using any other mods that alter debug options (texture changes only).
I wonder if this has to do with how the list fundamentally changed due to supporting up to 15 saves and how it now scrolls if there are enough saves present.
I have less than 5 saves so no scroll for me (maybe a reason) but my oldest save made on the original game version is still displayed on the top despite my other more recent saves.
67 comments
I'm getting a lua script error in AMUMSS for the current public build
Maybe I'll try seting AMUMSS up again from scratch :/
A little further testing showed that if I removed the mod it thought was faulty it would then report a *different* mod as faulty next run, and so on and so on.
I think a fresh AMUMSS install is probably a good starting point as my previous one was upgraded from many versions ago. If I'm still having issues after that I'll havce to try narrowing down the fault.
Thanks for trying to help anyway, I'm now certain it's not your mod that's the problem.
Report ends with this :
>>> FINAL REPORT <<<
[ATTENTION] Failed scripts:
[ >>>] - Check Report: Failed to compile some/all files in MODBUILDER\MOD
[ATTENTION] 1 [[ERROR]] detected
[ >>>] #59/59 [[Unsorted Saves 4.0.lua]] [1]
[ATTENTION] ERRORS will NOT produce MBIN files and a complete PAK file may not have been created.
[ATTENTION] You need to correct the error first!
And if I look for the actual error I'm getting this :
[[ERROR]] MBINCompiler = [ExmlException]: There is an error in XML document (460, 3) => check your script!
[PSARC] The PAK will not include this EXML
[ERR] MBINCompiler = [InvalidOperationException]
[ERR] MBINCompiler = [XmlException]: The 'Property' start tag on line 110 position 10 does not match the end tag of 'Data'. Line 460, position 3.
[ERR] MBINCompiler = [INFO]: E:\NMS Modding\AMUMSS\MODBUILDER\MOD\MODELS\PLANETS\BIOMES\COMMON\BUILDINGS\PARTS\COMMONPARTS\OBSERVATORY\HOLOGRAM.SCENE.EXML
Created this PAK: [[~PatchMod_COMBINED_Better Charge Icons+Better Empty Slots+Better Scanning Icons 1.2+New Summon Freighter Icon+No Red Landing .pak]]
Ending MBIN/PAK phase...
Ended script [[Unsorted Saves 4.0.lua]] in 5.042 sec
This looks like it's actually a different mod causing it but the error is showing up under Unsorted Saves presumably because that's the *last* script?
I have a bunch of your mods in my ModScript folder currently, and no other mods from elsewhere, unfortunately I have no idea which mod might be editing that value. I'll have to do the old half and half method until I find it I guess.
A quick search through the mod lua scripts finds only one reference to that file in ReLight, will confirm if that is the issue.
3.9 version should be fine again.
I made certain Disablemods.txt is gone from PCBANKS\Mods
I am not using any other mods that alter debug options (texture changes only).
I wonder if this has to do with how the list fundamentally changed due to supporting up to 15 saves and how it now scrolls if there are enough saves present.
Thank you for maintaining it.