|Manual of Style Homepage|
|Comics (Comic Hubs)|
|Abilities / Powers|
|Merchants / Stores|
Here at the wiki we strive to present information about our topics as accurately as we can, citing only from the most reliable sources. This oftentimes presents problems in that while we know certain things about the franchise have occurred we still need them explicitly spelled out in order to avoid ambiguity.
Please note that everything in this section is not by any means an exhaustive or even definitive list but should provide an idea on what is or is not acceptable.
Valid Sources Edit
- The games, the novels, the films, and other official tie-in materials. External sourcing is needed only to prove a point but if said point is readily accessible to anyone with a copy of the relevant medium it's unnecessary.
- Example: If trying to link Maya Brooks' alleged voice actress, her name must be at least present in the game's credits in addition to any confirmed BioWare source stating the fact outright or at least namedropping one of her social media accounts where the claim is explicit.
- Ancillary sites set up by BioWare for their projects.
- Bug confirmation/disputed information is another matter: it still requires at least 3 users as per policy regardless of external sources UNLESS Word of God intervenes below.
- The BioWare Blog
- BioWare Twitter
- Mass Effect Twitter
- Mass Effect Facebook
- Mass Effect Pinterest
- Mass Effect 3
- List of publications not known to be incorrect when it comes to Mass Effect-related news goes under here.
- List of confirmed social media accounts goes here, with names added and deleted depending on their current involvement with BioWare. Note that twitter accounts verified by twitter itself (blue ribbon beside the handle) are also considered confirmed. At the absolute minimum, the main players.
- Michael Gamble - Producer
- Ian Frazier - Mass Effect: Andromeda Lead Designer
- Fernando Melo - Producer
- Billy Buskell - Multiplayer Producer
- Corey Gaspur - Lead Gameplay Designer
- Dave Feltham - Senior Designer.
- Aaryn Flynn - General Manager of BioWare Edmonton and Montreal, confirmed by Jo Berry.
- Yanick Roy - Studio Director of BioWare Montreal
- Jos Hendriks - Designer.
- Sharon Price - Development Manager
- Jessica Hara Campbell - Level Designer
- Eric Bellefeuille - Lead UX
- Chris Wynn - Senior Development Director
- Joel MacMillan - Art Director
- Fabrice Condominas - Producer
- Nick Sadler - Technical Artist
- Graham Scott - Senior Level/Tech Designer
- Sarah Beck - Programmer
- Lee Kaburis - Development Director
- Voice Actors
- Mark Meer
- Jennifer Hale
- Grey DeLisle - confirmed by a fan asking. It should be noted that the original link is dead, the info found there at the time was deemed legitimate, and all other in-Facebook sources referencing the old address redirect to the current one, as shown here and here. Those are automatic redirects made by Facebook servers, not manipulations by any third party.
- Sumalee Montano
- Raphael Sbarge
- Ali Hillis
- Courtenay Taylor
- Nick Boulton - see here.
Conditionally Valid Sources Edit
Note: Before citing from the prescribed valid sources please make sure to countercheck against the following below.
- Previous BioWare employees. Normally they speak out with canon power only within their respective areas of expertise, so please take anything they say with a grain of salt.
- Example: If Chris L'Etoile, former Mass Effect and Mass Effect 2 writer, talks about behind-the-scenes matters pertaining to the first 2 games, it's valid and counts as devconfirmation.
- Casey Hudson - former Executive Producer
- Dusty Everman - former Senior Level Designer
- Pronouncements by confirmed sources related to the franchise but not directly related to their line of involvement. This employs the same reasoning as above. Voice actor involvement, especially the one-offs, is usually just limited to their characters so we shouldn't be expecting gameplay-related news or the like from them unless there's a very compelling reason to do so.
- Technical data discovered within the game files. The problem with data mining is that they're subject to individual interpretation, and that the stated numbers may conflict with what is actually experienced in-game. This data is subject to the conditions below.
- An online discussion strictly related to gameplay mechanics (not lore or canon) that has at least two of the following three requirements:
- Is supported by in-game testing with explicit numbers and test parameters (must be quantitative and measurable, not anecdotal/qualitative test data).
- Uses a related foundation of explicitly devconfirmed mechanics data (or trivially derived conclusions); extra plus if it uses devconfirmed methodology1.
- Is corroborated with game data files.
- If #1 is not met, then the discussion must be virtually self-evident from #2 and #3 (such as being trivially verifiable). In addition, the discussion must fulfill all of the following:
- Must be clear that the discussion is inclusive of past discussions if necessary; i.e. if there have been three increasingly more accurate discussions and test about a mechanic, don't source the first one.
- There must be general consensus in the follow-up discussion; i.e. test data that is directly contradicted by all follow up posts is most likely flawed.
- The discussion must be a reasonably high-trafficked thread; i.e. a post that has test data but no follow-up peer analysis has likely not had a chance to be verified.
- In addition, the emphasis on conditionally valid source means that if the edit being supported by this source is challenged by another editor, then explicit verification is necessary—whether by trivial "makes sense" gameplay or by actual re-running of tests, depending on the complicatedness of the test data or the controversiality of the edit—by three wiki editors.
- Furthermore, any mechanics discussion related to probabilistic or statistical analysis cannot be conditionally valid, as no one player (or even a group of players) can possibly provide a statistically significant sample size to state anything definitive about the odds of something happening unless explicitly devconfirmed otherwise.
- 1Note: The only devconfirmed methodology is direct memory scanning using external tools.
Invalid Sources Edit
- Wikipedia. Wikipedia presents general facts, the Mass Effect Wiki is for specialized information. It is only fitting and logical we cite from the actual sources pertaining to the franchise, not from any other third-hand party that cites sources both approved and unapproved by this wiki - which Wikipedia undoubtedly does.
- IMDb. Like this wiki and Wikipedia in that anyone can edit their pages, but with less stringent methods of acceptance (if there's actually any). Although if, for example, we are citing voice actors with legitimate confirmation sources it's acceptable to provide IMDb links to the Mass Effect characters that they voiced ONLY IF they do not have articles on Wikipedia.
- Private messages. Anyone can say they PM'ed a dev over so-and-so, even provide screenshots to back it up, but the problem is that the data is not independently verifiable. Not to mention anyone can doctor photographic "evidence" nowadays. Therefore, we highly encourage people wishing to pursue such avenues of correspondence to convince the concerned developer/s to post the relevant information on a publicly-viewable medium: BSN forums under BioWare-certified usernames, their valid Twitters, and so on.
- Unconfirmed sources. By this, it means those unlisted in the valid sources.
Criteria for Confirming Unconfirmed Sources Edit
- A confirmed source linking to the unconfirmed source in a post concerning unconfirmed source's role in the franchise.
- Hypothetical example: MEOfficial Twitter: @anthonyskordi voiced Leviathan.
- Real example: The way Patrick Weekes' work Twitter account was confirmed for the purposes of this wiki, above in the valid sources.
- In case of video evidence, the personalities involved should be shown stating or doing in no uncertain terms the things they were cited with.
- In case of unconfirmed source confirmation, add them to the list of valid sources with a note describing how and why.
Furthermore, we ask people that if they're trying to add unconfirmed sources, confirmation in accordance with the guidelines above falls under their responsibility, not others. There may be those who are willing to do some e-detective work in collaboration but there's no escaping the fact that people can be busy on other pursuits and may not be able to help all the time.
Consult the General Manual of Style for help in setting up reference sections when needed, or just look at any other similar article's source code to see how they are set up.
Lastly, a general rule of thumb to follow instead of reading everything above: Mass Effect Wiki likes devconfirmation.
- ↑ 1.0 1.1 1.2 1.3 1.4 Introducing Some Dev Team Leads for the Next Mass Effect
- ↑ Wikia staff blog post
- ↑ https://twitter.com/DaveFeltham/status/398487966135230464
- ↑ https://twitter.com/bioware/status/662722613626605569
- ↑ https://twitter.com/bioware/status/662360193020403713
- ↑ https://twitter.com/bioware/status/661621640061521920
- ↑ https://twitter.com/tibermoon/status/805450836981714944
- ↑ https://twitter.com/#!/masseffect/status/184768294258098177
- ↑ https://twitter.com/PatrickWeekes/status/268938761205858305
- ↑ BLOG: From Fan to Developer
- ↑ Interview with Writer Sylvia Feketekuty
- ↑ https://twitter.com/GambleMike/status/827379024326332419
- ↑ BLOG: Sam Hulick
- ↑ https://twitter.com/SamHulick/statuses/310123022713503745
- ↑ https://twitter.com/suemolly/status/273991299252768768
- ↑ 16.0 16.1 https://twitter.com/davidgaider/status/380154740853587969
- ↑ BioWare BLOG: I’m Sad That Hanar Can’t Wear Sweaters
- ↑ https://twitter.com/bioware/status/241979757552615425
- ↑ BLOG: Dusty Everman
- ↑ https://twitter.com/DustyEverman/status/836757863976488960