Dota 2 Wiki

PRD on item passives[]

Did you test javelin/mkb/sange if they actually use prd or did you just assume they do? If you tested it, can you provide the results? Bu3ny (talk) 13:36, 3 September 2015 (UTC)

I just used this article as a source (, assuming the article isn't wrong. Psion1C (talk) 13:56, 3 September 2015 (UTC)
Btw, I don't know how to check game files or something to find out things like these or whether Phase Boots affect collision size. I'm sorry. ): Psion1C (talk) 15:31, 3 September 2015 (UTC)
Then don't edit/add notes if you don't know if your edits are correct or not. Do that only if you are sure about it. Wether or not abilities use prd is not in the ability files. It requires ingame testing. Bu3ny (talk) 15:36, 3 September 2015 (UTC)

Ability descriptions/lore[]

Don't change the ability descriptions and lores. They are ment to equal the exact ingame wording. Bu3ny (talk) 14:40, 5 September 2015 (UTC)

I understand, I'm trying to get rid of informal notations like "doesn't/can't", and instead use formal language everywhere on a wiki page, except in the lore, OK? Psion1C (talk) 14:56, 5 September 2015 (UTC)
Except in descriptions and lores, ok. Bu3ny (talk) 15:21, 5 September 2015 (UTC)

If you make a link like this #PRD on item passives, it directly moves the screen to the section/ability of the same page, without re-loading the page. Don't remove the # in those Bu3ny (talk) 18:19, 6 September 2015 (UTC)

Alright, nice to know. Maybe I should read a guide on the wiki semantics. Can you recommend anything? Psion1C (talk) 18:45, 6 September 2015 (UTC)
Not really, I figured most the things I know here by myself ._. But I'm sure this here should basically include everything. Bu3ny (talk) 19:03, 6 September 2015 (UTC)


I know this has nothing to do with this topic, but can you tell me how to redirect pages? (6.79 gameplay update is not linked correctly) Psion1C (talk) 08:27, 8 March 2016 (UTC)

See w:mw:Help:Redirects. Basically just drop #REDIRECT [[Page#Heading]] in an empty page. The sharp must be the first character of the page and everything after the page definition is ignored. Molldust (talk) 08:54, 8 March 2016 (UTC)
Thanks for your help. Just one more question - how to create a new empty page (I just know you can click on a red link and then edit it)? --Psion1C (talk) 09:31, 8 March 2016 (UTC)
Exactly, redlinks are empty pages. If you want to edit a redirect, use the link on the top of a page to get back to the redirect without getting forwarded. Or you use the &redirect=no URL parameter. Molldust (talk) 09:36, 8 March 2016 (UTC)

Don't redirect[]

Don't redirect I'm making new pages for the versions, thanks - Lemoncake(talk) 20:24, 10 March 2016 (UTC)

OK, I wanted to link all patches until 6.73 in every balance changelog. Psion1C (talk) 20:29, 10 March 2016 (UTC)


Hi. Can you please look and draw attention here:

formatNUM without hundred separator[]

The page im having problem is [1] you cam compare with axe. At Battle Hunger notes there is one expression
{{calc|v1*{{#show:#Battle Hunger|?value6#}}|v1={{#show:#Battle Hunger|?value2 tal#}}}}

Would be like plotting {{calc|(v1+v2)*v3|v1=120/120/120/120|v2=16/24/32/40|v3=10/10/10/10}}
the currently output at dota2-pt is "1 360/1 440/1 520/1 600". I would like to be "1360/1440/1520/1600".
Its just visually unpleasant with the space, dota2 dont have big numbers (7 digits or more) its unnecessary having this separator.

The expression there its calling Template:Calculate. Since its used often was needed to have "formatNUM" there. Axe was the third hero I checked for reference problems. Probably there is many more "problems" like this

I believe this is a low priority problem. Just help me if you have a free time. I just didnt like the visual but I can live with it

I want the wiki be as automated as possible. This is why I prefer to fix this expressions instead put the values directly. I hope this encourage more people to contribute and maintain the wiki

Just add formatting right into expression. If there are only 3 heroes with this problem - it's not worth it to change the template itself.

Replace s:value in {{Talent class}}[]

I implemented. But seems my way to loop "s:value1, s:value2,..." wasn't perfect. Can you help implement something like this?

replace s:value with the whole value, for example the value is 1/2/3/4/5/6:
  +s:value something -> +1/2/3/4/5/6 something
replace s:value1, s:value2, s:value3,... with the index one
  +s:value2/s:value4% something -> +2/4% something

--Elite stay (talk) 01:27, 17 November 2019 (UTC)

I'm sorry, can you give me a more conrete example (maybe a hero and specific values), cause I'm not quite understanding what you are trying to achieve. --Psion1C (talk) 00:29, 20 November 2019 (UTC)
Hmm.. For example, Monkey King/Talents]. The t4left is "+1 Wukong's Command Ring" and v4left is "1100/7". Now if I want to change v4left to "1100/7/1", then I could use "s:value3" in t4left to replace it with the third value of v4left, spliting by slash, which is 1. So the t4left could be change to "+s:value3 Wukong's Command Ring". Then the final text after replacing should be "+1 Wukong's Command Ring".

But for "s:value", it should be replaced with the whole value. The t4right of MK talents is "+100 Armor Wukong's Command" and v4right is "100". So I could use "s:value" in t4right. So the t4left could be change to "+s:value Armor Wukong's Command". The final text after replacing should be "+100 Armor Wukong's Command". For t4left, if I use "s:value" instead of "s:value3", it should be "+1100/7 Wukong's Command Ring", not "+1100 Wukong's Command Ring", intendedly, if v4left is "1100/7".

These all is what I was trying to do. But unfortunately, tested on zh, it failed. It replaced the "s:value" part with "1100/7/1", then put the last character "3" right after it instead. So the whole text was replaced with "+1100/7/13 Wukong's Command Ring". It's bad. It is the default case in {{Talent class}} where you should code it. --Elite stay (talk) 14:08, 20 November 2019 (UTC)

Is this really useful? We only do this in the ability descriptions and notes to save editing time, because there is more than one occurence of the same value. I don't think it's worth it here. Just change both by hand when needed. --Psion1C (talk) 18:50, 25 November 2019 (UTC)
Really! I have seen so much people forgot update that, including valve's. And buny said it's good. --Elite stay (talk) 12:48, 26 November 2019 (UTC)
Like this edit. --Elite stay (talk) 5:02, 27 November 2019 (UTC)
First, why are we calling it "s:value", what does the "s:" stand for? Second, do we ever need more than 1 value to be displayed in a talent text, or is it always exactly 1 value that is part of the text? --Psion1C (talk) 20:47, 27 November 2019 (UTC)
"s:value" is copied from valve's format. Its name doesn't matter actually. Lina/Talents needs two values on Fiery Soul talent. But yes, it can be simplied to one value. But I believe there will be 2 or more values in the future. --Elite stay (talk) 09:38, 30 November 2019 (UTC)
Template:Talents should also replace "s:value" words. --Elite stay (talk) 10:49, 28 December 2019 (UTC)