Dota 2 Wiki
Dota 2 Wiki


I think the cost of the item should be listed. -- Wynthyst User Wynthyst sig icon.png talk 00:20, 3 June 2012 (UTC)

I agree, see my proposal in the notes below. -RJ 17:13, 3 June 2012 (UTC)


The below are notes made in the templates code. Discuss them. :3 -RJ 17:13, 3 June 2012 (UTC)
  • Items can be in multiple bundles
  • Link to main page for each bundle
    Bundles and their contests can be listed on Bundles. Each bundle doesn't have enough information to warrant its own page. -RJ 17:13, 3 June 2012 (UTC)
  • Style the links to the hero and slot pages
  • Prices/"Buy Now" button, similar to tf2wiki's
    Will get on this when the TF2 Wiki comes back to life. Krooc will have to help me learn SMW too, as that's our equivelent of the 'Dictionary' system the TF2 Wiki uses. -RJ 17:13, 3 June 2012 (UTC)
  • Figure out best practice for linking to the creator
    Link to Steam Workshop page or link to individual Steam profiles. -RJ 17:13, 3 June 2012 (UTC)
  • Make an infobox specifically for bundle pages, or re-use this?
    Bundles don't need an infobox. -RJ 17:13, 3 June 2012 (UTC)
You can build the bundle information totally into this infobox (bundle rarity, bundle cost, etc) to be used on the Bundles page, without having to create specific bundle pages. -- Wynthyst User Wynthyst sig icon.png talk 00:13, 4 June 2012 (UTC)
  • Page for each slot
    Item slots perhaps? -RJ 17:13, 3 June 2012 (UTC)
  • Page for each hero's items, linked to by his page
    This and/or a per-hero navbox - a more specific version of Template:Dota 2 Store nav. -RJ 17:13, 3 June 2012 (UTC)
  • General cosmetic item page, linked to by the main page
    Equipment, Dota 2 Store -RJ 17:13, 3 June 2012 (UTC)

Remove 'releasepatch' and 'releasedate'.[]

We have 3 parameters for dictating whether something is released - releasepatch, releasedate and released. To me, it makes sense to only go with the latter and set, in item pages, the value to be {{Patch name|5|31|2012}} (for example, displays Error: Invalid time. Patch - with the added benefit of automagic formatting based on language subpage). They're all hooked up to SMW, and the latter - released - expects a boolean value, so I don't want to just do my own thing and edit them in case they're there for a reason. So, is there a reason for them being there? Or can I go ahead and deprecate 'releasepatch' and 'releasedate'. -RJ

I'm not sure why there are two properties for the date, however I don't think we can easily setup {{Patchname}} to return in a format we can use semantically, if we ever want pages of automatically sorted dates (which we can do with the current system). I don't think we need two entries, though, since 'releasedate' alone should be enough (I think it can be parsed to create a link to the correct patch automatically, by passing the date to {{Patch Name}} in the template). -Baloroth 18:48, 4 June 2012 (UTC)


I think we need to beef up Categorization of Equipment, given how there will inevitably be more and more added with each patch. I suggest we add two dynamic categories using:

  • Hero name parameter
  • Slot name parameter

For example, a piece of equipment that went into the head slot for Tidehunter would automatically put it in the Category: Tidehunter Equipment and Category: Head Slot Equipment categories. There would need to be an if statement that if the hero parameter is all, that it instead puts it in something like Category: All Hero Equipment

I'd be happy to implement these changes if there's approval. --Ten19 21:37, 6 August 2012 (UTC)

Depending on what you actually want to accomplish with that categorization, you might already be covered by Semantic MediaWiki. For example, here are cosmetic items for Tidehunter's head: {{#ask:hero::Tidehunterslot::Head}}. This is given by {{#ask:[[Category:Equipment]][[hero::Tidehunter]][[slot::Head]]}} --Kroocsiogsi 22:03, 6 August 2012 (UTC)

Modifier icons[]

Should cosmetic modifier icons be included in this template like it is in game? I threw together a quick mockup of what something like that could look like here. --Litzsch (talk) 20:03, 16 July 2017 (UTC)

New parameter for cargo querying[]

We might want to add a new parameter (maybe something like |type=) to make querying for stuff like emoticon packs possible. The current way with categories does not work with Cargo and using _pageName LIKE "%emoticon%" would brake as soon as valve changes their naming scheme.--Litzsch (talk) 23:22, 12 December 2017 (UTC)