Logs / Error guide / Rust
Rust: “Failed to call hook … on plugin …”
What the message means
A plugin reacted to an event in the game (a hook like OnPlayerConnected) and stopped with an exception. The plugin stays loaded, but exactly this function doesn't work – again every time the event occurs.
What it looks like in the log
RustDedicated 2026.11.06 (2614) Server startup complete
[Oxide] 19:12 [Error] Failed to call hook 'OnPlayerConnected' on plugin 'Welcomer v2.1.0' (NullReferenceException: Object reference not set to an instance of an object)
at Oxide.Plugins.Welcomer.OnPlayerConnected (BasePlayer player) [0x0002c] in <a1b2c3d4>:0
Excerpt from an example log, marked the way the analysis marks it.
Common causes
- NullReferenceException: the plugin accesses something that doesn't exist (yet) – a player, a configuration, data from another plugin.
- The plugin's configuration or data file is corrupted or comes from an old version.
- A plugin it depends on isn't loaded.
- After a Rust update, a game function behaves differently.
How to fix it
- Read the name of the plugin and the hook from the message – the analysis shows the plugin directly.
- Update the plugin to the latest version.
- Back up the plugin's configuration (oxide/config/<name>.json), delete it and reload the plugin so a fresh file is created.
- Check whether all plugins the plugin requires are loaded.
- If the error stays, send the author the link to your log.