Babscoole is currently the manager of Exosolar's mods.
You can post questions here on NexusMods, and both Babscoole and Exosolar check the boards enough that you will get an answer within a handful of days. But for the fastest response, you can contact us through Discord instead.
You can contact Babscoole on discord at Babscoole#6326 You can also contact Exosolar on discord at Exosolar#5120
That's for color, but sort of the default settings. NMS RGB is normal RGB divided by 255. Conversely to convert from NMS to normal RGB, multiply by 255. You can try setting the values for WaterFogColourNear to the same as for WaterFogColourFar and see what happens. The colors are VERY much impacted by the settings in the palette applied itself as well though. In the script itself, the palette values are numbers in a table. In the actual file, line 6 of the script looks like this:
<Property value="GcPlanetWaterColourData.xml"> <Property name="WaterFogColourNear" value="Colour.xml"> <Property name="R" value="0.1751" /> <Property name="G" value="0.1751" /> <Property name="B" value="0.1751" /> <Property name="A" value="1" /> </Property> <Property name="WaterFogColourFar" value="Colour.xml"> <Property name="R" value="0.232752" /> <Property name="G" value="0.232752" /> <Property name="B" value="0.232752" /> <Property name="A" value="1" /> </Property> <Property name="WaterColourBase" value="Colour.xml"> <Property name="R" value="0.003" /> <Property name="G" value="0.003" /> <Property name="B" value="0.003" /> <Property name="A" value="1" /> </Property> <Property name="WaterColourAdd" value="Colour.xml"> <Property name="R" value="0.004" /> <Property name="G" value="0.004" /> <Property name="B" value="0.004" /> <Property name="A" value="1" /> </Property> <Property name="FoamColour" value="Colour.xml"> <Property name="R" value="0" /> <Property name="G" value="0" /> <Property name="B" value="0" /> <Property name="A" value="0" /> </Property> </Property> So may only be like that on the current planets you're exploring and different on others, depending which palette is randomly assigned.
I used the version that includes jasondude's mod since I had been running that one, however it changed the color of some of my ships. I'm guessing it's a conflict with True Color.
I don't know what true color does, but Abyss only makes changes to METADATA\SIMULATION\SOLARSYSTEM\COLOURS\WATERCOLOURS.MBIN and GCWATERGLOBALS.GLOBAL.MBIN, which ships don't use for color. Could be another mod though, that makes changes to BASECOLOURPALETTES. Do a conflict check with AMUMSS to find which mod .paks have that file.
I checked Courtycats TrueColor. It changes METADATA\SIMULATION\SOLARSYSTEM\COLOURS\BASECOLOURPALETTES.MBIN and METADATA\GAMESTATE\PLAYERDATA\CUSTOMISATIONCOLOURPALETTES.MBIN only. Completely different files than Abyss. You need to find which other mod(s) change one of those or both to find your ship color change culprit. :)
Just the kind of mod i was looking for! since the LASAGNA biome generation mod retired , i have been trying to find some mods that do something similar, and lasagna had a water color changer, and since it is retried, i have been trying to find a water color changer mod, and this is perfect, if it does not work right off the bat, i will use the Lua to automatically update it, and i am waiting for better planet generation to be updated, so i will have the perfect mod combo!
I just checked and working fine on this end. May be problematic if trying to combine with other water mods, such as ARGHWater or possibly use of ReShade.
To clarify on Babscoole, Arghwater is fully compatible with Abyss but it's still possible that Arghwater itself is temporarily incompatible with a new version of NMS.
Help me, there is a bug that the seas are all white in the discovery interface, I already removed all my mods, I left only this one and the seas are still white. I use Jasondude version and Exosolar's Hybrid Abyss.
Yes, they should work fine at the same time. I don't believe BPG makes changes to either METADATA\SIMULATION\SOLARSYSTEM\COLOURS\WATERCOLOURS.MBIN GCWATERGLOBALS.GLOBALS.MBIN.
You can use the conflict check in AMUMSS to be certain though.
Could you please enable the "Download with Manager" button? Mod Organizer is able to manage NMS mods; meaning it can download and install them directly from Nexus.
Do you happen to have a link to Mod Organizer. Want to take a look first. I turn that off because I've seen problems with some mods and mod managers in the past and I don't want to get stuck trying to support various mod managers. :)
Edit: NM, found the link from Stepmod. :) I've enabled mod manager again.
It can easily be installed manually. It just an extra step. So if you're concerned about other managers, it's not a big deal. I only asking for convenience. :) I can tell the Step users to download and install manually.
The LUA was never meant to be in the zip bare like that, was a mistake on my part with the last update. The LUA ONLY makes the changes to GCWATERGLOBALS.GLOBALS, but does not add the new colors. If you wish, you can extract the .pak file. There you will find the LUA and the METADATA\SIMULATION\SOLARSYSTEM\COLOURS\WATERCOLOURS.MBIN, which must be added into ModExtraFilesToInclude in AMUMSS.
Which means I've been screwing up my merges for who knows how long. Awesome. THANK YOU for taking a minute to impart some sorely-needed kernels of wisdom on modding NMS. Very much appreciated ! =)
Happy to oblige. Yeah, the LUA repo is quite handy. I'd say in the high 90th percentile of LUA scripts ever written for NMS. Even some private ones that have never been published with a MOD on Nexus.
Give Feedback
73 comments
You can post questions here on NexusMods, and both Babscoole and Exosolar check the boards enough that you will get an answer within a handful of days. But for the fastest response, you can contact us through Discord instead.
You can contact Babscoole on discord at Babscoole#6326
You can also contact Exosolar on discord at Exosolar#5120
{
["PRECEDING_KEY_WORDS"] = {"WaterFogColourNear"},
["VALUE_CHANGE_TABLE"] =
{
{"R", "0.02"},
{"G", "0.02"},
{"B", "0.02"},
}
<Property value="GcPlanetWaterColourData.xml">
So may only be like that on the current planets you're exploring and different on others, depending which palette is randomly assigned.<Property name="WaterFogColourNear" value="Colour.xml">
<Property name="R" value="0.1751" />
<Property name="G" value="0.1751" />
<Property name="B" value="0.1751" />
<Property name="A" value="1" />
</Property>
<Property name="WaterFogColourFar" value="Colour.xml">
<Property name="R" value="0.232752" />
<Property name="G" value="0.232752" />
<Property name="B" value="0.232752" />
<Property name="A" value="1" />
</Property>
<Property name="WaterColourBase" value="Colour.xml">
<Property name="R" value="0.003" />
<Property name="G" value="0.003" />
<Property name="B" value="0.003" />
<Property name="A" value="1" />
</Property>
<Property name="WaterColourAdd" value="Colour.xml">
<Property name="R" value="0.004" />
<Property name="G" value="0.004" />
<Property name="B" value="0.004" />
<Property name="A" value="1" />
</Property>
<Property name="FoamColour" value="Colour.xml">
<Property name="R" value="0" />
<Property name="G" value="0" />
<Property name="B" value="0" />
<Property name="A" value="0" />
</Property>
</Property>
Abyss or Hybrid Abyss?
Running any other mods that make changes to GCWATERGLOBALS.GLOBALS.MBIN or METADATA\SIMULATION\SOLARSYSTEM\COLOURS\WATERCOLOURS.MBIN?
METADATA\SIMULATION\SOLARSYSTEM\COLOURS\WATERCOLOURS.MBIN
GCWATERGLOBALS.GLOBALS.MBIN.
You can use the conflict check in AMUMSS to be certain though.
Do you happen to have a link to Mod Organizer.Want to take a look first. I turn that off because I've seen problems with some mods and mod managers in the past and I don't want to get stuck trying to support various mod managers. :)Edit: NM, found the link from Stepmod. :) I've enabled mod manager again.