Building Skins 2.0.10

33 minutes ago, Wilogarl said:

Players who own the DLC could no longer use their skins, when trying to skin the original skin was used

 

Correct. Players that own the skins can no longer use them. They skin to default stone or metal not adobe or container. Only does this after yesterday's update. Please fix

Ok so here is the scenario that happened. We took heli and after we went around to repair the base and everything we hit to repair was switched back to the default sheet metal skin. Is that something I would just need to disable first before repairing?

I would recommend uninstalling until issues are addressed in an update tbh

1 hour ago, Dead Nasty said:

I would recommend uninstalling until issues are addressed in an update tbh

ok thank you for the quick response.

2 hours ago, Dead Nasty said:

Ich würde die Deinstallation empfehlen, bis die Probleme in einem Update behoben sind

I have also handled it this way

Latest version pumps out

building skins imagelibrary not found plugin disabled

would this be in conflict  with skinner?

The earlier version without shipping container still works

OK i am an idiot this newer release uses image library  https://umod.org/plugins/image-library

Any way to use "bskin all" to switch everything back to non-DLC?

Hello, I have a problem with the plugin, it doesn't work for me. Nothing comes out. nor the GUI, nor anything.
I have all the permissions and I am the administrator, I also tried all the commands and nothing. And I only get this warning in the chat.
SKIN UPGRADE IS NOT REQUIRED FOR {0} AVAILABLE BUILDINGS
And this in the console;
 

When stone is upgraded to steel or iron is upgraded to steel, it will become thatch, and the upgrade is not correct

When stone is upgraded to steel or iron is upgraded to steel, it will become thatch, and the upgrade is not correct

12 hours ago, Bear Grills said:

Any way to use "bskin all" to switch everything back to non-DLC?

change the desired skin in the menu and use the command / bskin all

12 hours ago, Lei_Wong said:

Hello, I have a problem with the plugin, it doesn't work for me. Nothing comes out. nor the GUI, nor anything.
I have all the permissions and I am the administrator, I also tried all the commands and nothing. And I only get this warning in the chat.
SKIN UPGRADE IS NOT REQUIRED FOR {0} AVAILABLE BUILDINGS
And this in the console;
 

unload the plugin and delete the config file

46 minutes ago, Warmth said:

When stone is upgraded to steel or iron is upgraded to steel, it will become thatch, and the upgrade is not correct

remove the auto-upgrade plugin that you are using or replace it with the one that is fixed for updating with dls

2 hours ago, ☞Марат☞ said:

remove the auto-upgrade plugin that you are using or replace it with the one that is fixed for updating with dls

No other auto-upgrade plug-ins are installed, only this building skin plug-in is installed

A player in question purchased the container DLC, but before buying it, they activated the bskin at some point and later deactivated it. When trying to use the purchased DLC, the system automatically transforms it into metal because the bskin is deactivated. Is there any way to implement a check to see if the person has the DLC or add a disable button to the interface? Thank you for the plugin... it's fantastic.

On 5/6/2023 at 12:45 PM, CupsOhJoe said:

Would love to see it apply the skin after the structure is built

100%

Cool story bro 

2 hours ago, Dead Nasty said:

Guessing this isn't gonna be fixed any time soon. Well it was cool the few days it lasted. Later tater. 

You need to be more patient. This is a free plugin and I do it in my free time.

On 6/7/2023 at 8:30 AM, Wilogarl said:

Players who own the DLC could no longer use their skins, when trying to skin the original skin was used

 

Why would a player enable this if they own the skins? Perhaps only sell the permission to players that want to use it, or tell owners of skins to not be so thick headed. 

Failed to call hook 'OnServerInitialized' on plugin 'BuildingSkins v1.0.8' (NullReferenceException: Object reference not set to an instance of an object)
at Oxide.Plugins.BuildingSkins.OnServerInitialized () [0x0009f] in <3637d6d213be4a42b927eb2391038c1e>:0
at Oxide.Plugins.BuildingSkins.DirectCallHook (System.String name, System.Object& ret, System.Object[] args) [0x00100] in <3637d6d213be4a42b927eb2391038c1e>:0
at Oxide.Plugins.CSharpPlugin.InvokeMethod (Oxide.Core.Plugins.HookMethod method, System.Object[] args) [0x00079] in <23ba99f131254889867c71f0bd137b1d>:0
at Oxide.Core.Plugins.CSPlugin.OnCallHook (System.String name, System.Object[] args) [0x000d8] in <157a94ee66ab4a7991faecd1eb84be3b>:0
at Oxide.Core.Plugins.Plugin.CallHook (System.String hook, System.Object[] args) [0x00060] in <157a94ee66ab4a7991faecd1eb84be3b>:0

3 hours ago, Dead Nasty said:

Guessing this isn't gonna be fixed any time soon. Well it was cool the few days it lasted. Later tater. 

You could also open the BuildingSkins.cs file and fix it by yourself   But complaining is easier, isn't it?

Got this after updating:

 

Failed to call hook 'OnServerInitialized' on plugin 'BuildingSkins v1.0.8' (NullReferenceException: Object reference not set to an instance of an object)

at Oxide.Plugins.BuildingSkins.OnServerInitialized () [0x0009f] in <455b87802c5e4d35903b9709add8c34e>:0

at Oxide.Plugins.BuildingSkins.DirectCallHook (System.String name, System.Object& ret, System.Object[] args) [0x00100] in <455b87802c5e4d35903b9709add8c34e>:0

at Oxide.Plugins.CSharpPlugin.InvokeMethod (Oxide.Core.Plugins.HookMethod method, System.Object[] args) [0x00079] in <23ba99f131254889867c71f0bd137b1d>:0

at Oxide.Core.Plugins.CSPlugin.OnCallHook (System.String name, System.Object[] args) [0x000d8] in <157a94ee66ab4a7991faecd1eb84be3b>:0

at Oxide.Core.Plugins.Plugin.CallHook (System.String hook, System.Object[] args) [0x00060] in <157a94ee66ab4a7991faecd1eb84be3b>:0

1 hour ago, Chiyo said:

You could also open the BuildingSkins.cs file and fix it by yourself   But complaining is easier, isn't it?

ill keep that in mind. 

4 hours ago, Watcher said:

Failed to call hook 'OnServerInitialized' on plugin 'BuildingSkins v1.0.8' (NullReferenceException: Object reference not set to an instance of an object)
at Oxide.Plugins.BuildingSkins.OnServerInitialized () [0x0009f] in <3637d6d213be4a42b927eb2391038c1e>:0
at Oxide.Plugins.BuildingSkins.DirectCallHook (System.String name, System.Object& ret, System.Object[] args) [0x00100] in <3637d6d213be4a42b927eb2391038c1e>:0
at Oxide.Plugins.CSharpPlugin.InvokeMethod (Oxide.Core.Plugins.HookMethod method, System.Object[] args) [0x00079] in <23ba99f131254889867c71f0bd137b1d>:0
at Oxide.Core.Plugins.CSPlugin.OnCallHook (System.String name, System.Object[] args) [0x000d8] in <157a94ee66ab4a7991faecd1eb84be3b>:0
at Oxide.Core.Plugins.Plugin.CallHook (System.String hook, System.Object[] args) [0x00060] in <157a94ee66ab4a7991faecd1eb84be3b>:0

3 hours ago, RetroMaja said:

Got this after updating:

 

Failed to call hook 'OnServerInitialized' on plugin 'BuildingSkins v1.0.8' (NullReferenceException: Object reference not set to an instance of an object)

at Oxide.Plugins.BuildingSkins.OnServerInitialized () [0x0009f] in <455b87802c5e4d35903b9709add8c34e>:0

at Oxide.Plugins.BuildingSkins.DirectCallHook (System.String name, System.Object& ret, System.Object[] args) [0x00100] in <455b87802c5e4d35903b9709add8c34e>:0

at Oxide.Plugins.CSharpPlugin.InvokeMethod (Oxide.Core.Plugins.HookMethod method, System.Object[] args) [0x00079] in <23ba99f131254889867c71f0bd137b1d>:0

at Oxide.Core.Plugins.CSPlugin.OnCallHook (System.String name, System.Object[] args) [0x000d8] in <157a94ee66ab4a7991faecd1eb84be3b>:0

at Oxide.Core.Plugins.Plugin.CallHook (System.String hook, System.Object[] args) [0x00060] in <157a94ee66ab4a7991faecd1eb84be3b>:0

try unloading the plugin and deleting the date file

4 hours ago, Chiyo said:

You could also open the BuildingSkins.cs file and fix it by yourself   But complaining is easier, isn't it?

That dude is always like that. 

Last working version (for me, without edits) from what I could see was 1.0.5.

Fix yourselves or wait for updates.