Yup for sure a issue just tried it to see what is dose.
[DOUBLEPOST=1503669012][/DOUBLEPOST]Code:(07:25:30) | Failed to call hook 'OnEntityKill' on plugin 'Timber v0.1.9' (NullReferenceException: Object reference not set to an instance of an object) (07:25:30) | at Oxide.Plugins.Timber.OnEntityKill (.BaseNetworkable entity) [0x00000] in <filename unknown>:0 at Oxide.Plugins.Timber.DirectCallHook (System.String name, System.Object& ret, System.Object[] args) [0x00000] in <filename unknown>:0 at Oxide.Plugins.CSharpPlugin.InvokeMethod (HookMethod method, System.Object[] args) [0x00000] in <filename unknown>:0 at Oxide.Core.Plugins.CSPlugin.OnCallHook (System.String name, System.Object[] args) [0x00000] in <filename unknown>:0 at Oxide.Core.Plugins.Plugin.CallHook (System.String hook, System.Object[] args) [0x00000] in <filename unknown>:0 (07:25:32) | Unloaded plugin Timber v0.1.9 by Mattparks
I am not the Dev but I have not noticed and FPS differences on any of my servers at all with this mod. I am running this on quad core's and 8 GB ram no FPS differences at all.
Just wanted to toss that out the other stuff he would have to answer

Timber [Obsolete]
Makes trees and cacti fall before being destroyed.
Total Downloads: 2,223 - First Release: Jul 21, 2017 - Last Update: Aug 28, 2017
- 5/5, 29 likes
-
spam console
Attached Files:
-
-
https://pp.userapi.com/c840627/v840627727/a3a/WZzwhGcWUmI.jpg
after the latest update, correct -
For all of the 'OnEntityKill' issues:
Your config file needs to be changed to look like the one on the overview page, the values associated to the keys do not need change but the layout changed. Read the update notes if you have issues after a update. -
-
-
... after TIMBER - Update again BUG:
Failed to call hook 'OnEntityKill' on plugin 'Timber v0.1.10' (NullReferenceException: Object reference not set to an instance of an object)
2 Versions older are working ... AGAIN: Never touch a running System !!! Why an Update with no new Features and BugFixes, when older Version works well ? -
-
After deleting config files and updating the timber log it doesn't seem to have any major issues. Although im still suspecting a small amount of lag that it produces from time to time. I know you've specifically said there would be zero impact with server performance. But it just doesn't feel that way completely?
-
This is my config. Any reason why it should be causing the lag? There wasn't anyone complaining about lag issues since the start of the server. 2 Months later I added this plugin in and players are starting to seeing latency. Any reason why this is happening? Any possibilities that the lag issue would have relations with this plugin at this time?
Code:{ "options": { "harvestStanding": 1.0, "harvestFallen": 1.5, "hitsStanding": 15, "hitsFallen": 3, "despawnLength": 3.0, "screamPercent": 0.0, "includeCacti": true, "logToPlayer": true } }
-
Became only after restart.
I deleted lang files/config file before update Timber. -
So the developer apparently have selective hearing or unable to disclose this information about the lag issue? No means to be offensive. Lag is the major issue and as beautiful as this plugin is, if it generates that much of a latency and uses excessive RAM "somehow" it's going to be a problem for all the players on the servers who have this plugin installed. I understand you're not getting paid for making this plugin and I have no power to tell you to do anything, but why half ass it. I can see a clear latency after this plugin was installed in somewhat where it's causing an average of 30 player server on a vanilla server. I've introduced this to 3 other server owners and they've all claim the plugin lags and causes server performance issue and they've stopped using it right after. Sames goes for me, but I enjoy the plugin and trying to see if the developer is still in interest to work on this plugin.
-
-
-
It changes gather manager rates.
-
-
-
-
-
Very appreciative with the professional reply. Will get others to test this out as well and come back with a more in depth of the possibilities if it happens again. Instead of just claiming "Lag" with no help to the developer on what might be lagging the server.