Skinner 3.1.1

On 2/10/2026 at 4:20 PM, Rockefeller said:

FYI looking through my server logs and found this at boot up.  Skinner is on newest version.

 

"[Skinner] Processed 209/209 workshop skins (batch completed: 0 updated/added from API response).
[Skinner] Finished processing workshop skin imports. Total processed: 209/209
[Skinner] Saved Workshop Skins
Duplicate permission registered 'skinner.default' (by plugin 'Skinner')
[Skinner] Saved Workshop Skins
NullReferenceException: Object reference not set to an instance of an object
  at Oxide.Plugins.Skinner.UpdateSkinKeys () [0x000b9] in <c1d68007eae84b73a89b8347f7f435b1>:0 
  at Oxide.Plugins.Skinner.UpdateImportedSkins () [0x00196] in <c1d68007eae84b73a89b8347f7f435b1>:0 
  at Oxide.Plugins.Skinner+<GetSteamWorkshopSkinData>d__192.MoveNext () [0x005fe] in <c1d68007eae84b73a89b8347f7f435b1>:0 
  at UnityEngine.SetupCoroutine.InvokeMoveNext (System.Collections.IEnumerator enumerator, System.IntPtr returnValueAddress) [0x00026] in <90c589ebc24b486c9e5903521dacec9d>:0 "

are you running item perks or epic loot by any chance?

Hi! One of my players is having a consistent issue when using the /skin command.

When he tries to load a skin on an item, a few things happen:

Some items inside his base get automatically reskinned back to default, even though he didn’t touch them.

He gets kicked from the server with a very long error message.

The item he tries to skin (for example a shirt) only loads the icon, but the skin never applies to the character model.

It looks like the plugin is reskinning objects it shouldn’t touch, and then triggers a kick when the skin fails to apply properly.

Could you take a look at this? If you need logs, screenshots, or the exact kick message, I can provide it.

Thanks in advance!