Skinner 3.1.3

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!

On 2/13/2026 at 1:19 PM, Kapco411 said:

Try this patch Whiskers made. It may resolve this issue for you. 

ItemMoveRPCPatch.cs 2.22 kB · 0 downloads

Yes, now it works fine. Is this fixing an temporary issue from Oxide? 

1 hour ago, Dr.D.Bug said:

Yes, now it works fine. Is this fixing an temporary issue from Oxide? 

Its a facepunch issue but yes this temp fixes the problem.

Does this player have all the correct permissions to use the plugin and is this an RPC kick by chance?

29 minutes ago, Kapco411 said:

Does this player have all the correct permissions to use the plugin and is this an RPC kick by chance?

Yes, the player has all the necessary permissions and it is also an RPC kick. In this case, however, it only affects skins with the Miners Hat. All other skins are not affected. Even as an admin, this happens to me too. Every player is or was affected by this until now. Now, with this new plugin from you, or rather from Whiskers, everything works fine.

is there a skinremove command? or do i have to manually remove from the data file

Some of my players have reported and I just personally witnessed a null reference kick when skinning mining hat.

6 hours ago, Whispers88 said:

This is a facepunch bug, they are aware of it. You can use this to patch the issue for now.

ItemMoveRPCPatch.cs 2.22 kB · 1 download

Ok Whispers I will give it a go! Thank you for a fix!

DLC skins are no longer available in skin add-ons, so it would be nice if you took a little price cut. :I need, but my budget is limited

Still getting this on bootup all month:

[Skinner] Processed 175/175 workshop skins (batch completed: 0 updated/added from API response).
Navmesh Source Collecting took 256.34 seconds
Starting Monument Navmesh Build with 6393 sources
[Skinner] Finished processing workshop skin imports. Total processed: 175/175
[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 <7f2363d476d34cb39ec024441638e397>:0 
  at Oxide.Plugins.Skinner.UpdateImportedSkins () [0x00196] in <7f2363d476d34cb39ec024441638e397>:0 
  at Oxide.Plugins.Skinner+<GetSteamWorkshopSkinData>d__192.MoveNext () [0x005fe] in <7f2363d476d34cb39ec024441638e397>:0 
  at UnityEngine.SetupCoroutine.InvokeMoveNext (System.Collections.IEnumerator enumerator, System.IntPtr returnValueAddress) [0x00026] in <90c589ebc24b486c9e5903521dacec9d>:0 

30 minutes ago, Rockefeller said:

Still getting this on bootup all month:

[Skinner] Processed 175/175 workshop skins (batch completed: 0 updated/added from API response).
Navmesh Source Collecting took 256.34 seconds
Starting Monument Navmesh Build with 6393 sources
[Skinner] Finished processing workshop skin imports. Total processed: 175/175
[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 <7f2363d476d34cb39ec024441638e397>:0 
  at Oxide.Plugins.Skinner.UpdateImportedSkins () [0x00196] in <7f2363d476d34cb39ec024441638e397>:0 
  at Oxide.Plugins.Skinner+<GetSteamWorkshopSkinData>d__192.MoveNext () [0x005fe] in <7f2363d476d34cb39ec024441638e397>:0 
  at UnityEngine.SetupCoroutine.InvokeMoveNext (System.Collections.IEnumerator enumerator, System.IntPtr returnValueAddress) [0x00026] in <90c589ebc24b486c9e5903521dacec9d>:0 

i had that to , my fix was - stop the plugin - delete the .cs and the data files - redownloaded fresh .cs  - installed it and its fine

Will this now skip dead skins and go to the next or does it still hang everything up?  Tnx

33 minutes ago, LoneWolf71 said:

Will this now skip dead skins and go to the next or does it still hang everything up?  Tnx

use the client option in f1 console

graphics.itemskintimeout 20

the default is 60 seconds, so any skin the client has issues with, it will take 60 seconds before it moves on, so if you lower the threshold, it will move on faster

so in your case, you should also go through your skins and remove the dead ones manually so the players dont get timeouts on bad skins. 
(edit: of course if your internet is shite, thats gonna fail a lot more on downloading skins if you move the timer up. as the client downloads any skin in it tries to load to your PC)

At the moment, when we stack boxes using the Chest Stacks plugin from supreme and then want to skin them using the /si command, I skin the bottom box only, for example, but then the entire stack is given the same skin. Could there be a problem with the interaction between your two plugins?

2 hours ago, Whispers88 said:

what do you mean by dead skins? if the ids dont exist the API wont find them, which is a really quick lookup

I had a bunch of skins, when it hit one that didn't work it froze everything, or wouldn't load anything at all.  I moves to skinbox as it skips over skins that are broken and works fine.  Then there was this: