Tool raiding not being logged despite global tracking being enabledSolved

Hi, I upgraded to v2, and am testing it now. I enabled global tracking in the "_global" section but I can not get it to log breaking stuff with tools like a hatchet, a rock, a paddle, etc. It only logs when using actual weapons and boom like a hunting bow, M249 and C4.

Could it be maybe because of "Note: When the global wildcard item * is enabled individual items that are enabled take priority over global settings."?
I see that for example the "rock" item has "enabled" set to true but all 3 notification options are set to false.

Merged post

Ok, it seems that this is exactly what it is, I enabled that specific item's notifications and it works now.

This however presents a new problem: it means I will have to enable all of these settings manually for all the tools that exist in the game.
Would it be possible to add a global way for this? Or change how the current global tracking settings work to make this work?



Merged post

For now I have worked around the issue by changing all of the items that had this by default:
"enabled": true
to this:
"enabled": false

and this has fixed the issue for now, everything is now getting logged as expected, using any tool/item. Loving the new rewrite/update so far!

When I first designed the plugin I didn't add support for global configs and I built out a default config for the items I thought would be best to log. After adding the global config option I originally had it take priority over everything if it was enabled, which seems like the functionality you were expecting. Unfortunately when I was using it I ran into an issue where I wanted to have the global config enabled, but disable certain item notifications so I decided to allow the invidual items to take priority over the global settings. This allows you to specify custom notification options for specific items without global overriding it.

So, what you did here is exactly the way I intended the global config to be used. It might be abit confusing since the default config has a bunch of items enabled when you first install the plugin, but if you decide to go the global config route, just disable everything like you did and the global config will work as expected.

I see, that makes a lot of sense now why its the way it is, thank you.

Locked automatically