Not working after latest oxide update today ...

Deathmessage appears to have stopped working after today's update... this is what I get in console now as I attempt to reload it.

DeathMessage was compiled successfully in 6227ms
Unloaded plugin DeathMessage v1.0.9 by Damo/beee
Fallback handler could not load library /home/rust/server/RustDedicated_Data/MonoBleedingEdge/x86_64/data-0x55889cbb7bc0.so
Failed to call hook 'OnServerInitialized' on plugin 'DeathMessage v1.0.9' (NullReferenceException: Object reference not set to an instance of an object)
  at Oxide.Plugins.DeathMessage.OnServerInitialized () [0x00006] in <772a45334f3140439f864003c4300234>:0 
  at Oxide.Plugins.DeathMessage.DirectCallHook (System.String name, System.Object& ret, System.Object[] args) [0x002ab] in <772a45334f3140439f864003c4300234>:0 
  at Oxide.Plugins.CSharpPlugin.InvokeMethod (Oxide.Core.Plugins.HookMethod method, System.Object[] args) [0x00079] in <753b27d02c104b8d8166056be06d5c55>:0 
  at Oxide.Core.Plugins.CSPlugin.OnCallHook (System.String name, System.Object[] args) [0x000d8] in <1a298a556ab640a3a0e3fbde04ac5b5c>:0 
  at Oxide.Core.Plugins.Plugin.CallHook (System.String hook, System.Object[] args) [0x00060] in <1a298a556ab640a3a0e3fbde04ac5b5c>:0 
Loaded plugin DeathMessage v1.0.9 by Damo/beee

Same here. But seems like an Oxide update issue with newest Rust version.

06/09 11:26:58 | Failed to call hook 'OnPlayerConnected' on plugin 'DeathMessage v1.0.9' (NullReferenceException: Object reference not set to an instance of an object)
at Oxide.Plugins.DeathMessage.OnPlayerConnected (BasePlayer player) [0x00000] in <9430adc8ebb345448be5ac0dd9526b0b>:0
at Oxide.Plugins.DeathMessage.DirectCallHook (System.String name, System.Object& ret, System.Object[] args) [0x00392] in <9430adc8ebb345448be5ac0dd9526b0b>:0
at Oxide.Plugins.CSharpPlugin.InvokeMethod (Oxide.Core.Plugins.HookMethod method, System.Object[] args) [0x00079] in <753b27d02c104b8d8166056be06d5c55>:0
at Oxide.Core.Plugins.CSPlugin.OnCallHook (System.String name, System.Object[] args) [0x000d8] in <1a298a556ab640a3a0e3fbde04ac5b5c>:0
at Oxide.Core.Plugins.Plugin.CallHook (System.String hook, System.Object[] args) [0x00060] in <1a298a556ab640a3a0e3fbde04ac5b5c>:0

Hello I don't have this error
I'm using the latest version of Oxide

"DeathMessage" (1.0.9) by Damo/beee (0.58s) - DeathMessage.cs

According to others, Death Notes the free version similar to this is also apparently broken, something to do with the latest update from oxide.

I'll re-apply the plugin and see if this resolves, and report back.

I unloaded Death Message from 2 different servers, both servers run different plugins ... I even tested it on a TEST server with 0 plugins to confirm it just wasn't conflicting with something... still has issues.

Fallback handler could not load library /home/rust/server/RustDedicated_Data/MonoBleedingEdge/x86_64/data-0x55889e82fd10.so
Failed to call hook 'OnServerInitialized' on plugin 'DeathMessage v1.0.9' (NullReferenceException: Object reference not set to an instance of an object)
  at Oxide.Plugins.DeathMessage.OnServerInitialized () [0x00006] in <7a56aaa7ea1542e6911088e56d6849e9>:0 
  at Oxide.Plugins.DeathMessage.DirectCallHook (System.String name, System.Object& ret, System.Object[] args) [0x002ab] in <7a56aaa7ea1542e6911088e56d6849e9>:0 
  at Oxide.Plugins.CSharpPlugin.InvokeMethod (Oxide.Core.Plugins.HookMethod method, System.Object[] args) [0x00079] in <753b27d02c104b8d8166056be06d5c55>:0 
  at Oxide.Core.Plugins.CSPlugin.OnCallHook (System.String name, System.Object[] args) [0x000d8] in <1a298a556ab640a3a0e3fbde04ac5b5c>:0 
  at Oxide.Core.Plugins.Plugin.CallHook (System.String hook, System.Object[] args) [0x00060] in <1a298a556ab640a3a0e3fbde04ac5b5c>:0 
Loaded plugin DeathMessage v1.0.9 by Damo/beee
Unloaded plugin DeathMessage v1.0.9 by Damo/beee
Failed to call hook 'OnServerInitialized' on plugin 'DeathMessage v1.0.9' (NullReferenceException: Object reference not set to an instance of an object)
  at Oxide.Plugins.DeathMessage.OnServerInitialized () [0x00006] in <7a56aaa7ea1542e6911088e56d6849e9>:0 
  at Oxide.Plugins.DeathMessage.DirectCallHook (System.String name, System.Object& ret, System.Object[] args) [0x002ab] in <7a56aaa7ea1542e6911088e56d6849e9>:0 
  at Oxide.Plugins.CSharpPlugin.InvokeMethod (Oxide.Core.Plugins.HookMethod method, System.Object[] args) [0x00079] in <753b27d02c104b8d8166056be06d5c55>:0 
  at Oxide.Core.Plugins.CSPlugin.OnCallHook (System.String name, System.Object[] args) [0x000d8] in <1a298a556ab640a3a0e3fbde04ac5b5c>:0 
  at Oxide.Core.Plugins.Plugin.CallHook (System.String hook, System.Object[] args) [0x00060] in <1a298a556ab640a3a0e3fbde04ac5b5c>:0 
Loaded plugin DeathMessage v1.0.9 by Damo/beee

Hello please run command oxide.version
to your server or Rust Admin and see if you have the latest version
2.0.6002

I ran oxide.version and this is my readout, this looks correct and should be the most up to date version.

Oxide.Rust Version: 2.0.6002

Are you testing on Windows, or Linux ... I have found in the past sometimes plugins work on Windows, but not Linux or vice verse. The two oxide updates may be the same version, but they are separate instances based on OS of server.

My servers are Linux based.

I am testing on Windows
I've now asked some developers and they said the same thing with Windows and Linux
But they also said to wait for tomorrow's update to see if it works

UPDATE: So it would appear whatever happened with yesterdays 2 oxide updates... my config Json file was somehow corrupted and was causing the issue..

Even though I unloaded, removed all DeathMessage files ... when I uploaded again I copied my backup config file with my pre-set selections. When I just did the plugin itself, and manually changed my settings back in config... all is working fine again. So if you see others having same issue, they just have to delete there config json and let oxide re-compile a new one and re-set all config selections again. You can close ticket, thanks for help.

UPDATE: So it would appear whatever happened with yesterdays 2 oxide updates... my config Json file was somehow corrupted and was causing the issue..

Even though I unloaded, removed all DeathMessage files ... when I uploaded again I copied my backup config file with my pre-set selections. When I just did the plugin itself, and manually changed my settings back in config... all is working fine again. So if you see others having same issue, they just have to delete there config json and let oxide re-compile a new one and re-set all config selections again. You can close ticket, thanks for help.

I tested the plugin on the Staging Brach server
And there they worked

Changed Status from Pending to Closed