at Oxide.Plugins.ExcavatorLock.OnServerInitialized () [0x001c7] in <666aae7e0f854bf9bc31a5b91f3586e3>:0

at Oxide.Plugins.ExcavatorLock.DirectCallHook (System.String name, System.Object& ret, System.Object[] args) [0x00335] in <666aae7e0f854bf9bc31a5b91f3586e3>:0

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

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

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

i managed to fix it . had to remove the data files and reload the plugin

I am unable to duplicate the issue on my system.
Are you using other plugun that interact with excavator ?

Verify the server and oxide are using the latest version.
unload the plugin and remove the config/ExcavatorLock.json and data/ExcavatorLock.json. plugin will generate default an next plugin restart

Merged post

thanks for the feedback.
I was searching umod and a number of cases were related to config or data file issue.
but still curious of the conditions that lead to this issue.

im not using any other plugins that interact whith the excavator , and everything was up to date. it happend after a server restart . when i looked in the data folder it had 1 line saying null . so i removed the data file and reloaded and it seemed to fix the problem