# Read the first useful line in a Rust plugin compile error

[Rust server guides](https://rustsc.com/learn/index.html.md) / [Troubleshooting](https://rustsc.com/learn/troubleshooting/index.html.md)

Copy the earliest error attached to the plugin you tried to load. Include the file, line and diagnostic code if the framework prints one. Later errors can follow from the first, so give that one your attention before changing several files.

## Decode the first diagnostic

The examples below are abbreviated. Keep the unabridged version for the maintainer.

| First clue | Check on a spare server | When to stop |
| --- | --- | --- |
| A named required plugin, type or assembly is missing | Open the plugin's dependency instructions. Check whether the named dependency is the expected version and has a load entry of its own. | If the dependency has its own compile error, resolve that first. |
| A namespace already contains a definition, such as CS0101 | Search the active plugins folder for two files containing the same type. A second downloaded copy can carry a numbered filename while keeping the original type. | Keep the original package together if its author intentionally distributes more than one file. Move an identified extra copy outside the active folder. |
| A member cannot be found, such as CS1061 | Check whether the plugin author supports this game and framework build. Check the missing member and recent releases for this plugin or its required dependency. | If many unrelated plugins fail together after a Rust update, confirm framework compatibility first. Do not replace the missing code with a guess. |

## Wait for the actual verdict

Watch the console after a reload request. In our disposable Oxide and Carbon tests, the request could answer before the compiler printed the error. A test source with the wrong value type produced a named file and location after the request. Check the current plugin list and version at the end of the attempt, then try the player action once.

## Give the maintainer one repairable case

Send the plugin version and original download source, the Rust and framework versions, the exact diagnostic and the smallest change that produced it. Say whether a fresh unedited download fails too, if you checked on a clean compatible copy. Remove any credentials or player data from the excerpt. Once the new file compiles and remains loaded, try the same player action as the final check.

## Sources

- [Oxide installation and compilation](https://docs.oxidemod.com/guides/owners/install-plugins)
- [Oxide on required versus optional dependencies](https://docs.oxidemod.com/guides/reviewers/guidelines/dependencies)
- [Microsoft on duplicate definitions](https://learn.microsoft.com/en-us/dotnet/csharp/language-reference/compiler-messages/using-directive-errors)
- [Microsoft on a missing member](https://learn.microsoft.com/en-us/dotnet/csharp/language-reference/compiler-messages/cs1061)

## Related resources

- [Why did your Rust plugin compile but fail to load?](https://rustsc.com/learn/troubleshooting/rust-plugin-compiles-but-does-not-load/index.html.md)
- [Which Rust plugin dependencies should you install first?](https://rustsc.com/learn/setup/install-rust-plugin-dependencies-in-order/index.html.md)
- [Find and manage plugins](https://rustsc.com/support/guides/plugins/index.html.md)

---

HTML version: https://rustsc.com/learn/troubleshooting/read-rust-plugin-compile-errors/
