1. Community
  2. Plugin Support
  3. My CH47
Console spam
Plugin Page
Posted 2 years ago
#1

How do I stop all this console spam?

 

Failed to call hook 'OnEntityKill' on plugin 'MyCH47 v1.0.1' (NullReferenceException: Object reference not set to an instance of an object)
  at Oxide.Plugins.MyCH47.OnEntityKill (BaseNetworkable entity) [0x0000a] in <37a5b4d3ce23402baf5a83685b192>:0

  at Oxide.Plugins.MyCH47.DirectCallHook (System.String name, System.Object& ret, System.Object[] args) [0x00174] in <37a5b4d3ce23402baf5a83d685b2c192>:0

  at Oxide.Plugins.CSharpPlugin.InvokeMethod (Oxide.Core.Plugins.HookMethod method, System.Object[] args) [0x00079] in <cd9a02fd33134782d550bb1a9c8e9f>:0

  at Oxide.Core.Plugins.CSPlugin.OnCallHook (System.String name, System.Object[] args) [0x000d8] in <b76ec77c47d1449e92b2baab860384>:0

  at Oxide.Core.Plugins.Plugin.CallHook (System.String hook, System.Object[] args) [0x00060] in <b76ec77c47d1449e92b2baab860384>:0
Posted 2 years ago
#2
the problem has not been solved =/

o.reload MyCH47
13:25:32
[CSharp] Started Oxide.Compiler v*.*.*.* successfully
13:25:36
MyCH47 was compiled successfully in 1713ms
13:25:36
Unloaded plugin My CH47 v1.0.2 by FastBurst
13:25:36
Loaded plugin My CH47 v1.0.2 by FastBurst
13:25:42
Failed to call hook 'OnEntityKill' on plugin 'MyCH47 v1.0.2' (NullReferenceException: Object reference not set to an instance of an object) at Oxide.Plugins.MyCH47.OnEntityKill (BaseNetworkable entity) [0x0000a] in <04311cdd665a4694a7effff67b0ca9a9>:0
at Oxide.Plugins.MyCH47.DirectCallHook (System.String name, System.Object& ret, System.Object[] args) [0x00174] in <04311cdd665a4694a7effff67b0ca9a9>:0
at Oxide.Plugins.CSharpPlugin.InvokeMethod (Oxide.Core.Plugins.HookMethod method, System.Object[] args) [0x00079] in <87ce9ac9776a48658bc55eae6debe38b>:0
at Oxide.Core.Plugins.CSPlugin.OnCallHook (System.String name, System.Object[] args) [0x000d8] in <b6d06fce9e044af4a6ddc8d724bd3b0b>:0
at Oxide.Core.Plugins.Plugin.CallHook (System.String hook, System.Object[] args) [0x00060] in <b6d06fce9e044af4a6ddc8d724bd3b0b>:0
Posted 2 years ago
#3

Has anyone found a fix for this?