Jump to content

Plugin wont load

Work in Progress 0.1.9

Hawkhill
Hawkhill

Posted

After each server restart, the plugin wont load.
Have to manually type in console oxide.reload WipeStatus
Then everything works fine until next restart.

image.png

IIIaKa

Posted

Changed Status from Pending to Work in Progress

IIIaKa

Posted (edited)

@Hawkhill
Hello, could you please provide more information about your server? What mod are you using, and what operating system?
Since your error is not a standard one, it seems that your server is complaining that the "serverinstance" field doesn’t exist in "WipeTimer", even though it’s present in the regular versions.

 

  

On 11/10/2025 at 7:45 AM, Hawkhill said:

image.png

 

image.png

 

Most likely, the issue here is with the compilation of your entire server.
Also, check the integrity of the server files and ensure they are up to date.

Edited by IIIaKa
Hawkhill

Posted

Sorry for late reply.... 
I dont know what OS the server is running.... Im renting it from Pinehosting. and it checks for updates / updating every server restart.
Other plugins im using works fine.
Its just this one that wont load proper after the server restarts.
The weird thing is that i cant find any errors in console after restart on this plugin. 
But in rust admin rcon thingy it comes up with the error on the screenshot..
When i manually load the plugin, everything works like it shoud.
image.png.59c4ed883a766ee7e438117e13540930.png

IIIaKa

Posted

On 11/17/2025 at 7:52 PM, Hawkhill said:

Sorry for late reply.... 
I dont know what OS the server is running.... Im renting it from Pinehosting. and it checks for updates / updating every server restart.
Other plugins im using works fine.
Its just this one that wont load proper after the server restarts.
The weird thing is that i cant find any errors in console after restart on this plugin. 
But in rust admin rcon thingy it comes up with the error on the screenshot..
When i manually load the plugin, everything works like it shoud.
image.png.59c4ed883a766ee7e438117e13540930.png

Hello. This seems to be a peculiarity of your server/hosting. Try doing the same on your own local machine, the plugin will compile and start without any problems after restarting the server.
For some reason, at the moment when plugins are being compiled, the "serverinstance" property is missing in the "WipeTimer" class, and not just "null", but completely absent, even though it does exist on normal servers. Because of this, the plugin fails to compile and doesn't load.
However, after your server fully starts, the "serverinstance" property appears and the plugin compiles without any issues.

I also recommend contacting your hosting provider's tech support and asking why the "serverinstance" property is missing in the "WipeTimer" class during plugin compilation, and how exactly the server startup process works on their side. Is it the standard procedure, or have they modified something?

IIIaKa

Posted (edited)

You have a few temporary workarounds:

1) Replace:

if (WipeTimer.serverinstance != null)
	result = WipeTimer.serverinstance.GetTimeSpanUntilWipe();
else
{
	PrintError("The custom date list is empty and the vanilla wipe date could not be obtained! The first Thursday of the next month will be used instead.");
	result = GetNextFirstThursdayOfMonth() - DateTime.UtcNow;
}

with:

result = GetNextFirstThursdayOfMonth() - DateTime.UtcNow;

However, you will lose the ability to get the vanilla(in-build) wipe date;

2) Manually restart the WipeStatus plugin each time, "o.reload WipeStatus";

3) I can create a small workaround plugin for you that will automatically restart the plugin after WipeStatus has fully initialized.

Edited by IIIaKa
2.1m

Downloads

Total number of downloads.

9.7k

Customers

Total customers served.

140.9k

Files Sold

Total number of files sold.

3m

Payments Processed

Total payments processed.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.