Add a response to the player that they need a hammer in hand if they do not have one.

Remove is deactivated when swapped to another item/hammer is put away.

If I have this set

    "No Held Item Mode": false,
    "No Held Item Mode - Disable remover tool when you have any item in hand": false,

and

    "Hammer Hit Mode": true,
    "Specific Tool Mode": true,
    "Specific Tool Mode - Item shortname": "hammer",

it won't let you remove anything without a hammer in hand. But it doesn't tell you why it isn't working.

Oh. Sorry. I would like a chat response to the player letting them know that they need to be holding a hammer with these settings after runing the /remove command. "ItemNotHeld": "You need to be holding a {0} in order to use the remover tool.",

And if possible disable the tool when switched to another held item, or the hammer is put away "ToolDisabled": "Remover Tool has been disabled.",

I have no idea how to add that to the lang file. I assume it would need to be added to the plugin/cs since ItemNotHeld is not already part of the code.

Everything looks to be in order as far as the config and lang file. But the chat response to the player when not holding the hammer isn't responding. And the the remove tool isn't disabling when not holding the hammer.

This is what I have set right now. I'm not sure if I'm missing something somewhere else. I most likely am. I haven't used this plugin in a long while.

    "Hammer Hit Mode": true,
    "Hammer Hit Mode - Requires a hammer in your hand when remover tool is enabled": true,
    "Hammer Hit Mode - Disable remover tool when you are not holding a hammer": true,
    "Specific Tool Mode": true,
    "Specific Tool Mode - Item shortname": "hammer",

"Specific Tool Mode": true, ////Set it to false....

"Remove Mode Settings (Only one model works)"
So what mode do you want to use?

I didn't realize that was a conflict.

I thought that it was part of the same settings but it meant you had to use a specific type of tool.

Very redundant, unnecessary and wrong now that I read it again.

Sorry about that.

It works perfectly now that it's set up properly.