Error on Console after February 2023 updateFixed

Hi,

I have a question, after the last update of February 2023, the plugin doesn't really work anymore. I don't get any notifications. But instead I got errors on the console.

Error message raid tracker on console screen.

if image doesn't show, link to the image about the error: https://ibb.co/xHv3DvR

Kind regards,

TheLivingGamer92

Thanks for the report. Post your config to https://pastebin.com/ and I can take a look, make sure to remove your webhook url from your config before posting to pastebin.

gJB9FIt0aTK8rVt.png Clearshot

Thanks for the report. Post your config to https://pastebin.com/ and I can take a look, make sure to remove your webhook url from your config before posting to pastebin.

Hi Clearshot,

Thank you for the quick answer.  You welcome.  I'm not familar with pastebin, but I can give it a shot to try.

This is the config: https://pastebin.com/FUDvgjt0   let me know if the link doesn't work.  (I tried to find my webhook url but for some reason it ends up with null at the Discord -> WebhookURL variable. That is weird that it ends up on null because I had url on it. But I don't think that causes the errors? )

 

Kind regards,

TheLivingGamer92

I've been getting the same, no logging in game as well- here's my oxide console spam:

Failed to call hook 'OnEntityDeath' on plugin 'RaidTracker v2.0.0' (NullReferenceException: Object reference not set to an instance of an object)

at Oxide.Plugins.RaidTracker.FindWeaponConfig (System.String category, System.String shortname) [0x00157] in <469aa046f6f742138f258a90b8544869>:0

at Oxide.Plugins.RaidTracker.AddOrFindWeaponConfig (System.String category, System.String shortname) [0x000de] in <469aa046f6f742138f258a90b8544869>:0

at Oxide.Plugins.RaidTracker.OnEntityDeath (DecayEntity entity, HitInfo info) [0x0076c] in <469aa046f6f742138f258a90b8544869>:0

at Oxide.Plugins.RaidTracker.DirectCallHook (System.String name, System.Object& ret, System.Object[] args) [0x00527] in <469aa046f6f742138f258a90b8544869>: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 <d5f57e12edfe4fa0b5c5dbdd9b51eff8>:0

at Oxide.Core.Plugins.Plugin.CallHook (System.String hook, System.Object[] args) [0x00060] in <d5f57e12edfe4fa0b5c5dbdd9b51eff8>:0

Seems like there is a nasty bug with the config, I've had a couple reports of this error happening now. It's definitely related to there being null values within the config, for some reason the config is wiping itself out and saving with null values.

I've been working on an update that should fix this, you can test it out if you'd like. I'd recommend deleting the broken config file and allowing the plugin to generate a new default config.

https://raw.githubusercontent.com/clearshot-xs/RaidTracker/dev/RaidTracker.cs

gJB9FIt0aTK8rVt.png Clearshot

Seems like there is a nasty bug with the config, I've had a couple reports of this error happening now. It's definitely related to there being null values within the config, for some reason the config is wiping itself out and saving with null values.

I've been working on an update that should fix this, you can test it out if you'd like. I'd recommend deleting the broken config file and allowing the plugin to generate a new default config.

https://raw.githubusercontent.com/clearshot-xs/RaidTracker/dev/RaidTracker.cs

 

Thank you for the quick reply.

That is no problem, I can test it out. Yep I will do.

I will let you know about it.

gJB9FIt0aTK8rVt.png Clearshot

Seems like there is a nasty bug with the config, I've had a couple reports of this error happening now. It's definitely related to there being null values within the config, for some reason the config is wiping itself out and saving with null values.

I've been working on an update that should fix this, you can test it out if you'd like. I'd recommend deleting the broken config file and allowing the plugin to generate a new default config.

https://raw.githubusercontent.com/clearshot-xs/RaidTracker/dev/RaidTracker.cs


Hi Clearshot,

I have tested out the new version from the link.
So far no errors on console. Only when I try to destroy a wall for example. Nothing is logged into the oxide/data folder or oxide/data/RaidTracker folder. I also tried with the Discord webhook but nothing happend on that.
Also after that there where no errors on the console.

Kind regards,
TheLivingGamer92

Discord logging is not enabled by default, did you enable the notifyDiscord option for the trackers you would like to receive alerts for?

Locked automatically