Plugin error explainer
Paste an error from your Oxide or Carbon console. Get what went wrong in plain English and the code change that fixes it.
What it explains
Paste anything your server printed when a plugin failed: compile errors (error CS0246, CS1061, CS0103), runtime exceptions (NullReferenceException in a hook), or the "Failed to call hook" lines Oxide logs. You get the cause in plain English and, when the fix is in code, the lines to change.
Reading an Oxide compile error
KillRewards.cs(42,13): error CS1061: ... tells you three things:
- The file:
KillRewards.csin your plugins folder. - The position: line 42, column 13.
- The compiler code:
CS1061means a method or property does not exist on that type, often because a Rust update renamed it.
Errors after a Rust update
If plugins that worked yesterday fail on wipe day, the game changed under them. Our monthly update reports list the hooks and types that changed, and Update Guard repairs plugins you generated here automatically.
FAQ
Is it free?
Yes. You get 3 explanations a day, no account needed. The limit resets every day.
Should I paste the whole plugin?
Start with the error lines only. They include the file, line and error code, which is enough for most compile errors. For runtime errors, include the full stack trace.
Is what I paste stored?
The error text is sent to our server to generate the explanation and is not published. Do not paste passwords, RCON details or API keys.