Dota 2 Wiki:Discussion

__NEWSECTIONLINK__ [ create a new section]

Regular tournaments
We already have got pages for every tournament and for all tournaments together, but don't you think pages for series of tournaments like Dreamhack, TI or Premier League will be fine? JoinDota Masters for example, 7 were tournaments hold under this name. Such pages would contain stats like number of participations for each team, teams with the biggest number of wins and so on. What do you think about it? Example: User:Kemerover/Sandbox/The_International
 * Yes. But try to not link it from the Tournaments page. Redefining history 22:57, 5 June 2012 (UTC)
 * Ehm, I didn't get what I shouldn't do. And what about to create Regular Turnaments section in Tournaments?

Semantic MediaWiki vs Dictionary
So a couple of months ago we wanted a system to do as the Dictionary system did on the TF2 Wiki, and we didn't have anybody willing to host a bot to run the dictionary back then so we decided on SMW and that is what we have been using. Well, now we have the choice between the two; so I'm opening a switchover up for discussion. Should we drop SMW and use Template:Dictionary? - RJ 19:57, 3 June 2012 (UTC)
 * Dictionary - I prefer the Dictionary system. I have more experience in it and I think its a frankly better solution.  It would allow us to separate information such as Hero stats away from hero pages, reducing the likelyhood of that information being falsely modified; and removing declarations from pages or other templates gives us cleaner page/template code.  It is also centralised - which means mass-modifications (e.g. store price changes) are easier as they can all be done in one page, rather than the individual pages the values are hidden away in. - RJ  19:57, 3 June 2012 (UTC)
 * It's interesting that you describe putting values on individual pages as "hiding" them; I have exactly the opposite reaction. If I, as a new user, notice that Earthshaker's movement speed is incorrect, my first reaction would be to edit the page to correct it. If we used a dictionary to store that information, I would have to navigate a chain of templates to figure out where that value is stored. As another example, I'm trying to figure out how I would go about adding an item to Scout's Special Delivery item set. Do I have to add it to Item_set_infobox, or to Dictionary/item_set_weapons, or Set, or all three? Does one overwrite the others? Do I have to manually update Special_Delivery/ru, or is that updated automatically from one of the other values? Are there other pages I have to update, like maybe a page with a list of item sets or something? If Dictionary/item_set_weapons doesn't automatically update Special_Delivery and/or Set, then what does it do? How would I even know Dictionary/item_set_weapons exists if I hadn't stumbled across it earlier? In short, I won't claim that Dictionary is more or less logical or intuitive than SMW, but I suspect your experience with Dictionary is largely responsible for your comfort with it. --Kroocsiogsi 22:09, 3 June 2012 (UTC)
 * If you try to edit one of the dictionary subpages, there's an editnotice that makes it pretty obvious you're not doing the right thing WindPower 00:21, 4 June 2012 (UTC)
 * Yes, I saw that editnotice. "Please do not create or edit individual dictionary subpages, e.g. Template:Dictionary/items/flamethrower. Make changes to the main dictionary pages linked above instead." Dictionary/item_set_weapons is one of "the main dictionary pages linked above", is it not? --Kroocsiogsi 01:00, 4 June 2012 (UTC)
 * Dictionary much more convenient than use switch templates--FreeXMan 20:02, 3 June 2012 (UTC)
 * What does this have to do with anything? - Nickoladze 21:39, 3 June 2012 (UTC)
 * I don't understand your comment. I don't think anybody's suggesting switch templates, although they appear to be used for the last-mile language translation in both Dictionary and SMW. --Kroocsiogsi 22:09, 3 June 2012 (UTC)
 * We had this debate a month ago, it's even 3 discussions above. We had already created dictionaries for ability and hero ifo, and we all decided to switch to SMW because it was easier. Anybody who had a voice against SMW didn't say anything, and now we've spent hours of time converting everything that was using ability dictionaries to using SMW and now you want to switch back to dictionaries again? Absurd. I actually find this quite offensive because I was the one that originally spent 6+ hours setting up the ability dictionary and I voluntarily dropped the project in favor of SMW. You say we didn't have anybody willing to host a bot, yet Curse has told me over and over that they will host the bot I've written to manage the Guides listings. - Nickoladze 21:35, 3 June 2012 (UTC)
 * I originally asked Curse back in December to run a bot for the dictionary system, among other things; their response was that they did not have the server capacity to do it. If that is no longer the case then I hadn't been informed (I knew you had a bot, but I didn't know what was going on regarding hosting it).   Looking at The Plan (for SMW), one of the "Decision points" is "We decide to keep Semantic MediaWiki, or to scrap it." - that can effectively be the discussion going on now.  While a lot of work is already done for SMW, is it still the best system now that we have an alternative available? - RJ  22:01, 3 June 2012 (UTC)
 * Comment. It's a bit of an odd question, because they don't have the same functionality, although we probably shouldn't use both. Dictionary has the not-insignificant advantage that TF2 wiki users are familiar with it. SMW has the advantage that it is an established project that has decent documentation and support channels, and does not require a specialized bot.
 * But the killer-app of SMW, and the reason I am so enamored of it, is a function Dictionary lacks: SMW can query from a value, not just from a name. Dictionary can take a Hero and tell you what primary attribute it has; SMW can take a primary attribute and tell you what Heroes have it. This means that we can dynamically generate information about released strength Heroes, or lane-support Heroes, or Heroes with non-standard vision ranges, or all abilities that are UAMs, or all abilities that are spammable because they have a cooldown of less than 20 and a mana cost of less than 75, or all abilities that are partially blocked by magic immunity, or all items that provide bonus movement speed, or all the tournaments that have started but haven't ended, or all the players who play the ganker role, or all items that have abilities that are blocked by Linken's Sphere, or the twenty most expensive cosmetics, or all the immortal strange hats, or whatever other silly thing comes to mind. And equally importantly, these lists or tables or charts will be always up-to-date in all languages, even Hungarian, without manual modification.
 * But, y'know, tee-eff-teu gets along fine without all that, so maybe it's not necessary. ;-) --Kroocsiogsi 22:09, 3 June 2012 (UTC)
 * TF2 doesn't have nearly as much data to work with to make SMW worth while. Making a list of something such as which classes have a base HP > 120 would be trivial for them, as it would probably include 2 or 3, while a similar query for Dota 2 would return something like 50 heroes. Some of the best strengths of SMW involve the thing we were just trying to figure out last night, listing all heroes that have cosmetic items and list them out nicely. A dictionary would not be able to accomplish this. Like you said, all data in a dictionary is only accessible by name, and not value. That's a pretty big negative if you ask me. - Nickoladze 22:21, 3 June 2012 (UTC)
 * Hm. Excellent points.  I suppose both could co-exist, but have to be careful not have either treading on eachothers' applications...  The dictionary system is a lot better at handling translated strings and/or getting correct strings for things, e.g. what we use Template:Item name for; but it is inferior in its dynamicity of application.  It sounds to me like SMW would be add a ton of functionality to the guides section of the Wiki (the most likely place for obscure queries like "all heroes above 120HP"), which of-course the dictionary system is incapable of, and so for that reason I'm on-board with keeping it; but I do think the dictionary system can still be of value.  - RJ  22:38, 3 June 2012 (UTC)
 * I created the dictionary system as a consequence of Valve not wanting to install SMW (or any extension for that matter). It is much less powerful, much slower, very crufty (why use tons of wiki pages to store data?), and has some pretty bad limitations. SMW is more powerful and can do pretty much everything the dictionary system can do WindPower 00:21, 4 June 2012 (UTC)

Updated SkillboxMinimal
I went ahead and updated Template:SkillboxMinimal so it can accept a "source" variable that is a wikilink. The idea here being that you make the Hero or Item name the source, and the actual ability name the name, so it makes a nice wikilink to the source of the ability. The more links the better! Let me know if there are any issues/improvements on this. I'm also going through the articles that use the template and updating them accordingly. --Ten19 20:55, 9 June 2012 (UTC)

3d model on items?
how do you guys feel on 3d model viewing on items? example http://wiki.teamfortress.com/wiki/Lugermorph — The preceding unsigned comment was added by Wolf (talk) • (contribs)
 * It's a great idea and certainly something we can work on and implement in the future, but right now I don't think we are not ready to distract ourselves with big wiki-projects (those images take a lot of work, and sometimes even require modified models); we have a lot of content, especially after the Dota 2 Store patch, that needs to be improved (i.e. give every page an introduction - even if just one sentence, figuring out how to display things consistently and concisely) before we can take on implementing such new features. - RJ 00:49, 11 June 2012 (UTC)

Patrolmen
Faraday suggests adding a new rank below mod, with privileges to see and mark patrols, to help with vandalism, specially in foreign languages (or so I think), they will use patrol red signs system. (ChocolateWaffle) - Faraday  10:14, 14 June 2012 (UTC)
 * The patrol feature is, on the various wikis I'm involved in, never used. I have personally tried to push people in to using it, but it usually ends up with a day or two's worth of activity and then people just forget about it or give up on it (myself included); so as a feature it is, from my experience, worthless.  Introducing a new user group below staff and above regular contributors is also something I really do not like the sound of; it would split our community into editors we trust and editors we don't - something I think goes against the core ideals of a collaborative platform such as a Wiki.  We should assume every contributor makes their edits in good faith, and trust them to do so unless they prove otherwise.  So, to conclude, I am against the suggestion.  It would unnecessarily split our community all because of a feature that is rarely used. - RJ  20:25, 14 June 2012 (UTC)
 * I think it's a good idea becose we havent people who can replace me. No one will see vandalism without me. I am not sure that will i active the next two months. It's a plan how we can replace me. Faraday  20:05, 21 June 2012 (UTC)
 * Doesn't seem necessary, but it wouldn't make life any harder for me. RJackson is really the person who would have to manage this, so I support his decision. --Kroocsiogsi 20:10, 21 June 2012 (UTC)
 * Don't really care, but seems a unnecessary to me. Might work in the Russian language section if Faraday is worried about that. -Baloroth 20:13, 21 June 2012 (UTC)
 * I think it should be done. --DarkAssassin 20:37, 21 June 2012 (UTC)

Template:AbilityMinimal
I noticed that the last few days people changing the templates on the pages characters from Skillbox to ABILITY. There is a "Smaller" version of Skillbox ..... so can someone make the choice for ABILITY? or it is'nt necessary and i can continue using the SkillboxMinimal in futur ? LEG 15:02, 14 June 2012 (UTC)
 * I believe the new way of doing this is using Template:Ability with the parameter "layout = minimal". I'm not sure if it's finished, though, so I'd continue using SkillboxMinimal for now. --Kroocsiogsi 18:15, 14 June 2012 (UTC)

Template: Recommended to heroes

 * Special Case: Radiance is a core item in Lone Druid's Spirit Bear

I suggest to make "Template: Recommended to heroes", this template already used to page Radiance and Radiance/ru, i think it cool idea make it for all recommended items.If it is necessary, i can make it itself. Have you some ideas? Medok 08:45, 15 June 2012 (UTC)
 * Recommended items are very subjective content, which is not good content to author on a wiki. The recommended items we list in pages are only there because they're the in game default recommendations, so we justify listing them with the reason were documenting the default state if the game.  With "Recommended Heroes [to use an item]" there us no such default information in the game files, so we would author that information ourselves, and as that information us subjective it would likely attract a lot of edits and potentially cause edit wars.  For that reason I am against the suggestion. - RJ  09:27, 15 June 2012 (UTC)
 * What? The list will only include Heroes who have the certain specific item be included in their default recommended items. It's not (re)inventing anything, and it is merely listing those who use the item as suggested by Valve's list. If you see the Radiance page now, you'll understand that they all commonly have Radiance as a recommended item. -- Denmax 14:21, 15 June 2012 (UTC)


 * I see no problem with this, so long as it remains clear that these are recommended by Valve and therefore not subject to editing wars (or you will see the people raging about how Radiance is recommended on Enigma, for example). -Baloroth 15:22, 15 June 2012 (UTC)
 * I shown how this might be done via Semantic MediaWiki, on Radiance. (The code I wrote in Radiance would naturally be put into a template to ease deployment.) --Kroocsiogsi 09:07, 16 June 2012 (UTC)
 * I think Hero images are too flashy for this. Recommended items are disputed, as RJackson alludes, and I don't like the idea of making disputed material the most eye-grabbing thing on the page. If we implement this idea at all, I propose using text. I have shown how this might be done, below Medok's navbox, on Radiance. --Kroocsiogsi 09:07, 16 June 2012 (UTC)
 * How about the one I just posted now right below the division? Would this work? -- Denmax 10:00, 16 June 2012 (UTC)
 * It is technically feasible, but I would oppose it. The name of a hero is far more readable than its corresponding mini-hero, especially for new players. --Kroocsiogsi 10:14, 16 June 2012 (UTC)
 * Well my primary concern right now is how noteworthy is that information on an item page; we don't want to clog up pages with every little detail about an item just so we can say "Yep, we have everything." - we aim to provide enough information that a page is helpful and contains the sort of information people want to find. Do people visit item pages to find out what heroes (by default) an item is recommended to?  I can't think of a context where that would be helpful; though it is worth noting I'm a low-level player - perhaps there are some higher-skill uses that I simply cannot think up.  So yeah, that is my concern right now - would that information be of interest to anybody?  - RJ  00:58, 23 June 2012 (UTC)
 * I like the idea, item pages are rather empty except especial cases like Aghanim's Scepter, and if we stick to Valve's recommended items it isn't as subjective, and I sometimes browse items and go like "who would this be good on?", I doubt anyone would take that info too seriously, more like a suggestion, and we could always add a "this are only suggested items by valve, your experience may vary" or whatever -ChocolateWaffle 01:21, 23 June 2012 (UTC)
 * "Starting" items are boring. "Early game" items tend to be pretty boring. "Situational" items are perhaps the most controversial. How about just doing "Core" items (excluding Boots, Wand, Wards, TP, etc.)? There wouldn't be nearly as many, but it might give more reasonable results. --Kroocsiogsi 01:42, 23 June 2012 (UTC)
 * As long as it's clear that these are valve-recommended, I see no reason not to do this. - Nickoladze 01:49, 23 June 2012 (UTC)
 * I propose to this idea with, which can be seen in action on Radiance, Abyssal Blade, and Divine Rapier. I propose its inclusion on all item pages except basic items costing less than 900 (e.g. Bottle or Quelling Blade), or items with no results (e.g. Ultimate Orb or Soul Booster), or items with too many results to be useful (e.g. Boots of Speed or Bracer). I have a few use cases in mind. Amelia reads about Radiance, and thinks it sounds incredibly powerful. Why don't more people get it? She discovers that it is recommended for heroes who are hard to kill, so perhaps it would not be as powerful in the hands of a glass cannon. Bartholomew just got creamed by a Lifestealer with Armlet of Mordiggian. He decides he wants to try this item for himself, but he doesn't like playing Lifestealer. He sees that Armlet is also recommended for Huskar. He decides to try getting Armlet on Huskar. One disadvantage of this feature is that it is subjective. Another disadvantage is that our item pages are sparse, so this section will appear to have undue importance. I do not believe these disadvantages outweigh the advantages. To mitigate the first disadvantage, only Valve-recommended items are shown. It is not obvious to casual editors how to modify the displayed items, which is fine, since they will hardly ever need to. To mitigate the second disadvantage, the section can be short and boring, devoid of icons and color. For this reason, I oppose the sample template at the top of this discussion topic. (I also strongly oppose the template on Radiance/ru, which I think is a misapplication of the navbox concept.) If I receive no further comments, I think I will "be bold" and implement it on the basis of the mildly positive comments so far. (Perhaps I can come up with a phrasing adjustment to please Baloroth.) --Kroocsiogsi 01:06, 14 August 2012 (UTC)
 * Looks pretty good. Maybe change the language to something like "Heroes for whom Valve recommends $ITEM as a core/situational item." -Baloroth 02:13, 14 August 2012 (UTC)
 * [[Image:Pipe of Insight.png|x16px]] I'll stick that in my pipe and smoke it. --Kroocsiogsi 03:30, 14 August 2012 (UTC)

We now have Template:Item infobox wrapper
Template:Item infobox wrapper has been created. Over the next few days I plan to use bots, elbow grease, and volunteers to deploy it across non-English pages, replacing Template:Item infobox. --Kroocsiogsi 05:23, 22 June 2012 (UTC)
 * What are peoples' feelings about creating skeleton item pages (like, infobox only) algorithmically for all languages where they don't exist? Useless load on servers, or painless way to seed new languages with lots of blue links? (The same can be done for Heroes, but I'm thinking of dealing with items first.) --Kroocsiogsi 02:42, 23 June 2012 (UTC)
 * I'd say not to make skeleton pages, it could end up making languages look relatively complete in Dota 2 Wiki:Translation progress but with the majority of articles actually empty; red links serve as a to-do list for translators, I think eliminating them would do more harm than good in the long run. - RJ 03:14, 23 June 2012 (UTC)
 * Cool. In that case, should we delete untranslated pages? (e.g. Iron_Branch/cs) --Kroocsiogsi 03:44, 23 June 2012 (UTC)
 * Yes - RJ 14:51, 23 June 2012 (UTC)
 * a bunch of these. Looks like /cs was the only major offender. --Kroocsiogsi 22:39, 26 June 2012 (UTC)
 * with more bots and less elbow grease than expected. There are probably some stupid bot-edits that I missed, but overall it looks good to me. French items were formatted oddly, so I think I'll patch those up. If you notice anything else, holler at me. Or fix it yourself... --Kroocsiogsi 22:44, 26 June 2012 (UTC)

Potential Guide System Discussion
The wiki staff has been working hard on a submitting and rating guide system that is close to completion, but we would like to hear input from the community on what would work, what wouldn't, any suggestions, etc. For starters, should anyone be able to edit guides or should they be user private? -ChocolateWaffle 12:23, 28 June 2012 (UTC)
 * Discussion should happen on Talk:Community Guides, not some generic "discussion" page. -- Wynthyst [[Image:User Wynthyst sig icon.png ]] talk  12:28, 28 June 2012 (UTC)
 * I put it here because it will be a main feature of the wiki, that page is too obscure and unreachable by most users, and even more by newcomers, so atleast we should leave the link here for others to find it. -ChocolateWaffle 12:34, 28 June 2012 (UTC)
 * I was told to wait for Kaelten in IRC at least twice now and neither time has he tried to get ahold of me. I wrote an amendment to Community Voice that needs to be "inspected" and then installed, as well as a bot that needs to be hosted and put on an automated cron job. I completed those at the end of April, if I remember correctly. - Nickoladze 21:43, 28 June 2012 (UTC)

Front page layout compacting
As discussed in the channel I would like to make a change to the front page layout that will better display the important links, namely the hero tiles. With Valve's release of the heropedia I think it's important that we make our pages as visible as possible, since people are more likely to go here first. So what I want to do is move all index links to one row and condense the latest patches box into a height that is about the same as the resized index box. So in other words have a flow with the most important content on the top, and continuing downwards in order of interest/usefulness/importance.

Here is an excellent concept of what I'm talking about made by Waffle. -- Lagg 01:00, 30 June 2012 (UTC)
 * Concept looks great. We would have to scale down the index nav icons though to be more friendly with smaller screens, but I agree with the suggestion. Feel free to work on a sandboxed version of the page, and we can iterate and perfect it together. - RJ  01:06, 30 June 2012 (UTC)

Dota2 not working properly since Luna,Wisp patch.
Since the release of the new patch I've been having problems with dota2 I try to open it and when it goes to the Main Menu it gets stuck there.Instead of letters and stuff its all squares and so you can't read anything and it also crashes after a while bringing me back to desktop if anyone else has the same problem please tell me and let's find a solution. — The preceding unsigned comment was added by 188.4.108.116 (talk) • (contribs)
 * We are not a tech support / help website. The Developer Forums would be better suited for your query. - RJ  18:11, 2 July 2012 (UTC)

Adding Dotacinema Introduction videos for all Heroes
I would like to add the Introvideos for the Heroes Dotacinema made for each hero. What do you guys think?
 * Copy a hero page into your sandbox and add a video to it. If it looks good, I agree with the idea. - Nickoladze 20:10, 6 July 2012 (UTC)


 * First, it certainly shouldn't go where you first put it IMO (not at all the right place for it). Second, I'd prefer it to be a simple link, rather than an embed. Embedding it takes up far too much room on the page overall. Put a link under "See Also" and I think it'd be fine. -Baloroth 20:25, 6 July 2012 (UTC)
 * The size can be changed on the embedded video, I agree that it was too large. Link - Nickoladze 20:29, 6 July 2012 (UTC)
 * Yeah, on second though an embed below the abilities themselves (but above recommended items) would look fine, if it was a little smaller. We want the ability statistics to be above the video, since they are more important/looked up more often, but recommended items and below are probably less important information than the video. -Baloroth 20:37, 6 July 2012 (UTC)


 * The Dotacinema videos would add further clarification and visuals to skills, which some people probably prefer over having just a list of notes. About the placement, at the TF Wiki we embed the videos underneath the statistics (example page), and since it's mostly information about skills and the hero, I think it would be best to embed the video underneath the Abilities section, potentially underneath the Recommended Items section. Only the inclusion of a link to it would be fine with me as well. Hefaistus 20:39, 6 July 2012 (UTC)


 * @Nickoladze I wanted it to make it like on the TF2 wiki. But here because its about the Abilities I wanted to add it above so you get an overall look at it and then you can read what the abilities do and not and so on.
 * I think that most people coming to the Wiki will be looking for the ability info first. People looking specifically for videos on a hero will probably go straight to YouTube. - Nickoladze 21:45, 6 July 2012 (UTC)


 * I wouldn't mind seeing links to the video somewhere on the page as a footnote or something along those lines, but personally I've always thought that video embeds direct people's attention off the page a bit too aggressively. -- Lagg User Lagg optf2 icon.png 21:47, 6 July 2012 (UTC)


 * Valve did it, videos is very old and good idea, why not? Faraday  00:33, 7 July 2012 (UTC)
 * I presume you're referring to the videos embedded on the TF wiki. That was actually us that did it, and I'd rather not repeat it here because it's brought more grief than good (people have quite the tendency to try and sneak in their own videos of debatable usefulness to get view count bumps) -- Lagg User Lagg optf2 icon.png 06:35, 7 July 2012 (UTC)
 * No-no, i mean videos on heropedia from Valve Faraday  08:35, 7 July 2012 (UTC)


 * If we link to DotaCinema, why not link to 'Purge plays X' or DotaFire or the alt-tab hero guide, or any of the other garbage out there. The content is weak at best and absolutely should not be embedded. Even linking to it isn't an idea I'm fond of, as many of the guides are simply just bad and wiki is supposed to remain objective sources of facts. Decency 02:32, 7 July 2012 (UTC)


 * Well now I'm confused, at first I thought that this was an official thing like Heropedia because I misread the original talk line. In this case I am changing my vote entirely to -- Lagg User Lagg optf2 icon.png 06:35, 7 July 2012 (UTC)


 * The very same point as Baloroth. Takes too much space on the page and too much attention. Also, embded things generally slow down browser performance - if you have several tabs open and each has a video in it. I recommend adding a link at the bottom of the page, thou. Viperys 08:28, 7 July 2012 (UTC)


 * The wiki is supposed to include information that are as objective as possible. That's the reason the idea of a "Guides" section was introduced, a place where extremely subjective (but useful) information could be allowed and stored. There would be no problem if this was the guide section, but in my opinion DotaCinema videos should no exist in the main hero pages. I also don't think there should be any blatant advertising of DotaCinema on the wiki pages. Redefining history 08:50, 7 July 2012 (UTC)


 * What if we put up links to the Heropedia videos in the ability notes? For example, we could add it like this to Earthshaker's Fissure ability: Visuals. Hefaistus 12:23, 7 July 2012 (UTC)
 * I like those videos. They're not on DotaCinema's channel and they have no logos or advertisements anywhere in the video. It's much better than us going through and making videos if we ever wanted to. - Nickoladze 12:39, 7 July 2012 (UTC)
 * i like this idea. Faraday  12:46, 7 July 2012 (UTC)
 * I like this idea. Can't embed them, obviously, since there are too many. One thing is we should make sure whatever we do that we get the makers/owners permission (I don't imagine Valve will mind, but we should make sure, since some of the DotaCinema guys actually made the videos). -Baloroth 18:20, 7 July 2012 (UTC)

Hero Model Pictures in infoboxes
This is a project I have been working on and off for quite some time now. People have oftentimes expressed the desire for us to show in-game hero models on their pages. For this reason, I have been working on several infobox variants to showing off those models, as well as pictures of every hero currently (up to Disruptor and Undying) in the game, with the exception of Wisp. The infoboxes can be found here, while all hero pictures can be found here. Be sure to leave behind feedback. Hef aistus 19:06, 7 July 2012 (UTC)


 * I like that Idea, but I would only take ONE Picture for the Hero page (A 3D View or Animated version) and the Portrait goes into the Gallery Section.

Dota 2 heroes list with difficulties (according to hero pages) and attributes
Would this be of use to anyone? See User:Fizz/Heroes Table... I don't know where I should put it, if I should put it anywhere... Fizz 19:24, 18 July 2012 (UTC)
 * My instinct is that it doesn't really belong anywhere right now. Then again, I'm not sure List_of_heroes_by_difficulty really deserves a page either. I'm not terribly happy with the ultimate data source (i.e. hero pages). User:Pigbuster/Hero_Difficulty seems more interesting to me, but might be tricky to work back into the wiki. For type/attribute/role, I happened to make a mockup yesterday, but I have no plans at this time to put it into the wiki. --Kroocsiogsi 20:15, 18 July 2012 (UTC)

Heroes' skill level recommendation
I'd like to express my opinion about paragraphs such as the following on hero pages: "Due to Slardar's easy ability to adapt, he is a great hero for new players to try. He is recommended for new players." May I be informed of who makes these recommendations? Are they results of community votes or simply opinions of some editors? These assertions seem highly subjective and do not belong in a wiki context unless we have sources to cite or make sure everyone agrees. This reminds me of the days when everyone recommended Skeleton King to newbies simply because he had an extra life (and guess what, he is indeed still recommended here). Most of the heroes recommended to new players actually require a lot of skills to be effective, and some of them see expert use in the competitive scene. Yet every hero page has a line "This hero is recommended for ...", which makes it sound like community consensus and thus authoritative (Actually, the same applies to the "Tips" part of many hero pages, too).

In general, my point is that possibly subjective and/or controversial content (this includes strategy guides/tips, appraisals of a hero/item's power, and assessment of competitive clans/players) should be treated extremely carefully in a wiki, which is generally not the case here. People will tend to believe whatever is said here as Dota 2 Wiki is currently the most comprehensive database about Dota 2. I understand that being undermanned and a lack of policies is probably a main cause for the permeating subjectivity, so the competitive sections could remain as they are now. But it should be obvious that heroes' skill level recommendations and such are dangerous content that could affect the site's credibility. So, as a start, I suggest removing the recommendation paragraphs permanently, or at least temporarily before we come up with a way to improve them substantially. I'd also love to hear your opinions on this topic. Wyverald 02:52, 19 July 2012 (UTC)


 * PS. Sorry if I sound a little hot-headed with that wall of text. Dota 2 Wiki is actually doing a pretty good job; it's just that sometimes I get really annoyed with subjective content (even if it's just a little off the line). I hope the sharp comments did not offend someone, and I really hope some of the administrators could share their opinions. Wyverald 03:07, 19 July 2012 (UTC)


 * Yep, it's just the opinions of "some editors". No community votes or consensus-seeking. Ditto with the "tips" sections, the "gameplay" sections, and the "recommended items" explanations. The Dota 2 Wiki hasn't really shunned opinions as yet; just because it's a wiki doesn't mean it's Wikipedia. Whether this is desirable is an important question that, to my knowledge, hasn't been seriously addressed. We keep procrastinating about launching a Community Guides section, but it's not clear how much, if any, information would be removed from hero pages if it were launched. About your suggestion to remove difficulty information: I am (unhelpfully) . --Kroocsiogsi 03:54, 19 July 2012 (UTC)


 * P.S. Although it's not part of the wiki, you might want to know about User:Pigbuster/Hero_Difficulty (which is basically the work of one guy). --Kroocsiogsi


 * I am sympathetic to your concern, those difficulty ratings are pretty subjective. However, they are also somewhat useful to new players. Sure, Slardar is a bit tricky to play very well, but he is fairly easy to play overall (same with Skeleton King: he is very easy for new players to learn the basics with, since he has one active skill). I think everyone understands that, as a wiki, everything on it is community contributed and therefore subjective considerations such as difficulty ratings (difficulty is inherently somewhat subjective) are just that, subjective, or at least I hope this is the case. If anything, I think the language could be tweaked to reflect the fact that it is an opinion more clearly, but they are still useful so I don't think we should remove them entirely. -Baloroth 15:12, 19 July 2012 (UTC)


 * I'm going to have to here. When I first started getting deep into D2 I went to look at the wiki and was quite surprised that some heroes like Pudge were listed as intermediate while Dazzle, Witch Doctor, and Warlock for example were listed as new. At first I assumed that a lot of these changed from dota but the more I play the more I'm starting to question the recommendations. It's hard enough for the games themselves to do this because of how subjective skill levels tend to be. It seems like it might be better to just emphasize the pros and cons of each hero's attributes and skills and let people determine it themselves. -- Lagg User Lagg optf2 icon.png 06:45, 22 July 2012 (UTC)

Rating system for hero difficulty
Regarding the issue above, what do you think about implementing a rating system (like 1 to 5 stars or something) for hero difficulty in each page? Allowing all users to vote we could reach a consensus on the average difficulty of a hero based on the playerbase opinion, instead of having biased opinions in hero pages. -ChocolateWaffle 23:32, 24 July 2012 (UTC)
 * I like the idea, the community drives the website and a whole and they can vote on this as a whole instead of lots of edits swapping the first few sentences around. Here's what the rating system looks like, btw: -- Nickoladze 23:35, 24 July 2012 (UTC)


 * If there are actually enough people willing to do this I think it's a suitable alternative to my solution. I hope to see enough votes for a meaningful average though. -- Lagg User Lagg optf2 icon.png 12:23, 26 July 2012 (UTC)
 * Rating systems are typically used to show how good something is; in this case it would show how 'difficult' a hero is - 1-star being super-easy, for instance, and 5-star being very difficult. The problem that arises here is that in the different tiers, or contexts, of Dota games the difficulty of heroes varies - one hero, for example, might be super-easy to play and stomp low-level pubs with, but in mid/high level pubs, that hero might end up actually being quite difficult to play with simply because opponents' have a bit more knowledge of the game.  In such situations, is it correct to throw a simple 3-star "Medium difficulty" rating on that hero? - where the hero is super-easy in low-tier, but super-hard in high-tier?  I think this solution risks simply being inaccurate and cause of dis-credibility because of it's simplicity being applied to the complexity of Dota.  I have to question the appropriateness of putting such skill-ratings on heroes on a Wiki - a resource intending to be factual (avoiding subjective content).  Lagg's suggestion of a pro's-and-con's is probably a much better solution, but who dictates those pro's and con's, and how do we ensure they're completely factual?  I think the best solution would be to drop the subjective topic of 'How easy is this hero', and stick to the facts - the heroes stats and abilities; and leave it to a player's game knowledge to determine how easy/difficult a particular hero is - for newbies without game knowledge, there are other resources out there aimed at them to help them learn this initial knowledge. - RJ  18:27, 30 July 2012 (UTC)


 * I don't think we need to worry about "difficulty at high-tier": anyone playing at that level already knows how difficult it is. As for people who are watching games at that level, I don't think it is all that important for them either. Such ratings are mostly for newer players, and I think if we note that or imply it somewhere in the scheme, a crowd-based rating scheme would be informative for the kind of people who are looking for a difficulty rating for a hero. -Baloroth 22:43, 30 July 2012 (UTC)


 * The immediate upsides and downsides of a given ability are quite obvious if observed a few times. I do think we can realistically give this as long as people can stay neutral about it and not deviate into subjective things. For example, Chronosphere's upside is that it's a beast among disables that even affects buildings. A downside is that it disables all units in the effective radius, meaning allies as well. From that information alone contained in each ability, I think that it can provide people a nice way to judge for themselves how difficult a hero is according to their familiarity and play style. Even if we assume that a generalized rating system is only going to be paid attention to by people in so called "lower tiers" (we shouldn't) you're still going to see the same problem that you would with a so-called "higher tier" player. Dota is just too complex to have a blanketed system like this as far as I'm concerned. Though I will say that if we do go with the voting someone needs to make better sprites, stars aren't going to work. -- Lagg User Lagg optf2 icon.png 07:06, 3 August 2012 (UTC)
 * Nnngh, I just realized we are using CommunityVoice which is silly and has no features for using different star images. This is going to make pages look pretty bad. Unless someone besides me wants to hack CommunityVoice to allow this and get Curse to install it I'm going with a definite vote. -- Lagg User Lagg optf2 icon.png 21:14, 3 August 2012 (UTC)


 * So is everybody for this idea then? Should we add it into the hero infobox? -- Nickoladze 21:36, 2 August 2012 (UTC)
 * Letters dont work. (Ð¿Ð¾Ð´Ð°Ð½Ð¾ 5 Ð³Ð¾Ð»Ð¾ÑÐ°)Ð¡Ð¿Ð°ÑÐ¸Ð±Ð¾ Ð·Ð° Ð³Ð¾Ð»Ð¾ÑÐ¾Ð²Ð°Ð½Ð¸Ðµ) Faraday  09:07, 3 August 2012 (UTC)
 * Definitely a good idea, especially if we can get a reasonable sample size of users participating. If it gets too skewed from spam or something, I suppose we could come to a consensus on the level and set it manually? --Ten19 17:34, 3 August 2012 (UTC)
 * Any more thoughts on implementation of this? Should 5 stars mean max difficulty? Any way we could make this clear to the user? Faraday, what are you talking about with those characters? It's broken for translated pages? -- Nickoladze 01:56, 14 August 2012 (UTC)

Illusion damage taken language
Naga Siren has been having a minor edit war over how much damage her illusions take (the amount is 600/500/400/300%, but Valve and formerly our page for her stated this in bonus amount, which is of course 500/400/300/200%). Different pages refer to this in different ways, some as the straight percentages (like Illusion) and some in bonus percentages (like Shadow Demon's Disruption). I propose that we decide on one method to refer to illusion damage and use that on every relevant page on the wiki, 'no matter what language Valve uses for that skill' (since I believe

My suggestion would be simply the percentage of damage that the illusions take (so 200% for Chaos Knight's illusions, and 600/500/400/300% for Naga Siren's illusions), since that is what Playdota does and I think it is a lot clearer. Our Illusions page, among others, already does this and I think it is a lot clearer and more universal that specifying the extra damage the illusions take. -Baloroth 16:01, 23 July 2012 (UTC)


 * Absolutely. I don't care which style we use, as long as (1) it's uniform and (2) we devise language that totally eliminates the ambiguity. The only reason I haven't taken this on myself is that I still don't know what language to use:
 * Total damage taken: 300%
 * Total damage taken: 300%
 * Net damage taken: 300%
 * Damage taken multiplier: 3×
 * Received damage multiplier: 3×
 * Total damage taken: 100% + 200%
 * Bonus damage taken: 200% (total: 300%)
 * Bonus damage taken: 200%
 * Bonus damage taken: 200%
 * Additional damage taken: 200%
 * et cetera
 * With any of the above, multiples (2×) could be used instead of percentages (200%).
 * "Total damage taken" and "bonus damage taken" are demonstrably ambiguous, because users keep mis-editing them. There's going to be constant cleanup work to keep all the pages in line unless the language is unambiguous even to our beloved "challenged" editors. I hate to admit it, but I'm leaning toward the wordy-but-completely-unambiguous versions, like:
 * Bonus damage taken: 5×/4×/3×/2× (total: 6×/5×/4×/3×)
 * Also, the same issue exists for critical strikes. --Kroocsiogsi 18:33, 23 July 2012 (UTC)

Organized Equipment Tables
As more and more items are getting added, I think it's time we come up with a standardized Equipment Table, so it's not just a big alphabetized pile. I've come up with a format that has flexibility so you can add additional items/categories. Now, the concern here is the impact on the article page. No matter what, the table is going to grow in size with more items, but being organized does make it slightly larger. This is addressed by making the whole chart collapsible. Here is my proposal:

Obviously things can be tweaked. I've also implemented a smaller scale Table Icon template so it does save space as more are added. If approved, I'm more than happy to go through and create all of the tables for heroes with equipment. Thanks! --Ten19 05:22, 26 July 2012 (UTC)
 * Looks good to me. Horizontal-space, or the lack of it on smaller displays, is a concern I'd have for this - but it seems to scale pretty well as-is. - RJ  18:27, 30 July 2012 (UTC)
 * Sounds good. If no one has any objections, I'll start implementing this wiki-wide in the next day or so. --Ten19 05:36, 31 July 2012 (UTC)
 * I like it, better sorted than they are right now. -ChocolateWaffle 02:55, 3 August 2012 (UTC)
 * Like RJ said it, make it horizontal. But it looks pretty good for me. -Blutsense 09:45, 3 August 2012 (UTC)
 * Would be much better, if u could do Raritys in-table. -ZekoN How to do time? Sorry, Im a beginner in Wiki.

Adding the Tournament Items from the Store onto the Infopages of that Tournament
I made a preview for this here. This would give the opportunity to add the replay tickets from the store onto the pages without just linking to it, like it is right now in the dota store page of the wiki. --Blutsense 10:05, 28 July 2012 (UTC)
 * Looks good. - RJ 18:27, 30 July 2012 (UTC)
 * If no one else has anything to say I would start implementing that later. --Blutsense 09:46, 3 August 2012 (UTC)

Player/Team template
Do we need one? Example: http://www.dota2wiki.com/wiki/User:Kemerover/Sandbox/Template:Team

Group permissions pertaining to AbuseFilter
Over at Technical Requests, I have requested that some group permissions pertaining to AbuseFilter be changed. Specifically, I requested that,  , and   be granted to all users. The configuration can be seen at the AbuseFilter extension page. There are many wikis that do this, notably the English Wikipedia, so I don't think it's a security or privacy concern. The reason I requested these permissions is that we have had several comments about trigger-happy abuse filters, and I am concerned that we may be handing out some permanent IP blocks (and account creation disabling) to good editors. Being able to see the actual edits that trigger the abuse filters may help us identify improvements to the current filters. User:RJackson previously requested and was granted permission to review the AbuseFilter logs, but I think the job has turned out to be too large for one person, and I don't want to nag.

Wynthyst has asked about community input about this change, so here's a place to do it! --Kroocsiogsi 23:36, 4 August 2012 (UTC)
 * Yeah, I tried monitoring them when I first got access; but it's too much effort for me to maintain. If somebody reports their wrongful Abuse Filter match to me, I look into it and rectify it - but I don't actively monitor it. I have no problem with a publicly viewable log. - RJ  23:52, 4 August 2012 (UTC)


 * with extending privileges down to mods to lessen the burden on RJ, although I'm not knowledgeable enough on the matter to decide whether or not regular users should be able to see some of these things. -- Nickoladze 00:30, 5 August 2012 (UTC)


 * We may be able to reverse wrongful bans for anyone who goes to the effort to request it, but it is hard to know how many people have been banned and either did not know how or were unwilling to take the effort to reverse such bans (and I know it has been a problem in a few cases). -Baloroth 02:23, 5 August 2012 (UTC)


 * It took me about 7 minutes to even get here, I was trying to update hero update history and I keep getting banned every 5 seconds for opening many pages. Not only should staff/good users be safe from it, but I also think the limit (if it can be adjusted) is a tad too low, considering images loaded also count towards the cap, visiting 2-3 pages that have tables with images easily fills the limit and triggers a ban. EDIT: It took me another 5 minutes to make this edit because I got banned again. Anyway, just reading everyone else's comments, you seem to talk about a different kind of ban, a permanent one (I know some have happened when making large edits), but the anti-spam 5 minute ban is also a pain in the butt as I've been witnessing for over a week. -ChocolateWaffle 11:59, 6 August 2012 (UTC)
 * That's the new anti-spidering measures that Curse have enabled, not anything to do with AbuseFilter. --Kroocsiogsi 18:23, 6 August 2012 (UTC)
 * Unsure if you were there when I first discussed this with Kaelton, but that should be fixed as soon as images are moved onto a different server. Because of image caching, I've had no problems loading pages lately. If I were you, I'd try and bug Kaelton to get this migration expedited. Also, what Kroo said. -- Nickoladze


 * I because this is one of those things someone at Curse should have thought to do in the first place, so naturally I'm inclined to. -- Lagg User Lagg optf2 icon.png 06:04, 7 August 2012 (UTC)
 * Just  Faraday  14:09, 10 August 2012 (UTC)

Permament IP blocks, and blocking in general.
It has been brought to my attention that permanent bans on mischievous IP editors - as we have been doing - has some concerns we need to address. The primary concern is the possibility of blocking legitimate contributors that have inherited, from their ISP, a blocked IP address. Given we can only block specific IP addresses, and not IP ranges, the occurence of inheriting a blocked IP is very very rare; but even so, if it happens it can frustrate potential contributors and possibly harm that contributors perception of the Wiki. The permanent blocking of IP addresses I could previously justify as taking a hard-stand against clearly detrimental behaviour (essentially vandalism, on whatever scale), with the intent of discouraging such behaviour from occurring in the future. The aim of this discussion is simply evaluate the way we handle such detrimental behaviour; essentially: Is a permanent block over-the-top? Given that blocked IP addresses can be inherited, would a month or so's block be a sufficient replacement for a "permanent" block? and should we consider a new kind of policy to lead to permanent blocks e.g. scale the block length with how many blocks a previous user has had? I'm trying to keeping this discussion open, so I encourage discussing anything re: blocks; but I would like people to comment specifically on the issue of permanent blocks - whether they're (ever) appropriate to IP addresses. - RJ 14:24, 11 August 2012 (UTC)
 * It's just fine to block IP addresses when there is obvious vandalism being done, but I don't think enough people are understanding that as you block more and more IP addresses the chances of you blocking someone who the IP gets reassigned to that may want to contribute increases. The chance of a single address being used by someone that will also want to edit here are very small at the moment. But given enough time there is a distinct possibility that you have blocked a quarter of an entire ISP subnet before you know it. If you understand this and the repercussions of it this talk line doesn't apply to you. Everyone else I suggest take it seriously. -- Lagg User Lagg optf2 icon.png 16:47, 11 August 2012 (UTC)


 * It is almost never appropriate to issue a permanent block on a first offense, IMHO. Permablocks should be reserved for repeated infractions after previous blocks. (And even then, a year would be sufficient.) I would go further and say that blocks of any length are usually not appropriate on a first offense. A lot of trolling comes from people within the Dota community who could be rehabilitated into contributors. Immediate blocks are appropriate for botspam and goatse, but not "DENDI SUCKS EGGS". --Kroocsiogsi 17:43, 11 August 2012 (UTC)

Cosmetic Item navigation
I am not a fan of Template:Dota_2_Store_nav. It is already too large to be useful. I propose deprecating it. In its place on the cosmetic item pages of heroes, I propose User:Kroocsiogsi/Single-hero_cosmetic_item_nav, which is unfinished. The notable differences include: (1) only items for the current hero are shown, (2) if an item is in a set, only the set is shown, (3) images are shown, (4) the template depends on Dictionary for translation, which in turn depends on WindBOT. The template bears similarity to the individual hero equipment templates (example), and I have not fully considered whether this template might replace them as well.

Two nearly identical templates would be made for couriers ( Here.) and for announcers ( Here.). We would need to consider how taunt, tool, and tournament items should be navigated.

Areas of the template that I intend to work on, if there is interest, include:
 * 1) Font size, image size, and alignment
 * 2) Possible removal of images  Still could be done if it's an issue.
 * 3) Possible implementation of rarity coloring
 * 4) How to link to Dota 2 Store and/or to the hero
 * 5) Localization

I would appreciate your thoughts. --Kroocsiogsi 23:31, 17 August 2012 (UTC)


 * I'm a fan, as long as we keep the pages that list all equipment, all bundles, etc. I definitely want rarity coloring, which would probably mean a complete recoloring of the template in a light-on-dark style. I've been thinking of ideas in my head for overhauling the cosmetic item navboxes infoboxes a bit as well, might be a related project to think of at the same time. -- Nickoladze 23:52, 17 August 2012 (UTC)


 * Hm, I wasn't thinking about coloring the text, I was thinking about a border or background or something. Coloring text also breaks redlinks and visited links, so I try to use it sparingly. And yes, I'm not proposing removing the equipment page or anything like that. Those "cosmetic item category pages" (Equipment, Custom Courier, etc) would need to have the Dota 2 Store nav template replaced with a different template, probably a navbox that just listed the categories themselves. --Kroocsiogsi 00:06, 18 August 2012 (UTC)


 * I have implemented preliminary rarity coloring. I can't decide if it's too visible or not visible enough. :-| --Kroocsiogsi 05:42, 18 August 2012 (UTC)


 * Localization is not very big problem. Faraday  08:33, 18 August 2012 (UTC)


 * Right. None of these are very big problems. --Kroocsiogsi 17:27, 18 August 2012 (UTC)

Nvidia 3D Vision Fix
I found a fix for 3D Vision gaming:

search google for "helixmod blogspot" check the gamelist to find the Dota2 fix.

Fixed: Scaling based on convergence: Name Plates/health bars Scaling based on convergence: Hud

Removed: All shadows(Set shadows to low in-game settings. Then it will disable from there) All bad glowing effects(Disable all the effects in settings. Then click vysnc off then click apply)

Issues aware of: Blood is still 2d. Hud breaks at higher convergence settings.

Before you try this please read this WARNING. No ones been banned for playing a game online using a fix but it MAY happen. Thanks goes to FudgePack for the account. Game looks either great or good depending on preferences. Can easily play at max depth and you can move convergence up till the point where health/mana bars are off or your own preference. Character names will remain attached to character models regardless of depth/convergence setting.

have fun!

Organized Equipment Tables v2.0
Updated Equipment Tables to sort Equip Slot and added quality items. Tell me what else you can do or fix.


 * Make it horizontal not vertical. Because when the heroes can more and more items the Table will be getting to long. -Blutsense 07:23, 20 August 2012 (UTC)


 * I quite like the rarity borders around the items, but I concur with Blutsense. Make the items horizontal, not vertical. On top of that, Axe's shoulder pieces are all considered armor pieces. The shoulder slot has no cosmetic items. - Hef aistus  10:40, 20 August 2012 (UTC)

Step-by-step instructions for newly released items would be good
I have an idea for somebody who understands the cosmetic item section better than I do: document the steps that need to be taken when new items are released. What pages need to be created, what dictionary pages edited, what images uploaded, what redirects created, what names should be used, etc. --Kroocsiogsi 19:21, 21 August 2012 (UTC)
 * I spent 5 hours doing this last week. It's very tedious and only works well if WindBOT decides to cooperate. I'd prefer if we got a bot that either periodically or on command scraped the API and did all the work for us. Creating the pages and uploading the images and whatnot. -- Nickoladze 21:50, 21 August 2012 (UTC)