Smelt Touch

SmeltTouch

Mined blocks are smelted automatically, so the items can be picked up in their processed state, as
if they had come fresh out of a furnace.

Break an iron ore and you get an iron ingot. Break sand and you get glass. Everything the server’s
furnace recipes know about works, including recipes added by datapacks or other plugins.

Configuration

SmeltTouch writes three files – config.json, enchantment.json and messages.json – to
plugins/SmeltTouch/ (Paper) or config/smelttouch/ (Fabric, NeoForge) on first start. Missing
options are filled in with their defaults on every load, and a broken file is moved to
<name>.json.broken instead of stopping the server.

See CONFIGURATION.md for what every field in the three files does, the id list
syntax used by filters, and example configs.

Command

/smelttouch

| Sub command | Description | Permission |
|—————————–|——————————————–|————|
| status [player] | show whether the effect is active | smelttouch.admin for other players |
| toggle [player] | switch the effect on/off for yourself | smelttouch.admin for other players |
| on / off [player] | set the state explicitly | smelttouch.admin for other players |
| reload | re-read the config and the recipe index | smelttouch.admin |

Permissions

| Node | Default | Meaning |
|——————–|———|———|
| smelttouch.use | everyone | required for the effect (configurable through general.permission) |
| smelttouch.admin | operators | reload, and toggling other players |

On Paper the node is declared with default: true, so it works out of the box and can be revoked
through any permission plugin. Fabric and NeoForge use the vanilla permission atoms
(smelttouch:use); because vanilla has no “granted by default” concept, an ungranted node only
denies when general.strictPermissions is turned on.