Template talk:Block/Archive 1

something
I need help. how do I make it so, if no tool is specified, there is nothing that appears there? when editing a block and not adding a tool, it goes crazy and adds the full-size image of the block used above it as it's tool.-- 10:43, 31 August 2010 (PDT)

Um, the last edit completely broke the tool section of the template.....-- 08:44, 4 September 2010 (CDT)
 * nvm. working now.-- 08:45, 4 September 2010 (CDT)

The tooltip for the various pickaxes always just says "Pickaxe" regardless of the type of pickaxe displayed. It'd be better if the tooltip said "Wooden Pickaxe" if the Wooden Pickaxe was displayed, "Stone Pickaxe" for the Stone Pickaxe, etc. This is easy to fix in the template but I don't have access to edit it. -- 02:31, 13 November 2011 (UTC)

requirements
just gonna tell you a few more requirements, if you can add them in :3 "direct sunlight" (flowers) "next to water" (papyrus) "near water" (seed/crops) so, if you can add them, please do! =3 if not, nevermind ^^-- 14:28, 5 September 2010 (CDT)

Add: Destroy Information
I've had a lot of people asking lately how to destroy things, and, when destroyed, whether you get the block back or not.

A good example of this is Pressure Plates and Stepping Stones. If destroyed by anything other than a pickaxe, you get nothing back...


 * Break the blocks under pressure plates to get them back.


 * I think the tool slot in the block template generally fulfills that need. 06:09, 29 May 2012 (UTC)

Two images?
Can we update this block so that it can show two images? I'm thinking for the step/double step, furnace/burning furnace pages.. could also be used for Redstone ore/glowing redstone ore, redstone torch on/off, redstone wire on/off and so on. There's already the facility to show two data values (as on the furnace page), would make sense to be able to have two images. 10:36, 8 October 2010 (UTC)
 * Done! I also added a 36px image that I intend to be used as an image for when the block in in your inventory. The parameters are  and , respectively.  21:22, 11 October 2010 (UTC)
 * Also added a section for stackability of the item, parameter is .  21:30, 11 October 2010 (UTC)
 * Cool :-) Updated the Step page to use the new template. 22:27, 11 October 2010 (UTC)

New tool choices and text
Just to let everyone know, now when putting in a parameter for, the image (if there is one) will also be a link to the respective part of the  page, and will also give the name of the tool when you hover over the image. Also, I added a new option for, which is  , so if you put in  , the template will say All tools. It's for objects that don't get bonuses from any tool, like leaves and cloth. 02:18, 13 October 2010 (UTC)

Burn Time
Many things can be used as fuel in a furnace, and I think that an objects burn time should be represented in the template infobox. If this can be done,yay; if not, so be it. Thanks for your help. 15:24, 14 October 2010 (UTC)

Minimum Tool
Can we add an optional "minimum tool required" bit to the template? 'Minimum tool' meaning minimum tool required to successfully extract the block.

Tool
Currently in the source, it states that for the tool space, I could put both "All tools" and "none". From my understanding, there is no blocks that has more than one preferred tools, let alone all tools. I think the "all tools" should be removed as "none" makes more sense. -- 08:43, 23 November 2010 (UTC)

Change the icons to my set of Generics?
I think that using diamond icons is a little too specific and may make people think you need an diamond tool to break it. Also, I think these would fit alot better. I made a set of Generic tool icons, here they are

Axe

Pickaxe

Spade

Hoe

Sword
 * I like it. Go ahead. 01:43, 14 January 2011 (UTC)
 * Done transitioning the icons. 23:10, 15 January 2011 (UTC)
 * Hm. Shouldn't we resort to using the proper tools when needed, though? Like, we could have an Iron Pickaxe with a + sign next to it on the Redstone Ore page. Just saying~ 18:10, 20 January 2011 (UTC)

Could somebody add a section for miscellaneous notes?
It would be useful to have a small section in the template for notes (e.g., adding this to cake: "Heals for when used. Has 6 uses.")  01:13, 14 January 2011 (UTC)
 * Like that? 01:43, 14 January 2011 (UTC)
 * But, why? The infobox is for generic information. Notes and usage is more appropriate in the article itself. -- 03:30, 14 January 2011 (UTC)

Translation into french
Hello there, May I try to translate this infobox into french ? I don't know if i'll be able to do it but I'd like to try. I'll need to make many edit of the page as previews shouldn't work (as I need to publish the page to get the infobox to change). Thanks.-- 20:52, 30 January 2011 (UTC)
 * I would wait with templates until we actually have a French language subdomain. While I know this makes some of the other page translation difficult, the French subdomain will do everything in french. This wiki will not recognize command level words in French. --   20:57, 30 January 2011 (UTC)
 * Ok, okay, didn't know you guys wanted to wait a subdomain for french articles. This is going to be great, thanks. (Are you a sysop btw ?) -- 21:00, 30 January 2011 (UTC)
 * I'm a representative of Curse.com that works as an advisor on this wiki. --   21:04, 30 January 2011 (UTC)
 * In the meantime, you should be able to copy this template into your userspace (e.g. at ) and translate it from there. It should be enough, minimally, to just translate the labels (what actually gets displayed when the template is used), but you could translate parameter names as well; that may make use easier for French editors. 「」· 21:49, 30 January 2011 (UTC)

Adding the ability to access the data fields in other pages
Hi all. I've been striving to come up with a way to use the data that's in the block's infobox header on other pages, in order to create pretty data tables and the like. For instance, wouldn't it be nice if kept itself up-to-date when the tntres value for a block is changed? If the two places aren't linked, they'll quickly get out of sync, because not everyone will remember to update all the places where the data is duplicated.

I think I finally came up with a way to do this that doesn't put up any barriers to editing and using the block pages in a normal, natural way. See for an explanation of how it works. However, as Wynthyst, I got a bit... overeager... in making these changes, so I'm cooling it for a bit, to see what everyone else thinks. So far most of the discussion has happened on, probably best to chime in there. But I'm leaving this note here in case anyone is following this space and not the community portal.

Although nothing is broken at the moment, behind the scenes the block pages are in an inconsistent state, with a smallish fraction using the new scheme and the rest deriving the tntres value from a data table macro. That's not a good way to leave things, so I'd like to move forward in a day or two. (Note that "moving forward" in this case means "getting rid of the misguided data table thing, which I definitely should not have done without some community feedback".) 00:45, 14 March 2011 (UTC)

Flamability
Hi, hope I'm doing this in the right place - can I make a suggestion for the flamability of blocks to be added to the template please? I'm assuming that's a "yes/no" thing but I can't see anywhere that confirms that blocks made from wood (like the workbench, chests) will or won't burn when they meet lava or fire? Many thanks! -- 12:14, 18 April 2011 (UTC)


 * Can anyone give a list of flammable blocks? (and yeah, I think this would be a reasonable addition to the infobox) 「」· 03:03, 19 April 2011 (UTC)
 * Can I bump this? I think every article has a mention of a block's flammability in its main description. A general rule is: Tree-type blocks incl. logs, leaves, planks etc. are flammable; as is wool. Netherrack burns indefinitely, TNT explodes on contact... all these can be worked in similar to how the are implemented.  13:17, 25 May 2011 (UTC)
 * List of flammable blocks:
 * {| class="wikitable collapsible collapsed"

! colspan=3 | Starport592's list of flammable blocks ! Name ! Icon ! Note || || || || || || || || Burns Infinitely || Explodes || Can be set on fire near a source of fire/lava, but not destroyed by the fire. Can set other things around it on fire. || Can be set on fire near a source of fire/lava, but not destroyed by the fire. Can set other things around it on fire.
 * }


 * There may be more but that should be most of them.
 * 06:05, 29 May 2012 (UTC)


 * Condensed your list to make it a bit more readable; all the data values of a block will have the same behavior. Looking at the 1.2.5 code, there are actually several mechanisms at work. BlockFire has a list of blocks it can spread to and burn up, each with a numeric ability to spread fire and tendency to catch fire. These blocks are: bookshelf, fence, leaves, planks, wooden stairs, tall grass, TNT, vines, wood, and wool; see table below for the data. I expect wood slabs and double slabs will be added to this list in 1.3 . The calculations are somewhat complex, so the spread/catch fire numbers are weighted values, not percentages.


 * Lava source blocks (but not flowing lava), on the other hand, can set blocks on fire if they are made of a flammable material; these materials are leaves, TNT, vines, wood, and wool. This discrepancy produces a number of blocks that will ignite if placed near lava, but are not consumed and fire does not normally spread to them (though they may be able to set other blocks on fire). These blocks are: bed, crafting table, chest, note block, jukebox, signs, wooden door, wooden pressure plate, fence gate, trapdoor, and giant mushroom.


 * Finally, there's the special case of fire on top of netherrack (or bedrock in the End), which will never burn out on its own. However, fire will not spread to it (if it did, the entire Nether would turn into an inferno).


 * {| class = "wikitable collapsible collapsed"

! colspan=3 | Orthotope's list of BlockFire values ! Block !! spread fire !! catch fire
 * Bookshelf || 30 || 20
 * Fence || 5 || 20
 * Leaves || 30 || 60
 * Planks || 5 || 20
 * Wooden Stairs || 5 || 20
 * Tall Grass || 60 || 100
 * TNT || 60 || 100
 * Vines || 15 || 100
 * Wood || 5 || 5
 * Wool || 30 || 60
 * }
 * -- 08:20, 29 May 2012 (UTC)
 * TNT || 60 || 100
 * Vines || 15 || 100
 * Wood || 5 || 5
 * Wool || 30 || 60
 * }
 * -- 08:20, 29 May 2012 (UTC)
 * Wool || 30 || 60
 * }
 * -- 08:20, 29 May 2012 (UTC)
 * -- 08:20, 29 May 2012 (UTC)

I'd also like to see flammability details added to infoboxes. I'd be happy to edit the data in if someone added the field to the protected template. Orthotope, since you're an admin now, would you be interested in doing that? — 20:24, 9 February 2013 (UTC)


 * I can add it, but what terms should be used? The field should distinguish between non-combustible blocks, blocks that fire can spread to and destroy, and blocks that can be set on fire by lava, but are not otherwise flammable. -- 05:03, 10 February 2013 (UTC)


 * I was thinking it should be labeled “Flammable”, and have these different values: the text "No", a separate template which displays the catch and spread values (like we use for data values), the text "No, but catches fire from lava" for the wood-but-not-flammable blocks, and "Special, see text" in the case of Netherrack. None of this detail actually needs extra work in the Block template. — 04:44, 18 February 2013 (UTC)


 * Added. Default value is "No", since the majority of blocks are not at all flammable. -- 05:38, 19 February 2013 (UTC)


 * "Flammable: No, but catches fire from lava" is confusing/seemingly contradictory. How about "Yes (lava only)"?
 * I agree that it would be a good idea to have a consolidated list of flammable blocks. The article seems like an obvious place (there are many things that can light blocks on fire, but they all produce one thing: a fire block). I'm afraid I don't follow orthotope's explanation well enough to attempt it myself, though. How are the weights used? Do items that can only be lit by lava have "spread fire" weights, or do other blocks use their "catch fire" weight from it?
 * &mdash; &middot;  &middot; 06:36, 19 February 2013 (UTC)

Add a "first appearance" section
Almost every single article starts with "X is a block that was added in version Y". We should add a first appearance section to the block template to get rid of that. 18:33, 7 May 2011 (UTC)
 * Sounds like a good idea. I'm all for it.-- -  MCWiki Administrator  18:49, 7 May 2011 (UTC)
 * Added it, thoughts would be great. A problem I can see is a way to show the first version of blocks with more then one version that they first appeared in, like saplings. -- 22:45, 7 May 2011 (UTC)
 * You just made a change, then reverted. Thank you for that, as I started to mass do them and I noticed that the ones I were working on broke *creeper* ( 01:20, 8 May 2011 (UTC)
 * Finally added all first version's to all blocks on the block template, took about 1 1/2 hours. Should we do the same thing for items? Oh, and you really do need to readd that multiple releases... some of the things I added (wood and saplings, for example) have multiple release dates, and it looks very messy without it. ( 02:48, 8 May 2011 (UTC)
 * Multiple releases didn't work for me, but I'll try again. Need autoconfirmed user to make a template.

-- 03:37, 8 May 2011 (UTC)

Old names/Alternative names
Hey, just got an idea. Instead of putting old names and alternative names in the page, put it at the top right, where the blast resistance and other things goes... What do you think? Discuss. C ali nou - ×  » 18:22, 13 May 2011 (UTC)

Shears in Tool section
Hey, the page asks to get concenus before editing, so I wanted to ask if it is alright to add a "shears" entry in the tools section - as far as additional info, to do so all I'd need to know is the standard for images used for the section, and where to upload said image to (if there is some specific place aside from standard wiki database). Figure this should be added since leaves need it

-- 22:49, 1 July 2011
 * Done (it was easier to do it than to explain how to do it ^^"). I used the grid image for shears, as there is only one type of shears (while other tools have wooden, stone, iron, … types) –  11:52, 3 July 2011 (UTC)

How do you Make a Block Image?
How does one make the 3D block image that's on every block page? Is there a tutorial? Program? What? 19:33, 13 October 2011 (UTC)
 * Have a look at 's FAQ. -- 19:35, 13 October 2011 (UTC)

New type required for Thin blocks
There are now new solid blocks that are thin.

And I think we need new type value for it.

Blocks are:, and  ( too, but seems they are bugged now and you cannot step next to them properly)

s I think are related to that type too. {{{static link|User:0xE1|0xE1}} 20:14, 27 October 2011 (UTC)}

Blast resistance
Since Blast Resistance Values is now up-to-date (as of 1.2.3), can we remove the [edit] link next to it? -- 23:52, 12 March 2012 (UTC)


 * I suppose. – (&#124;) at 00:03, 13 March 2012 (UTC)

Explosive resistance Icons?
I think that we should make little icons next to the blast resistance of a block on it's own block page.

The reason I think this is because it would be a quick and easy way to verify the general blast resistance of the block without having to search through the wiki like I did to find out if a certain block is able to stand, say a ghast explosion.

Therefore, I say that if a block can resist an explosion from whatever would cause one, then it should get that icon next to the blast resistance.

For example: (Not in order of strength, mind you)

Just thought that this might be useful. At least I'd find it useful. Reply back whether you like the idea because I would love to see this on the wiki!

--Cheers!

04:02, 29 May 2012 (UTC)

Shovel icons
and require a shovel to mine successfully, but the template will currently only display. Could someone add this line to the tool fields? | wooden shovel  = -- 18:44, 19 July 2012 (UTC)

Adding tooltips to tool icons
What do you think about adding tooltips to tool icons (that is shown when holding the cursor over an icon)? Something like this: -- 11:41, 16 August 2012 (UTC)

Line break for inventory icons
The line of inventory images such as at is squishing the content too much. How about breaking them to a second row instead of having a huge row of images? -- 04:28, 27 September 2012 (UTC)

Add Avaliablility
Certain blocks are unobtainable in Survival / creative only or they are obtainable through /give or client mods. –Preceding unsigned comment was added by (&#124;) 21:15, 23 December 2012 (UTC). Please sign your posts with


 * Done. – ᐸ  22:33, 23 December 2012 (UTC)


 * Are there any guidelines for how this line should be used? How about:
 * Creative inventory (e.g.,, , )
 * /give command (e.g., )
 * Mods required (e.g., )
 * Though technically, would probably be "/give command (pig spawner only, otherwise mods required)".
 * &mdash; &middot;  &middot; 06:53, 19 February 2013 (UTC)

"dirt" entry
I found some pages (such as and ) use to specify their placement requirement. Currently this entry is shown only on solid blocks. Should we remove this restriction? -- 04:16, 21 January 2013 (UTC)

Flammable information default change?
If you go to the page, you will read that the block info says it's not flammable. We don't know yet. The default for Flammable should be '?', so problems like those will not happen again. -- 22:09, 7 March 2013 (UTC)


 * Fixed for now by adding a  line. If you're volunteering to update the 100+ non-flammable blocks, I could change the default, but that's a lot of busywork I don't really feel like doing. --  05:58, 8 March 2013 (UTC)

Hardened Clay
For the merging of Stained Clay into Hardened Clay, the process was fairly easy, apart from the fact that only 16 inventory and item images are supported. What is the best way around this. – ᐸ   08:39, 17 May 2013 (UTC)
 * Hardened Clay and Stained Clay are different blocks with different ids, names etc. Why the merge? -- 09:15, 17 May 2013 (UTC)
 * Although the ids and names are different, they are more or less the same thing, with the exact same properties etc. Most of the information on both pages will just simply be repeated and it is much more organised to keep them on one page. – ᐸ    09:28, 17 May 2013 (UTC)
 * They have different crafting methods, uses, names, ids, history. The only things these block have in common are blast resistance and best tool. It's like saying and  are more or less the same thing. -- 11:12, 17 May 2013 (UTC)
 * Coal and charcoal were originally separate article because of the differences that you mentioned earlier, then they were combined into one article. Even though it may be quite different technical wise, in theory its more or less the same. – ᐸ    12:35, 17 May 2013 (UTC)
 * Actually on that note, perhaps a division of the two different block types like on the Coal page would be better. – ᐸ    12:37, 17 May 2013 (UTC)

New parameter: drops
I'd like this infobox to show on a glance what a mined block drops (if not itself). The values for this parameter could look like those in Entity infoboxes. A reminder that a tool may be needed for the block to drop anything and that Silk Touch and/or Fortune may change the drops could also be useful. — 18:39, 21 August 2013 (UTC)


 * . Defaults to "Itself" since most blocks drop themselves. – ᐸ <small style=display:inline-block;line-height:9px;vertical-align:-3px> – 20:38, 22 August 2013 (UTC)

de interwiki
please add the german interwiki link -> Vorlage:Block -- ( ~ ) 15:27, 7 October 2013 (UTC)
 * And the Dutch interwiki link -> please. I still think admins on other language wikis should have permission to do this kind of edits. --   undefined NL Admin  15:30, 7 October 2013 (UTC)


 * Done. A small configuration change to the wiki would be needed to set director-level protection; currently the only options are administrators, autoconfirmed, or all users. -- undefined 16:40, 7 October 2013 (UTC)

Add Strings
There should be a section to add the block strings, because later item ID's will not be supported by command blocks, and it would be useful to know that item's string.

For example, the string for the locked chest used to be: chest_locked_aprilfo­ols_super_old_legacy_we_should­_not_even_have_this

17:41, 9 November 2013 (UTC)


 * Added a  parameter for this. -- undefined 20:08, 9 November 2013 (UTC)


 * I would expect most names will be the same as the page name, so can we not do this automatically? What are the general rules for the names? Lower case and spaces replaced with underscores? Also I'm not sure about the parameter being called name. That sounds like it's going to set the name of the infobox, which is what title does already. What do Mojang call this? <span class=nowrap>– ᐸ <small style=display:inline-block;line-height:9px;vertical-align:-3px> ⎜ 00:55, 10 November 2013 (UTC)


 * The parameter can certainly be renamed, since it isn't being used yet. There doesn't seem to be an official term for the new IDs, as far as I can tell. -- undefined 02:45, 10 November 2013 (UTC)


 * The in-game warning calls them "names" for now:  (emphasis added).
 * There are actually a lot of blocks with different id names than their tooltip names. Maybe use a bot to set the id names from a decompiled list?
 * &mdash; &middot;  &middot; 03:54, 10 November 2013 (UTC)


 * nameid maybe?
 * I don't think AWB can add text based on the page name, it probably would have to be done manually. <span class=nowrap>– ᐸ <small style=display:inline-block;line-height:9px;vertical-align:-3px> ⎜ 14:52, 10 November 2013 (UTC)


 * I've changed it to nameid. Is there a list of names anywhere? And should we add the minecraft: prefix? <span class=nowrap>– ᐸ <small style=display:inline-block;line-height:9px;vertical-align:-3px> ⎜ 02:40, 1 December 2013 (UTC)


 * All the names are at and . The prefix isn't actually needed in-game, I could go either way on it. -- undefined 04:06, 1 December 2013 (UTC)


 * I've set the nameid for all blocks that have a different one from their title or pagename, the rest are done automatically. I'll do items later. <span class=nowrap>– ᐸ <small style=display:inline-block;line-height:9px;vertical-align:-3px> ⎜ 05:40, 1 December 2013 (UTC)


 * All done. There were a few things I wasn't sure about, though. For example, all the raw/cooked sharing the same names (I assume they must still use damage values?) as well as the block and item forms of somethings (s, s and, for example). Could someone take a look at these? <span class=nowrap>– ᐸ <small style=display:inline-block;line-height:9px;vertical-align:-3px>  ⎜ 05:51, 3 December 2013 (UTC)

Block Hardness
Could a parameter for block hardness be added? It could use the same system as Blast Resistance. On some articles, blocks are mentioned as being stronger than others, and it would be nice to see the information on the infobox. I could build template if needed. -- ( 17:16, 12 June 2014 (UTC)


 * The template is finished, I basically rewrote { {tl|Hardness Values}} in the style of Blast Resistance Values, then moved it to Hardness values. Opionions on adding this to the template?
 * -- ( 22:54, 28 June 2014 (UTC)


 * Thanks for working on it; added to the template. Sorry about the delay, I hadn't wanted to add it until the hardness template was ready to go. -- undefined 23:22, 28 June 2014 (UTC)


 * Thanks for adding it. I guess I need to dynamic now... I might make a subpage template for that  to make it easier, kinda like used on.
 * -- ( 00:13, 29 June 2014 (UTC)

it interwiki
Please add the italian link: Template:Blocco -- it.Wiki Admin 09:07, 9 July 2014 (UTC)


 * Done. -- undefined 16:09, 9 July 2014 (UTC)


 * Wouldn't it be easier to put the interwiki on the doc page using ? That would allow people from other languages to easily add it. -- ( 20:22, 9 July 2014 (UTC)


 * Thanks :)
 * -- it.Wiki Admin 20:33, 9 July 2014 (UTC)

Availability parameter
So, what do we put in the place used by the availability parameter? On most every article it is used, it is left as a question mark. Do we even need it? -- ( 21:07, 10 July 2014 (UTC)


 * Kill it. It's been in the template and no one knows what to put in it or how to read it. The subject is better discussed in the Obtaining section anyway, since it can be complicated (different editions, different gamemodes, etc.). &mdash; &middot;   &middot; 02:37, 11 July 2014 (UTC)


 * It's "basically" meant for what gamemodes it can be obtained in, but editions and cheat commands complicates it. I'll set to it hidden by default. <span class=nowrap>– ᐸ <small style=display:inline-block;line-height:9px;vertical-align:-3px> ⎜ 11:11, 11 July 2014 (UTC)

a --> an
The sentence: This block can be broken with any tool, but a axe is the quickest, contains a grammatical error, it should say an axe instead of a axe --  undefined NL Admin  16:14, 14 July 2014 (UTC)


 * –   – 14:55, 11 August 2014 (UTC)


 * Majr@undefined sorry to bother, but could we get this small thing done? – , , b 17:37, 8 September 2014 (UTC)


 * Done. -- undefined 18:59, 8 September 2014 (UTC)


 * Thanks! – , , b 19:22, 8 September 2014 (UTC)

Behavior of the parameter "dirt"
I noticed the dirt parameter only shows if the block is solid. I though only non-solid blocks have any requirements like that. Is there a reason? -- ( 21:35, 10 August 2014 (UTC)


 * It seems the switch is simply backwards. It is set to only show the field when it is a solid block, rather then when it is not solid. -- ( 19:35, 20 September 2014 (UTC)


 * Do we even need this parameter? There are relatively few blocks that can only be placed on certain other blocks (sugar cane, cactus, crops, flowers), and I think this behavior would be better described in the body of an article than in the infobox. -- undefined 23:35, 20 September 2014 (UTC)


 * I don't think so, and since it has been broken since august 26, 2010, so no one will notice it's disappearance. Plus as you said it can be described better elsewhere. -- ( 00:12, 21 September 2014 (UTC)


 * Agree to remove the dirt parameter. &mdash; &middot;  &middot; 03:23, 22 September 2014 (UTC)


 * Bump <span class=nowrap>– (·) 02:48, 6 January 2015 (UTC)


 * Removed. Pages which use the dirt parameter are in for a bot to run through and remove. <span class=nowrap>– ᐸ <small style=display:inline-block;line-height:9px;vertical-align:-3px>  11:04, 6 January 2015 (UTC)


 * , all uses of the parameter were removed, so the category is empty. <span class=nowrap>– (·) 16:54, 6 January 2015 (UTC)

Set drops to "list-style-none"
Can the drops section be set to use the class of "list-style-none" so drops can use the drops template? It would be helpful on blocks with multiple drops like. -- ( 02:30, 22 August 2014 (UTC)

Long boxes
Some of the Block boxes have become rather huge, especially with multiple data values for block and items. Long block boxes limit the space for article text and can make it difficult to add tables or thumb images to articles.

With the current expansion of the Data Values section in some articles, would there be any objection to simply saying "See below" or "See " in some of these fields with a link to the appropriate subsection where there's more space and freedom to describe all the data? &mdash; &middot;  &middot; 22:21, 19 September 2014 (UTC)


 * I think anything with multiple data values (including states) should just link to the appropriate section. There's no point in duplicating the information, and it can be displayed much better in a table in its own section rather than being crammed into an infobox, however ones with just a single data value should probably remain in just the infobox. <span class=nowrap>– ᐸ <small style=display:inline-block;line-height:9px;vertical-align:-3px> ⎜ 04:15, 20 September 2014 (UTC)


 * I agree that removing the values from the infobox is a good idea, although isn't the TOC on the other side already linking to the data values section?
 * I am also unsure about a few of the other sections, such as first appearances. It only currently applies to the PC addition, and is not the first thing someone needs to know about a block or item generally. If they want to know when it was added, they can always use the history section.
 * -- ( 04:31, 20 September 2014 (UTC)


 * Well people may be confused if part of the infobox just disappears, so we should at least link to it temporarily. We may also wish to keep a simple data value and link to the section for more info. <span class=nowrap>– ᐸ <small style=display:inline-block;line-height:9px;vertical-align:-3px> ⎜ 06:08, 20 September 2014 (UTC)


 * Yeah, a transition would at least be important. As for a simple data value, on most blocks that would be fine, on a few of the hub articles though there may be too many for even that. is an extreme example.
 * Also, what about the expressing of the numbers in three formats, are hex and bin even used by anyone anymore? Or can't they simply use a converter? -- ( 18:49, 20 September 2014 (UTC)


 * I agree that First Appearance could be phased out (maybe simply hardcoding a "See History" link in the template?). For numbers, if binary and hex are still useful I'd prefer they were just tooltips on the decimal number. And I agree, when there's only one data value, we can just state it in the box (though it may be useful to repeat it in Data Values too). &mdash; &middot;  &middot; 19:27, 20 September 2014 (UTC)


 * Hex is most useful for me when something is used as a bit field, such as potions; a few blocks (such as anvils and leaves) are partial bit fields. Other than that, I don't see much use for it, since NBT editors tend to show values in decimal. I'd be fine with getting rid of the binary entirely, as it's easy to recalculate from hex if needed. -- undefined 20:01, 20 September 2014 (UTC)


 * Since most pages are already getting the first ver replaced with "See history", can we hardcode the see histroy now? <span class=nowrap>– (·) 19:08, 2 January 2015 (UTC)


 * Only if every page has an update and complete history section. One of the reasons to manually change each one is so you can make sure the section is correct before you go pointing to it. <span class=nowrap>– ᐸ <small style=display:inline-block;line-height:9px;vertical-align:-3px> 06:16, 3 January 2015 (UTC)


 * Then what about a temporary hidden tracking category for pages that use the old format? It adds the category if does not equal " ". <span class=nowrap>– (·) 16:50, 3 January 2015 (UTC)


 * Any usage of firstver and any usage of multiplevers which does not link to #History adds the page to . <span class=nowrap>– ᐸ <small style=display:inline-block;line-height:9px;vertical-align:-3px> 11:08, 6 January 2015 (UTC)

Tntres and hardness defaults
Just a quick change suggestion. Currently the parameters  and   default to using , when they really should default to using. Basically if the title is set, you then have to set the two parameters for the sake of accuracy. <span class=nowrap>— ( 17:33, 30 September 2014 (UTC)


 * . <span class=nowrap>– ᐸ <small style=display:inline-block;line-height:9px;vertical-align:-3px> 06:34, 3 January 2015 (UTC)

Substitute doc
It seems the /doc subpage has been updated to the new doc style, but this page is administrative protected, so this page was never updated. <span class=nowrap>– (·) 17:59, 23 December 2014 (UTC)


 * Done. -- undefined 23:56, 23 December 2014 (UTC)

Hardness link
As the page has been moved, can the hardness parameter be changed from linking to to ? <span class=nowrap>– (·) 02:48, 6 January 2015 (UTC)

and
Is there a reason that uses its "renewable" parameter to populate  and, while this template doesn't?   17:21, 6 January 2015 (UTC)


 * Not that I know of; added. -- undefined 20:22, 6 January 2015 (UTC)


 * The category really should be set to only show on base pages in the main namespace, the category just filled with project pages, mod pages, and user pages as well as the useful pages. <span class=nowrap>– (·) 20:51, 6 January 2015 (UTC)


 * Better now? -- undefined 23:19, 6 January 2015 (UTC)


 * Yep. <span class=nowrap>– (·) 23:30, 6 January 2015 (UTC)

Name ID behavior
Is there a reason why only shows on pages in the main namespace? [ changed it to require being in main a while ago], and I really don't see any reason why, as it prevents usage of the template on other pages (for example, sandboxes), even with set. <span class=nowrap>– (·) 17:59, 17 January 2015 (UTC)


 * I assume it was so userpages and the like didn't get automatic nameids. I've changed it to just disable the automatic part. <span class=nowrap>– ᐸ <small style=display:inline-block;line-height:9px;vertical-align:-3px> 00:40, 18 January 2015 (UTC)

Overridden tntres and hardness
Can the overridden tntres and hardness parameters be set to only show in english mainspace pages? Currently the category is filled with translations and user pages, as well as the useful pages. <span class=nowrap>– undefined/undefined 15:49, 26 February 2015 (UTC)


 * . <span class=nowrap>– ᐸ <small style=display:inline-block;line-height:9px;vertical-align:-3px> 04:58, 3 March 2015 (UTC)