Template talk:Smelting

Can someone add a bit that shows the amount of experience obtained from smelting an item? - MinecraftPhotos4U (talk) 21:28, 26 November 2015 (UTC)

That could be useful. I'll see if I can make a mockup. —Fenhl 21:33, 26 November 2015 (UTC)

Gonna bump this, adding a section for experience would be really nice. -PancakeIdentity (talk) 02:13, 12 October 2019 (UTC)

Here is the preview:

{{#invoke: smelting/editcopy | table | Wet Sponge | Sponge | 1509}}

I added exp argument. Lê Duy Quang (Make some words | Contributions) at 15h12:49 – 2 | 17/2/2020 (UTC)

A second output slot for secondary outputs (namely buckets from lava buckets) might be useful, in line with my proposal for the Crafting template. Also, my request in the section above still stands, with my proposal to deprecate drops and experience sections in infoboxes as stated in the community portal. - User-12316399 (talk) 09:29, 8 October 2019 (UTC)

Smelting already lets players know the outcome of the buckets, there is no need to add an additional slot. Lê Duy Quang (Make some words | Contributions) at 14h12:43 – 2 | 17/2/2020 (UTC)

This isn't present on the pages of the item being smelted. - User-12316399 (talk) 14:17, 17 February 2020 (UTC)

Currently, crafting, trading, achievements, and advancements are all automated. For crafting, {{crafting usage}} is able to automatically load all crafting uses of a particular item in game generated from {{crafting}}. {{Load advancements}} loads advancements specified in Advancement using {{Advancements}}.

Yet Template:Smelting and Template:Stonecutting are not automatic. This makes split pages a burden for editors as there are multiple entries of the same recipe to maintain and update when pages are split and recipes are duplicated. Editors use "editor maintainance" to oppose split pages.

Template:Smelting and Template:Stonecutting should be automated with SMW/DPL. Editors would then only need to specify the smelting and stonecutting recipe in the obtaining section of a particular article. Then the recipes can automatically be loaded using {{Smelting usage}} and {{Stonecutting usage}}.

For example, an editor can add the stonecutting recipe for cobblestone walls in Cobblestone Wall#Obtaining using {{stonecutting}}, then for the block of cobblestone, use {{Stonecutting usage}} inside Cobblestone#Usage to load all stonecutter recipes of the block of cobblestone.

The same goes for smelting. Use {{smelting}} within Block of Glass#Obtaining and manually add the smelting recipes for the glass block. Then at Sand#Usage and Red Sand#Usage use {{Smelting usage}} to load the smelting recipes on those pages.

For smelting, I would suggest that recipes are only loaded when the fuel argument is left unspecified. If |fuel= is specified, it would also disable the automated recipe loading in addition to the |ignoreusage=1 used by {{crafting}}.

If these templates can be automated by someone who knows how to work with SMW/DPL, it would be greatly appreciated, and it would give wiki editors more flexibility with merged and split articles. Delvin4519 (talk) 23:58, 9 July 2024 (UTC)

Basically just changing once thing and it changes all of the recipes? That's a 👁 Image
 Yes from me. Nerdyguy2000 ( talk | edits ) 17:46, 10 July 2024 (UTC)

It is simply porting over the functionality of {{crafting usage}} to allow its functionality to be used for smelting and stonecutting. In the proposed updated system, an editor can add or change the smelting/stonecutting recipe of how to obtain a particular block and item, and it will automatically be applied to all pages using the new {{stonecutting usage}} and {{smelting usage}} templates. No more having to update recipes over and over again on dozens of split pages. It would function essentially as {{crafting usage}} does today for crafting recipes, propagating changes automatically on all pages that reference the updated recipes. Delvin4519 (talk) 17:58, 10 July 2024 (UTC)

Sooo... yeah. Sounds like changing once thing and it automatically changes the rest without having to go from page to page, editing... editing... Nerdyguy2000 ( talk | edits ) 18:03, 10 July 2024 (UTC)

These new templates are within scope of MCW:P/RECIPE. — BabylonAS 18:08, 10 July 2024 (UTC)

Well I support this but it doesn't need a proposal. It's just a matter of when someone gets around to doing it. - Harristic / Talk 👁 Image
14:08, 18 August 2024 (UTC)