Board Thread:Wiki discussions and announcements/@comment-3308937-20140828121932/@comment-658634-20140908002242

Emptylord wrote: No-one cares about their base stats at level 18, because no-one sees their base stats at level 18 (owing to buying items). The only times people might care about their base stats is levels 1 to their first shop. I care and I know many others care also as they go check it from the List_of_champions%27_health. Can you tell me how stats that are never seen by the player displayed at each champion page serving the reader in any way? Level 18 is seen seldom by players and their numbers do interest for those that dont buy mana or health. Like those playing a mage or a tank. Emptylord wrote: If you want this feature you're going to have to invest in creating the javascript yourself, or pestering someone who knows how - because I am the wrong person to be flaming. This also a largely irrelevant place to complain about it. I am not flaming nor pointing out you should do it. I am discussing about the topic and about the ideas suggested under the topic. Emptylord wrote: Telling players that Azir's must rank Arise! first is not Arise-specific details (since it's also "You cannot rank Shifting at level 1." and "You cannot rank Conquering at level 1."). Sure sounds like its Arise! specific detail if it needs to be taken first. Emptylord wrote: Most abilities that summon pets do something as well. Yes, future emphasizing the point that the information about the pet should be represented closely to the ability, not as its own section after all the abilities. Emptylord wrote: I do not know how to create mobile-specific alterations to the layout. You don’t need to know as it is done by wikia if the site follows the new layout suggestions and formations. e.g. most fixed width things break it, also usually everything that forces certain layout like no breaks. Emptylord wrote: I think you're confusing a database for an encyclopaedia. Admitedly I don't fully disagree with you, but it is not necessary to create a unique page for every piece of information (particularly if you don't need to categorize it).. I dont get your database metaphor. Especially as MediaWiki’s (the software that makes a wiki) run on databases and having an article per subject is not a database, not even in a long shot. Then again wiki is a database of collaborative information. I fail to see what should not be categorized. By having abilities as their separate articles we could have dynamic list of all abilities that produce stuns, griefing wounds and so on. There is nothing to lose and lot to gain by having own articles for each topic. Just as having own article for each skin so you can put all sounds and stuff to that one skins page and no need for other hassle.

Emptylord wrote: I initially planned to do this (having Trivia at the bottom of each article sans gameplay). However, there is a "trivia community" and I veto'd splitting trivia simply "for the readers". I think you misread what I said. Trivia around the article is nice but it would be nice to read it where it is related like that champion is called bob and it is named after the designer bob. Not having a whole section somewhere in end of the article that says it or in separate article. In the otherhand, I really don’t see point for writing those movie quotes or speculations. ‘In the movie Kissalanpojat VII they say ‘DIE!’ and thus it most likely a reference to Aatrox critical attack animation.’ this is my feeling about the general level of those reference euthanastics. Emptylord wrote: Not really. I would still need to find somewhere relevant to put the list the skin-links. Also, as above, I'm not interested in splitting trivia across a dozen pages (per champion). As said before, having the link to the skin article e.g. on the slide show of the skins. Spreading same trivia across dozen pages is indeed bad idea, thats why I suggested including all the related trivia in the article e.g. That skins voice overs, pictures, prices and so on that skins article page, not on the champions page as it is not related there.