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)

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)

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? Medok10 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)
 * Comment. 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)
 * Comment. 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)