Failed to call Hook "OnCollectiblePickup"

Hey, we got an Error, please look on it.

 

Failed to call hook 'OnCollectiblePickup' on plugin 'LootAudit v1.2.5' (NullReferenceException: Object reference not set to an instance of an object)
  at Oxide.Plugins.LootAudit.OnCollectiblePickup (CollectibleEntity collectible, BasePlayer player) [0x00000] in <15c8b72f98b743cea25602ca9e4fb28a>:0 
  at Oxide.Plugins.LootAudit.DirectCallHook (System.String name, System.Object& ret, System.Object[] args) [0x002b1] in <15c8b72f98b743cea25602ca9e4fb28a>:0 
  at Oxide.Plugins.CSharpPlugin.InvokeMethod (Oxide.Core.Plugins.HookMethod method, System.Object[] args) [0x00079] in <09575a60985045248bcb43b20faeeb99>:0 
  at Oxide.Core.Plugins.CSPlugin.OnCallHook (System.String name, System.Object[] args) [0x000d8] in <bae5f1223fce49c493b01571c99dce02>:0 
  at Oxide.Core.Plugins.Plugin.CallHook (System.String hook, System.Object[] args) [0x00060] in <bae5f1223fce49c493b01571c99dce02>:0  

Can you provide any other info?
What they were picking up?
Will look into it.

Changed Status from Pending to Can't Reproduce

Hey, sorry, i had not the time yet, to come back to you, i will test, how this issue would be reproduced

Hey, i had tried to reproduce the problem, the error was get after farming berries

I will come back to you with an error video

Changed Status from Can't Reproduce to Closed

Changed Fixed In to 1.3.0

Yea I'm also getting this error message. This is on start up with no players having connected yet. (Private listed, closed ports, local test server)

will look into it some more thanks

@BippyMiester
Can you enable debug in the config and send me the output when the error comes up?

@Gt403cyl2

I enabled the debug in the config, and nothing else popped up relating to LootAudit other then the error message.

(10:23:10) | Failed to call hook 'OnCollectiblePickup' on plugin 'LootAudit v1.3.3' (NullReferenceException: Object reference not set to an instance of an object)
  at Oxide.Plugins.LootAudit.OnCollectiblePickup (CollectibleEntity collectible, BasePlayer player) [0x00000] in <76b3e50c7a37411fb4e547d32b513636>:0 
  at Oxide.Plugins.LootAudit.DirectCallHook (System.String name, System.Object& ret, System.Object[] args) [0x002b1] in <76b3e50c7a37411fb4e547d32b513636>:0 
  at Oxide.Plugins.CSharpPlugin.InvokeMethod (Oxide.Core.Plugins.HookMethod method, System.Object[] args) [0x00079] in <09575a60985045248bcb43b20faeeb99>:0 
  at Oxide.Core.Plugins.CSPlugin.OnCallHook (System.String name, System.Object[] args) [0x000d8] in <bae5f1223fce49c493b01571c99dce02>:0 
  at Oxide.Core.Plugins.Plugin.CallHook (System.String hook, System.Object[] args) [0x00060] in <bae5f1223fce49c493b01571c99dce02>:0

Here is my entire log file.

logfile.txt

Looking at your logs, you have a bit of broken stuff...

HomesGUI v1.4.22 - corrupt data file
GodmodeIndicator v2.1.2 - OnGodmodeToggled failed.

Failed to check connectivity to the companion server:
Companion server failed to start: System.Net.Sockets.SocketException (0x80004005):

If you have no population when this happens it has to be a conflicting plugin because There are checks to only call the hook if a player collects the item.
The other possibility is it's a horse eating a wild berry (which I am working on). but likely hood of a horse spawning regularly on berries....

HomesGUI has been throwing that error for a long time. The data file isn't corrupted. The homes are still being listed on everyone elses end and the plugin is not broken at all.

Godmode Indicator failed due to the fact that I logged out when admin toggle was enabled. That happens, its normal, and it doesn't break anything.

Companion server connectivity is due to the app.port being set but not forwarded. Its something I've been meaning to fix, but again that doesn't break anything plugin wise.

Totally agree on the horse thing. Chance of that happening is slim to none. I'll run a test server with only your plugin enabled. See what happens. I'll have to deal with that in the next few days though. Been super busy with work this week.

Changed Fixed In from 1.3.0 to 1.3.4

What was it? Were you able to finally replicate it?

Fixed the horse issue.
Yes as soon as I loaded loot audit in my test server before I joined) the error came up and narrowed down it was a horse eating...

There is a small chance there is something else but I think I have accounted for most things now.

Feel free to post any other issues.
 

Yea for sure. Just was curious... Kind of weird tho that it was a horse. I mean even you said the odds of that happening are so slim. I wonder if the odds were greater then expected?

Time will tell, I didn't expect it either but yeah.