You are setting d.alarmColorDefault twice. So instead of creating a setting with the name "searchlight-assault-alarm-color" and default value "230,25,25,230" you are creating a setting with name "230,25,25,230" and default value "230,25,25,230". But because the replacement is consistent everywhere the setting is used, it doesn't cause any user-facing errors.
Discovered this when I was working on a modpack that includes your mod and changes your mod's settings:
-- Set warning color and safe color to 230/230/230/230
-- Set alarm color to 255/255/255/230
--Settings.setDefault("searchlight-assault-safe-color", "string", "230,230,230,230")
--Settings.setDefault("searchlight-assault-warn-color", "string", "230,230,230,230")
--Settings.setDefault("searchlight-assault-alarm-color", "string", "255,255,255,230")
-- Lines above do not work, instead I have to do:
Settings.setDefault("250,190,0,230", "string", "230,230,230,230")
Settings.setDefault("230,25,25,230", "string", "230,230,230,230")
Settings.setDefault("20,230,20,230", "string", "255,255,255,230")
Hi, this is a minor bug in your sl-defines.lua:
You are setting
d.alarmColorDefault
twice. So instead of creating a setting with the name "searchlight-assault-alarm-color" and default value "230,25,25,230" you are creating a setting with name "230,25,25,230" and default value "230,25,25,230". But because the replacement is consistent everywhere the setting is used, it doesn't cause any user-facing errors.Discovered this when I was working on a modpack that includes your mod and changes your mod's settings: