Hey - Not sure if this is one of the hooks broken through oxide or if it's another issue. Thought I'd ask. :D  

 Failed to call hook 'OnBradleyApcInitialize' on plugin 'BradleyControl v0.2.2' (NullReferenceException: Object reference not set to an instance of an object)
  at Oxide.Plugins.BradleyControl.OnBradleyApcInitialize (BradleyAPC bradley) [0x00092] in <99d338315d534c32882005c7503be256>:0 
  at Oxide.Plugins.BradleyControl.DirectCallHook (System.String name, System.Object& ret, System.Object[] args) [0x00349] in <99d338315d534c32882005c7503be256>:0 
  at Oxide.Plugins.CSharpPlugin.InvokeMethod (Oxide.Core.Plugins.HookMethod method, System.Object[] args) [0x00079] in <9affce1cd15c4ec183941adef8db1722>:0 
  at Oxide.Core.Plugins.CSPlugin.OnCallHook (System.String name, System.Object[] args) [0x000d8] in <4452f821def6406d834e4149849fe7ea>:0 
  at Oxide.Core.Plugins.Plugin.CallHook (System.String hook, System.Object[] args) [0x00060] in <4452f821def6406d834e4149849fe7ea>:0

Wulf

It's an error in the plugin, something is null and not handled.

The actual CS, not the config?

Irishsun530

The actual CS, not the config?

Failed to call hook 'OnBradleyApcInitialize' on plugin 'BradleyControl v0.2.2' (NullReferenceException: Object reference not set to an instance of an object)
  at Oxide.Plugins.BradleyControl.OnBradleyApcInitialize (BradleyAPC bradley) [0x00092] in <ccf6b9c0aef344a3ae6910d27457691f>:0
  at Oxide.Plugins.BradleyControl.DirectCallHook (System.String name, System.Object& ret, System.Object[] args) [0x00349] in <ccf6b9c0aef344a3ae6910d27457691f>:0
  at Oxide.Plugins.CSharpPlugin.InvokeMethod (Oxide.Core.Plugins.HookMethod method, System.Object[] args) [0x00079] in <efb9a8684e344ecfa065c7b416e6d2fd>:0
  at Oxide.Core.Plugins.CSPlugin.OnCallHook (System.String name, System.Object[] args) [0x000d8] in <b0a93b504f034a0db8b1c3d2503c0987>:0
  at Oxide.Core.Plugins.Plugin.CallHook (System.String hook, System.Object[] args) [0x00060] in <b0a93b504f034a0db8b1c3d​

scaryjames01

Wolf, I created a new thread, because this plugin was working for me until that last update, so I created a new thread as the yellow bar at the bottom says to do, since this thread is "stale".  I'm hoping that a new thread may generate some new interest and someone may fix the issue.

The error still exists and is relevant, which is why it was merged. There's no reason to have a new thread for the same issue.

My thinking was that since it was working 2 weeks ago, that post had been forgotton or ignored, since it was from 4 months ago.. I only started getting this error after that last 2 Rust updates.  I never saw it before that.  Perhaps that issue was checked on, and they didn't see the issue either, and are maybe ignoring this thread?   It's just a thought..

Thanks

scaryjames01

My thinking was that since it was working 2 weeks ago, that post had been forgotton or ignored, since it was from 4 months ago.. I only started getting this error after that last 2 Rust updates.  I never saw it before that.  Perhaps that issue was checked on, and they didn't see the issue either, and are maybe ignoring this thread?   It's just a thought..

Thanks

The plugin hasn't had a maintainer in nearly 4 years, so the issue that has only been posted for 4 months is unlikely to have resolved itself. ;)