Jump to content

CanBradleyApcTarget

Not a Bug 1.2.3

ShiiZo
ShiiZo

Posted

Hi,

i always get this error in the console:

Failed to call hook 'CanBradleyApcTarget' on plugin 'MonumentOwner v1.7.3' (NullReferenceException: Object reference not set to an instance of an object.)
at Oxide.Plugins.MonumentOwner+<>c__DisplayClass177_0.<CanBradleyApcTarget>b__0 (Oxide.Plugins.MonumentOwner+Controller x) [0x00006] in <b7567ed27bb4492e8c65f3e43903e8ae>:0
at Oxide.Plugins.MonumentOwnerExtensionMethods.ExtensionMethods.FirstOrDefault[TSource] (System.Collections.Generic.IEnumerable`1[T] source, System.Func`2[T,TResult] predicate) [0x00010] in <b7567ed27bb4492e8c65f3e43903e8ae>:0
at Oxide.Plugins.MonumentOwner.CanBradleyApcTarget (BradleyAPC bradley, BasePlayer player) [0x0002b] in <b7567ed27bb4492e8c65f3e43903e8ae>:0
at Oxide.Plugins.MonumentOwner.DirectCallHook (System.String name, System.Object& ret, System.Object[] args) [0x01112] in <b7567ed27bb4492e8c65f3e43903e8ae>:0
at Oxide.Plugins.CSharpPlugin.InvokeMethod (Oxide.Core.Plugins.HookMethod method, System.Object[] args) [0x00079] in <42f9bedc659b4f4786eb778d3cd58968>:0
at Oxide.Core.Plugins.CSPlugin.OnCallHook (System.String name, System.Object[] args) [0x000de] in <d59b507fd76240e5b62228d0eae39b73>:0
at Oxide.Core.Plugins.Plugin.CallHook (System.String hook, System.Object[] args) [0x00060] in <d59b507fd76240e5b62228d0eae39b73>:0


Is there anything to fix this?

ZEODE

Posted

Changed Status from Pending to Not a Bug

ZEODE

Posted

Hi, as you can see in the debug log, this error is not related to my plugin. It is to do with MonumentOwner plugin.

ShiiZo

Posted

Ah ok thanks, was blind.
I will check MO then.

Thanks for the fast response.

 

  • Like 1
1.9m

Downloads

Total number of downloads.

8.7k

Customers

Total customers served.

129.8k

Files Sold

Total number of files sold.

2.7m

Payments Processed

Total payments processed.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.