Where to put the appearance information in rewritten entity pages? --Naista2002 ♦ 16px16px 05:39, 16 October 2014 (UTC)
New discussions about article layout should occur on the style guide talk page, not here. KnightMiner has recently raised the subject in the Mob articles section but no consensus was reached. —munin · 16 px16 px · 06:37, 16 October 2014 (UTC)
Mob pages[]
Instead of writing "A wither skeleton may drop 0-1 coal, 0-2 bones, have a rare chance of dropping the stone sword" I think that using a table is better:
Ideas include: {{MobDrops|Mob}} → Module:DropsTable → Module:DropsTable/MobDrops. A template is given a mob name, which is passed to the template. It reads the info from mob drops sub-module and builds a table based on that. I'm somewhat good with Lua. --Naista2002 ♦ 16px16px 13:34, 21 October 2014 (UTC)
I prefer the text a little, as the table either requires quite a few columns (item, drop chance, three columns for looting chances, when it is dropped), or would just be redundant as to the infobox. (everything from that table is in the infobox only somewhat more compact). If a table is to be used, it needs to be designed in a way to avoid being too large and dropping below the infobox on smaller screens. –KnightMiner(talk) 14:40, 21 October 2014 (UTC)
Laura: you can place a link to a recipient (in this case, KnightMiner) there to notify him/her, either manually or using {{Ping}} or {{Reply}}.
What about the table, then I saw your sandbox. It is somewhat good. Fortune columns aren't always needed. Space confinements can be met with a collapsible.
Also, for eliminating problems with {{notelist}}, use <abbr> tags or {{Tooltip}} template instead.
Collapsible tables may be a bit overkill, as it would still jump below the infobox if too wide when uncollapsed. Really if the table can be kept at around 500 pixels it will work fine on the smallest screens we support. One way to keep it thinner would be to make the looting part stretch over the I, II, and III.
As for a module/template, it may be a good idea to have the template build the table, if only for consistency across articles, but placing all the drops in a module would remove simplicity of editing, and as the drops are really only used that way on one article, it would simply be placing the information somewhere else.
As for the actual use of the table, I'd say try it on a article or two. If it can present all the information better than the infobox, and is either below it or thin enough, then I would agree to using it, and we can discuss it becoming official policy on the style guide. We may even be able to migrate drops out of the infobox.
For example, with the article Guardian, it may be harder to actually use a table than text, such as if you get a fish, it still has to randomly decide what type of fish.
For example, with the article Guardian, it may be harder to actually use a table than text, such as if you get a fish, it still has to randomly decide what type of fish.
Also, the table should have an introduction (A wither skeleton has 4 possible drops: coal, bone, stone sword and wither skeleton skull). Laura Fidalgo(Talk / Contribs) 13:12, 22 October 2014 (UTC)
I also had a proposal, basically like that last one LauraFi posted. See here. And an introduction would be good, if only as a brief summary. –KnightMiner(talk) 14:27, 22 October 2014 (UTC)
Despawning subsection[]
Should there be a "Despawning" subsection in the Spawning sections of mobs? It would have information about the mob's despawning mechanic. If not, should the info be included along with the Natural Generation subsection? - Neutral0814 (talk) 14:24, 11 December 2015 (UTC)
Example:
== Spawning ==
=== Natural generation ===
Villagers spawn along with naturally-generated {{escaped link|village}}s, inside various buildings. In {{1.9}},{{upcoming}} A priest and a
zombie priest can be found inside {{escaped link|igloo}} basements.
=== Despawning ===
Villagers do not despawn naturally, but zombified villagers can despawn.
