Why isn't there a page about my favorite team/player/personality?
- There could be a couple reasons:
- This person or team does not meet our notability guidelines. In this case, we won't create a page for them unless they meet those guidelines in the future.
- We don't have enough information about the team or person to make a page for them. If you have info about the team or player, you can make the page yourself! Or, if you know the person or someone on the team, have them contact us and we can give them a survey to fill out; we'll make a page based off that info.
- We overlooked making a page for them. Sorry! If you think this is the case, let us know. Or, you could make it yourself!
This page isn't up-to-date or isn't well-written or is wrong or has another problem. What do I do?
- Again, you can always contact us about a page that needs an edit by contacting us. Or you can update the page yourself! Some pages, like tournament scoreboards or picks and bans, might be a bit confusing to edit. If you're unsure what to do, let us know that you were interested in editing a page but couldn't figure out how to. We're in the process of creating several tutorials to help you out, so we'll try to add one for whatever it is that you couldn't figure out.
- IF THE PAGE IS A MATCH HISTORY OR STATISTICS PAGE AND IS NOT UP-TO-DATE, PLEASE LOG IN AND CLICK "REFRESH" IN THE DROPDOWN MENU TO THE LEFT OF THE SEARCH BAR. This will cause the page to repopulate the data used in the creation of the page. Once you Refresh the page once, it will fix it for everyone else, including people who are logged out. Please attempt this prior to contacting us! If the page is still out-of-date or has some other problem, then of course feel free to reach out and we will look into it!
How do I find a page I'm looking for?
- There's a bunch of different ways to find pages on the wiki!
- Dropdown menus on the front page (useful for navigating to premier-circuit events and teams)
- Featured Leagues on the front page (useful for navigating to current major events and teams)
- Navboxes on individual pages (useful for navigating to other pages of similar types - e.g. other seasons of a league, players on a team, or teammates of a player)
- Tabs across the tops of pages
- Internal search - even though in the past this hasn't necessarily been useful, we're working on making it more useful by creating redirects from frequently-searched terms to the pages they should land on
- The side bar! There are a bunch of useful links under the "Competitive" category.
Why do you list country of birth instead of nationality or country of residence?
- This is probably the most-frequently asked question, and it's a relatively long answer. TL;DR, COB is the best out of a lot of imperfect choices. "Nationality" is what we ideally want to show, but at the same time "nationality" isn't as well-defined as you might want it to be.
- If a player grew up in Korea and moved to the US when he's 9, is he Korean or American? What about when he's 7? Due to the impracticality of directly asking every single player what they consider their nationality to be - and the fact that not every player will be able to answer one way or another - it's impossible to list factually and accurately.
- Even if we could ask every single player individually what they want us to list, that still may not coincide 100% with what you "want" displayed by them. Yes, Huhi obviously "should" have Korea listed and not France, but who knows what the exception might be under this other system (which we couldn't implement anyway due to impracticability).
- So we need to use something that's a stand-in for residency, i.e. a well-defined, factual attribute of a player that has an extremely high correlation with "nationality." There's a couple options that we might use: Country of Birth (COB), Citizenship, and Country of Residence (COR).
- COR is probably the worst one to use as a stand-in for nationality since players will live with their teams in the country where their leagues are held, and even the country that they go home to in the offseason could be different from both the country they were born in, the country they identify with as their nationality, and the country that the public thinks of them as being from. Also this is extremely subject to change.
- Citizenship has the problem of dual citizenship since we only have space to list one flag on roster pages. Also permanent residency is a thing, so we still might not have the perfect correlation that we want. And citizenship can change over time.
- Finally, country of birth. This is extremely easy to define, will never change, and is something that's generally easy to determine frequently without contacting the player directly since team announcements and other tournaments often list it themselves. It's not a perfect correlation with nationality, but it's pretty good, and as of May 2016 there's only one player whom people frequently complain about using COB for (Huhi).
- But Huhi should obviously be Korean, so clearly country of birth is a bad choice
- You haven't seen what the results of another system would be, so unless you've spent hours compiling data about another category and making sure it's all verified factual data, then you can't know what the problems are with another possible option. Anything that we list has foreseeable problems with it, and not only does COB seem to be pretty good overall as an indicator, but also it's our current system, and changing to another option has a pretty high opportunity cost associated with it, where we can't spend that time on other projects.
Why was Origen in the past abbreviated OR instead of OG?
- For technical reasons, we used to be unable to have two teams with the same short name, and we reserved OG for OpTic Gaming in case they ever entered League of Legends. However, we eventually began to use Origen's full name as its short name since 6 characters is short enough for a short tag, so this became irrelevant even prior to the team's disbanding. During OpTic Gaming's tenure in League of Legends, they instead used the abbreviation OPT.
Why do you write KingZone instead of KING-ZONE?
- We tend to standardize capitalization for LCK teams; we also write Kongdoo Monster instead of KONGDOO MONSTER and SK Telecom T1 instead of SK telecom T1, despite the alternate stylings used for these teams on the official LoL Esports site.
Why are your notability guidelines for support staff so strict?
- There's a lot of contributing factors.
- Historically, it has been very difficult to assess the impact support staff had on teams, and in many cases this trend continues. Even after head coaches became a formal part of LCS rosters, there were teams that didn't utilize this position and just had stand-in coaches. And outside of the coach role itself, it's still hard to judge the impact / relevance of other support staff positions. In some teams the support staff are as important as the players, but that's not the case everywhere.
- It's often harder to find data on roster changes related to support staff. Not all teams announce this. Player rosters can be discovered by watching teams play, not so for support staff.
- We are not losing data by not making these pages. We still track support staff changes to the fullest of our ability on team pages. If you wanted to research a particular coach or analyst's career, you could already do so by searching the wiki.
- Support staff don't have relevant stats to attach to their page the same way players do. There's no reason to have a location to keep match history or statistics pages on hand, because this information simply doesn't exist for support staff.
The following three points are related:
- The wiki is not a site for hosting resumes. While this question is frequently asked by support staff, it's extremely rare that I've been approached by fans looking for information about support staff that they're unable to find. This may be a failing of the community as a whole to recognize the importance of support staff, but we try to provide information that's useful to people.
- Our notability guidelines have to be absolute. Doing things on a case-by-case basis leads to unjustifiable inconsistencies. So committing to doing more support staff pages means committing to doing a lot more support staff pages.
- Everything we do has to be weighed by importance. We don't have an infinite number of editors with infinite time. So creating more pages about XYZ will always be at the cost of having pages about ABC.
But why not just let support staff make their own pages? A few reasons.
- This would lead to inconsistencies in who has pages that would seem unfair/illogical to fans.
- Our pages have pretty strict quality standards. We obligate ourselves to keep player pages updated. What would we do if a member of a support staff started a great page but then abandoned it? If we delete it or move it to the user namespace, people might wonder where the page went. (And if no one wonders this, the page wasn't being used in the first place.) And if we continue to maintain it ourselves then we run into the problems discussed above.
- A lot of historical data can be hard to verify. It has happened that a person edits themselves into the history of a team, but when I contact the team we are told they did not actually hold the position they said they did. This issue would only be compounded if we had to verify an entire person's competitive history.
If you want to make a page for yourself, you can still do that in the User namespace. Click here to get to a page that you can create. We do not officially monitor user namespace pages, and we don't link to them from elsewhere within the wiki, but as long as you don't misrepresent your user page as an official wiki page you can feel free to share it. We also don't guarantee technical support for user pages, but if you join our Discord you can ask in the channel
#wiki-help and maybe someone can help.
Who We Are
What's the difference between you and Esportspedia/EsportsWikis?
- Our staff includes both the editing base of the old Leaguepedia wiki as well as that of Esportspedia/EsportsWikis - combined, we are able to cover a lot more events and bring overall a much better wiki! You can read more here.
Whom should I talk to about...?
- Your best bet to get a quick response is to join our Discord. However you can also tweet at us or contact a staff member directly. If you're not sure whom to contact but prefer not to use Discord, you can send River a message or email her at river(dot)esports(at)gmail(dot)com.
I can't edit! What's going on??
- First of all, note that unless you are specifically granted Editor permissions, all of your edits will need to be accepted by a staff member before they go live. This is to reduce spam / vandalism. So if you are able to edit a page and then save it, it's probably working exactly as intended -- just check back in a bit to see if your edit was accepted.
- If you can't even click the "Edit" button, make sure you're logged in. It's also possible (but unlikely) that your IP address has been banned from making edits if someone at your IP was repeatedly making malicious edits. If you suspect this might be the case, please contact us!
I edited the page. Why isn't it showing up?
- As a vandalism counter-measure, we have an approval system for page edits. When you edit a page, you can see the changes yourself, but for your edit to go live for everyone, it must be accepted by a staff member. Once it's accepted, everyone will be able to see it.
Why wasn't my edit accepted?
- First, make sure your edit was actually correct. Maybe you had a typo? If your edit was definitely correct, try resubmitting with an explanation of what you were changing and why in the summary. If you've done that and you've waited at least 24 hours and it's still not accepted, then please contact us. Include your account name and a link to the page you were attempting to edit.
There's a change I need to make, but I can't figure out how. What do I do?
- Check out our page on editing here. There are a lot of MediaWiki tutorials available, and our staff are always willing to help out!
I added a link to an external page, but it's not working. How come?
- Did you add "http://" at the beginning? If not, the link won't work. You can also refer to our tutorial.