After a daily server restart RealPVE is not compiling, what can be done to resolve this as people can just raid when not loaded? again im going to have to go back to a different pve plugin

By @original4d
 

Quote

After a daily server restart RealPVE is not compiling, what can be done to resolve this as people can just raid when not loaded? again im going to have to go back to a different pve plugin  

@original4d

To solve any problem, it is essential to understand what is causing it. Without providing the necessary information, such as installed plugins, error logs(especially), configurations, etc., this is not possible.

@original4d
And I strongly urge you to create a support ticket with more detailed information about the issue, rather than posting in the discussion section, as troubleshooting in that section will only lead to confusion.

So I found this in the logs. I'm still going to leave the llugin unloaded......

Changed Status from Pending to Work in Progress

Which modification are you using? uMod or Carbon? Also, I need to know the list of installed plugins.
Because this error indicates that HumanNPC does not contain skinID, although this is not the case. HumanNPC is a class from Rust itself, which, through multiple inheritances, inherits from BaseEntity and has the skinID property.
You should check the integrity of this file: *SERVER*\RustDedicated_Data\Managed\Assembly-CSharp.dll

I have a slight suspicion that you have the HumanNPC plugin by Razor installed, and the compiler thinks my plugin is referencing his HumanNPC class instead of the HumanNPC class from the game itself.

Yes, the problem arises because the HumanNPC plugin has the exact same name as the in-game class HumanNPC that my plugin references.
So, when starting/restarting, the compiler mistakenly thinks my plugin refers not to the in-game class but to the plugin, leading to an error.
That's why detailed information is crucial.

Changed Status from Work in Progress to Closed

Changed Fixed In to Next Version

I've resolved the issue, so it won't occur in the next update.
However, if you'd like to fix this problem immediately, feel free to message me privately, and I'll send you the corrected file.

If the issue persists, feel free to report it in this thread.