dustyhansen

yea this appears to not be compatible with autoauth from umod? @LAGZYA

The name of the current tier is not showing in the message at the top left of the screen like it does in your example pictures.

I have input my key. I was able to add 1 skin successfully.

@AminoI am supposed to switch to your skin controller from skinbox today. Can you please reply here? You have multiple open tickets about skins getting lost on server restart too btw.

Downgrading Node,js seems to have fixed the issue!

I will give that a try. No, I didn't change anything in the code.

I do have Rust Edit installed.

I have a player reporting that Rodger's Dam is not working properly. There is a green card and red card room but there appear to be no fuse boxes to activate the doors. I am not sure if this is fixed in a later version already, but thought I would report it.

Even though it says in the console that these should not be spawning, they are still spawning on my server.

Same error when trying to add in-game. Tried another skin id and got the same error as well.

What does this mean? I tried adding a skin in the console and got this message.

@SrMiller I am running ver 20.7.0

hello?

I installed the plugin and the first cupboard I check is missing over half the names.

{ "Auto reload [If you change the config and save the file the plugin will reload itself]": true, "Day length [minutes]": 50, "Night length [minutes]": 10, "Use time control": true, "Presets": [ { "Name": "Clear", "Duration [seconds]": 3600, "Transition time [seconds]": 60, "Chance [0 - 100%": 80, "Wind": -1.0, "Rain": -1.0, "Thunder": -1.0, "Rainbow": -1.0, "Ocean": -1.0, "Atmosphere rayleigh": -1.0, "Atmosphere mie": -1.0, "Atmosphere contrast": -1.0, "Atmosphere directionality": -1.0, "Atmosphere fogginess": -1.0, "Atmosphere brightness": -1.0, "Clouds size": -1.0, "Clouds opacity": -1.0, "Clouds coverage": -1.0, "Clouds sharpness": -1.0, "Clouds coloring": -1.0, "Clouds attenuation": -1.0, "Clouds saturation": -1.0, "Clouds scattering": -1.0, "Clouds brightness": -1.0 }, { "Name": "Dust", "Duration [seconds]": 1800, "Transition time [seconds]": 60, "Chance [0 - 100%": 5, "Wind": 0.0, "Rain": 0.0, "Thunder": 0.0, "Rainbow": 0.0, "Ocean": 3.5, "Atmosphere rayleigh": 2.0, "Atmosphere mie": 4.0, "Atmosphere contrast": 1.25, "Atmosphere directionality": 0.75, "Atmosphere fogginess": 0.3, "Atmosphere brightness": 0.9, "Clouds size": 2.0, "Clouds opacity": 0.25, "Clouds coverage": 0.0, "Clouds sharpness": 0.0, "Clouds coloring": 1.0, "Clouds attenuation": 0.25, "Clouds saturation": 1.0, "Clouds scattering": 1.0, "Clouds brightness": 1.0 }, { "Name": "Fog", "Duration [seconds]": 1800, "Transition time [seconds]": 60, "Chance [0 - 100%": 2, "Wind": 0.0, "Rain": 0.0, "Thunder": 0.0, "Rainbow": 0.0, "Ocean": 4.5, "Atmosphere rayleigh": 1.0, "Atmosphere mie": 1.0, "Atmosphere contrast": 1.0, "Atmosphere directionality": 0.2, "Atmosphere fogginess": 0.9, "Atmosphere brightness": 0.5, "Clouds size": 2.0, "Clouds opacity": 0.0, "Clouds coverage": 0.0, "Clouds sharpness": 0.1, "Clouds coloring": 0.15, "Clouds attenuation": 0.15, "Clouds saturation": 0.8, "Clouds scattering": 100.0, "Clouds brightness": 0.8 }, { "Name": "Overcast", "Duration [seconds]": 1800, "Transition time [seconds]": 60, "Chance [0 - 100%": 10, "Wind": 0.0, "Rain": 0.0, "Thunder": 0.0, "Rainbow": 0.0, "Ocean": 3.5, "Atmosphere rayleigh": 0.2, "Atmosphere mie": 5.0, "Atmosphere contrast": 1.5, "Atmosphere directionality": 0.75, "Atmosphere fogginess": 0.5, "Atmosphere brightness": 0.9, "Clouds size": 2.0, "Clouds opacity": 1.0, "Clouds coverage": 1.0, "Clouds sharpness": 0.05, "Clouds coloring": 0.15, "Clouds attenuation": 0.15, "Clouds saturation": 0.8, "Clouds scattering": 20.0, "Clouds brightness": 1.0 }, { "Name": "RainMild", "Duration [seconds]": 1800, "Transition time [seconds]": 60, "Chance [0 - 100%": 10, "Wind": 1.0, "Rain": 0.2, "Thunder": 0.0, "Rainbow": 0.0, "Ocean": 4.7, "Atmosphere rayleigh": 1.0, "Atmosphere mie": 1.0, "Atmosphere contrast": 1.3, "Atmosphere directionality": 0.9, "Atmosphere fogginess": 0.2, "Atmosphere brightness": 1.0, "Clouds size": 1.0, "Clouds opacity": 1.0, "Clouds coverage": 0.4, "Clouds sharpness": 0.0, "Clouds coloring": 0.8, "Clouds attenuation": 0.05, "Clouds saturation": 0.8, "Clouds scattering": 0.4, "Clouds brightness": 1.0 }, { "Name": "RainHeavy", "Duration [seconds]": 1800, "Transition time [seconds]": 60, "Chance [0 - 100%": 10, "Wind": 1.0, "Rain": 1.0, "Thunder": 0.0, "Rainbow": 0.0, "Ocean": 7.4, "Atmosphere rayleigh": 0.2, "Atmosphere mie": 5.0, "Atmosphere contrast": 1.5, "Atmosphere directionality": 0.75, "Atmosphere fogginess": 0.7, "Atmosphere brightness": 0.8, "Clouds size": 2.0, "Clouds opacity": 1.0, "Clouds coverage": 0.9, "Clouds sharpness": 0.25, "Clouds coloring": 0.15, "Clouds attenuation": 0.15, "Clouds saturation": 0.8, "Clouds scattering": 5.0, "Clouds brightness": 1.0 }, { "Name": "Storm", "Duration [seconds]": 1800, "Transition time [seconds]": 60, "Chance [0 - 100%": 10, "Wind": 1.0, "Rain": 1.0, "Thunder": 1.0, "Rainbow": 0.0, "Ocean": 8.0, "Atmosphere rayleigh": 1.0, "Atmosphere mie": 3.0, "Atmosphere contrast": 1.3, "Atmosphere directionality": 0.75, "Atmosphere fogginess": 0.95, "Atmosphere brightness": 0.8, "Clouds size": 2.0, "Clouds opacity": 1.0, "Clouds coverage": 1.0, "Clouds sharpness": 0.4, "Clouds coloring": 0.15, "Clouds attenuation": 0.15, "Clouds saturation": 0.8, "Clouds scattering": 5.0, "Clouds brightness": 1.0 } ] }

I just had it go from Fog to Clear and the entire sky turned black then it turned back and the clouds turned black and then it was Clear. It was way more disruptive than just switching from Fog to Clear without a transition.

I am having issues with the weather not changing as well. For example, I have Fog set at 1800 seconds (30 minutes) and it stays foggy well over 30 minutes. I let it go to an hour before I manually changed it for the players.

Every time I go to use Skin Controller for the first time after a restart I get the attached message. If I enter the command again, Skin Controller loads normally. Is there a way to fix this? I don't want to tell my users that they have to ignore the message and do the command again.