Template talk:DungeonItem
How to use
Coding
First call the header, which uses two parameters: 1 (background color) and text (text color)
{{DungeonItem/h|<background color, uses color templates>|text=<only if needed; put hex code for text color>}}
For each entry there are five parameters: 1 (item name), 2 (article location, optional: leave out if the same as 1), 3 (floors), 4 (bundle size, for stacks of items) and sprite (image location if not at MDBag <1> sprite.png, use "None" if no image.)
If an item with image and own article: {{DungeonItem|<item name>|3=<floors; put like so: 1F-10F>}} If an item with no image but an article: {{DungeonItem|<item name>|sprite=None|3=<floors; put like so: 1F-10F>}} If an item with no individual article and no individual picture: {{DungeonItem|<item name>|<main article>|<floors; put like so: 1F-10F>|sprite=<image location>}} If an item with no individual article and no image: {{DungeonItem|<item name>|<main article>|<floors; put like so: 1F-10F>|sprite=None}}
At the end of the table, place the table closing code:
|}
Example
Ragged Mountain
Item | Floors | |
---|---|---|
34-49 Poké | 1F-5F | |
Oran Berry | ??F | |
Aspear Berry | ??F | |
Chesto Berry | ??F | |
Escape Orb | ??F | |
Blast Seed | ??F | |
Shiny Box | ??F | |
Heavy Box | ??F |
Stony Cave
Item | Floors | |
---|---|---|
30-57 Poké | B1F-B5F | |
Oran Berry | ??F | |
Aspear Berry | ??F | |
Chesto Berry | ??F | |
Pecha Berry | ??F | |
Escape Orb | ??F | |
Health Orb | ??F | |
Everyone's Strength Orb | ??F | |
Rollcall Orb | ??F | |
Shiny Box | ??F | |
Sinister Box | ??F | |
Zinc Band | ??F | |
Heal Seed | ??F | |
Max Elixir | ??F |
Scarves
As the page is located at Scarf (Mystery Dungeon), can a work-around be put into the template? It would take a lot of coding for each individual item on the dungeon pages. --Abcboy (talk) 00:17, 23 December 2012 (UTC)
- There's already a parameter for article title. I don't want to add a switch to shorten that because it'll negatively affect the template's performance, increasing the load on the servers. Werdnae (talk) 02:30, 23 December 2012 (UTC)
TM
What should I do about TM links in this template I have seen two different sollutions {{DungeonItem|TM Roost|TM}} and {{DungeonItem|Brick Break|TM31|??|sprite=MDBag TM Sprite}}
Which one should I use? --Raltseye (talk) 09:50, 13 June 2015 (UTC)
Item | Floors | |
---|---|---|
TM Roost | ??F | |
Brick Break | ??F |
- I propose using
{{DungeonItem|Brick Break|Brick Break (move)|??|sprite=MDBag TM Sprite}}
, since 1) the mapping between TM numbers and moves changes every generation and 2) TM numbers don't exist in Mystery Dungeon. This looks like:
Item | Floors | |
---|---|---|
Brick Break | ??F |
Item link change request
Since the template is locked, could someone who can edit it change the MDBag Looplet Sprite.png
image link to MDBag Looplet VI Sprite.png
, where the image is actually uploaded? I don't even give a Schif (Talk • Contribs) 23:11, 11 August 2016 (UTC)
- There is no means to edit the template code for that. You can add
|sprite=
followed by the file name minus the extention if you want the proper image to display. Berrenta (talk) 23:17, 11 August 2016 (UTC)- I mean, yes, but if the template currently has a non-existent image link coded in, and there is an image with a different name, wouldn't it make more sense to just change the template (or... move the image, I guess)? I don't even give a Schif (Talk • Contribs) 17:57, 12 August 2016 (UTC)
add note argument
Could somebody add a note argument after the item name? MannedTooth (Talk) 03:39, 18 October 2016 (UTC)
Lookalike Items
How should we deal with Lookalike Items? The way I've seen us do them is {{DungeonItem|Gaggle Specs|Glasses|B1-14|{{sup/md|sky}}}}
, which creates a section link to Glasses#Gaggle Specs; the problem is that the item description is actually located at Lookalike Item#Gaggle Specs.
I suggest creating a new template that can be used as follows: {{DungeonLookalikeItem|Gaggle Specs|Glasses|B1-14}}
becomes {{DungeonItem|Gaggle Specs|Lookalike Item|sprite=MDBag Glasses Sprite|B1-14|{{sup/md|sky}}}}
. This looks like:
Item | Floors | |
---|---|---|
S Gaggle Specs | B1-14F |
Since Lookalikes only appear in Explorers of Sky, the {{sup/md|sky}}
can be included by default.
Alternatively, we could add a lookalike=yes
flag to the existing template. Qzekrom (talk) 07:44, 22 December 2019 (UTC)
- I think the code you posted with this template works just fine, and one template is easiest to maintain. Then, if the second parameter is
Lookalike Item
, that's basicallylookalike=yes
. Nescientist (talk) 17:18, 23 December 2019 (UTC)