Disco Elysium Wiki
Advertisement
Disco Elysium Wiki

The purpose of this manual is to create guidelines to help keep content more uniform across all articles on the Disco Elysium wiki. All formatting described here is a guideline and may be overridden in circumstances where it is warranted.

These guidelines will never be unerringly perfect for every situation. However, please try your best to keep to the advice outlined in this article so others may use your edits as an example when creating and editing their own articles. Everything covered on this page has been put in place in order to maintain a sense of reliability and cohesiveness while keeping best practices in mind.

General[]

Preferred Terminology and Language[]

  • Although Disco Elysium is written in second-person perspective, and its protagonist, Harrier Du Bois is primarily referred to as "You", "Detective", or "Officer", this wiki uses "Harry" or his full name when describing any actions taken by the player. With very few exceptions, relatively minor spoilers of this nature are not a concern.
  • For the most part, Oxford spelling is to be used on the Disco Elysium wiki, however, as Disco Elysium uses an inconsistent version of Oxford within its script, this may be superseded depending on the specifics of the game's dialogue.
    • As an example, the shortened variant of the word "mother" may be written as both "mum" and "mom" within the same conversation;[1] direct quotations should always be written as they are seen in-game, rather than corrected to follow Oxford spelling.
    • The dialogue browser, FAYDE, may be used in cases where both UK and US spellings are used in-game, as the word(s) may be searched to see which version is used more frequently. If the word cannot be found within the script, default to Oxford English for the wiki.
    • "Epilogue",[2] "Monologue",[3] "Dialogue"[4] etc. should be preferred over "Epilog", "Monolog", "Dialog".
    • While the British word "lorry" is preferred in-game, the North American "elevator" is also used over the more common British "lift". Usage on the wiki should be decided on a case-by-case basis by searching for any occurrences of the word in the game's script using FAYDE.
    • The Communist vision quest, as well as several other added scenes from The Final Cut are most inconsistent with the original release's UK English script, as they were written by US-based writers and thus use unrevised US English.
  • Try to keep articles formal. Avoid the usage of slang, as well as any conversational or casual language. Sentences must be structured in a way that is clear and unambiguous. Avoid unnecessary verbosity. This wiki should use simple language and sentence structure for the sake of all readers. Language should not be too vague, and sentences should not be too long.
  • Stick to facts; speculation has no place on an encyclopedic wiki, and there should be room for readers to come to their own conclusions. Editors should aim to recount events, rather than suggest answers.
    • This means that the wiki does not have room for walkthroughs, guides that recommend internalizing specific thoughts, using specific gear, or otherwise suggest that there is a "proper" way to play the game.
  • DO NOT under any circumstances copy and paste text from other sources. This is most important when dealing with guides/walkthroughs, coverage of tasks, or other gameplay mechanics; this is plagiarism and will not be tolerated. We also do not give credit to specific users; please do not cite external links to Reddit, GameFAQs, or credit users from similar sites. Please use your own words and research, and be sure to double-check the validity using FAYDE or Disco Reader to view variables.

Writing[]

Keep your writing concise. Don't use two words where one will do. Keeping your writing simple will make it easy to understand and easy to expand on. Use complete sentences whenever possible. Avoid play-by-plays for game recaps; leave out inconsequential details whenever possible.
Check your spelling and grammar. Do not use 'u' in place of 'you' or '2' in place of 'to'. Write the way you would for a class paper or a newspaper article. If English is not your first language, an admin or another active editor should be able to help polish up any edits for you; keeping an eye on edit summaries after this occurs may be helpful for the future.
Keep all of the topics you cover within the scope of the article. Consider the article's title as your point of origin and write from that perspective. Make use of the wiki's ability to link to more detailed articles or external sources for more information. Avoid delving too deep into other characters stories or plot details that do not relate to the article you are writing for.
Don't be afraid to make changes. If you know something is wrong, correct it. If you think you could word something better, rewrite it. If an article has a glaring deficiency, fill it. Even if your first attempt isn't golden, you can fix it later or someone else will come along and fix it for you. Don't be afraid to screw up.
That being said...
Don't take it personally. This is a community wiki, and there are bound to be discrepancies between authors. Come to agreements amicably, don't play wiki ping-pong with others.

Criteria for Creation[]

When creating an article, be sure that the topic you intend to cover has not already been covered under a different name, on a compound page (such as Characters, which catalogues all background characters that do not need their own articles) and is significant enough to warrant an article. If your article is deleted, it may be due to a multitude of reasons, including inappropriate title, duplicated page, irrelevancy to the central wiki topic, or permastub (permanently a stub) status. If you believe your deleted article qualifies and may have been deleted in error, contact an Administrator.

Article Layout[]

Due to the nature of the wiki, it is impossible to always have the perfect layout for each situation. However, for each different type of page, it is recommended that these specifics be followed as closely as possible.

Lead Section[]

The lead section for each article should aim to summarize the basics of what follows. The lead should not be explicitly titled as Introduction or any equivalent header.

The lead should be able to stand alone as a concise overview of the article, establish context, and explain why the subject is interesting or notable. It should be between one or two paragraphs long, and should be written in a clear and accessible style so that the reader is encouraged to read the rest of the article.

The title of the article and any variations that it is commonly known as (in-game, not in the fandom) should always be bolded and included in the first sentence. For a character article, this usually means that their legal name is followed by their in-game title.

For example:

Lilienne Carter, also known as Lilienne, the Net Picker, is a character in Disco Elysium.

Roustame Diodore, also known as Mega Rich Light-Bending Guy, is a character in Disco Elysium.

For any non-character articles, it may instead be written similarly to the following:

The Greater Revachol Industrial Harbour, commonly abbreviated as GRIH, is a location in Disco Elysium.

Section Headings[]

Use the == (two equal signs) style markup for main headings, equivalent to <h2>. Do not use a single =. This is because a single = creates an <h1> heading which is already used by the page header and leads to issues with the page's code.

Use title case, and capitalize the letter of each word found in the section heading (aside from "on", "in", "and", etc.).

Do not use [[Wiki Links]] in subject headings. When edited, these sections become confusing in the edit history due to the link code. Instead, link to the subject within the section text itself. Additionally, avoid other special characters in headings such as an ampersand (&), or plus sign (+). In place of the ampersand, use the word "and", unless the ampersand is part of a formal name.

Always keep headings short and simple. Headings are guidelines to the page's structure and should inform the reader rather than confuse. Avoid unnecessary words or redundancy in headings.

Trivia[]

  • The == Trivia == section on each page should ideally be filled with relevant, factual, and interesting information.
  • If a piece of trivia would fit into a previous section of the article without breaking the flow of the text, it should be incorporated there instead. 
  • If a piece of trivia is speculative it should not be included.
  • Remarks made on twitter or forums by the development team and/or employees of ZA/UM (current or former) must be sourced.

Character Article[]

The ideal layout for a character article is a short lead section, followed by headings for Background, Involvement, Trivia, Behind the Scenes and Gallery, followed by Checks/Notes/References where applicable.

Background[]

  • The == Background == section should recount notable events in the character's life prior to their earliest involvement in the game.
    • Background sections should be written in the past tense.
    • Further subheadings may be used for any notable events, such as Kim Kitsuragi's === RCM Career === if the gap between events is significant enough and there is enough information to justify it. If a section contains only one or two paragraphs, separate subheadings are not needed.
    • If the page features a character whose background is not known, this section may be omitted from their page.

Involvement[]

  • The == Involvement == section should recount the character's involvement as close to chronological order as possible (though this may be understandably difficult to achieve due to the relatively non-linear nature of the game).
    • Involvement sections should be written in the present tense.
    • Information should remain relatively concise and only relay information that relates to the specific character (i.e. an unrelated character's title, background, etc. should be kept to their own page).
    • A character should be mentioned by name (and linked upon their first mention on a page) but not title. For example, when writing Harry's page, it should be, "Harry meets with Kim Kitsuragi," not "Harry meets with Lieutenant Kim Kitsuragi, an officer of the RCM, hailing from the 57th Precinct."
  • Any characters involved in the Mercenary Tribunal should have a separate subheading in their Involvement section detailing the outcome behind a spoiler template.

Behind the Scenes[]

  • The == Behind the Scenes == section may include any pieces of information that are not contained within the game itself, such as pre-release material or unofficial lore.
  • Remarks made on twitter or forums by the development team and/or employees of ZA/UM (current or former) must be sourced.

Additional Sections[]

  • Some major characters, such as Harrier Du Bois and Kim Kitsuragi, may have additional sections, including == Personality ==, however, these are not necessary for each character, and should only be added when sufficient information is available.
    • Personality sections should only make note of observable characteristics that reflect how a character behaves as a whole. Additionally, they should refrain from speculation.
    • Personality sections should maintain a neutral point of view. It is inappropriate to utilize an overly-disparaging or an overly-approving or defensive tone.
    • It is recommended that quotations within the personality section are marked with a citation.

Location Article[]

The ideal layout for a location article is a short lead section, followed by headings for Background, Involvement, Points of Interest, Trivia, and Gallery, followed by Checks/Notes/References where applicable.

  • If the article covers a large area, such as a district, city, etc., a Notable Locations heading may be added above Trivia.
  • Information on location articles should be concise and not give away any major plot details unless absolutely necessary. Information should only discuss relevance of the location in relation to the main plot.

Tasks Article[]

The ideal layout for a tasks article is a short lead section, followed by the direct in-game description under Description, and further expansion under Details, followed by Checks/Notes/References where applicable.

  • Gallery is for the most part unnecessary, as there should already be a serviceable image representing the task in the infobox.

Item Article[]

The ideal layout for a tasks article is a short lead section, followed by the direct in-game description under Description and headings for Uses, Trivia, and Gallery, followed by Checks/Notes/References where applicable.

  • Each item should have an image in the Gallery section showing its in-game location.

Templates[]

Spoiler warnings, stubs, notices, etc. are extremely important tools to utilize, not just for other editors, but readers too. There are several different types of templates that can be found on this wiki.

The most important templates are:

{{Stub}}

This template should be used at the beginning of an article to mark it as a stub.

This article is a stub, and may be missing key information. You can help the Disco Elysium wiki by expanding it.

{{Cleanup}}

This template should be used at the beginning of an article to mark it as being in need of cleanup, as well as warn readers that the content on the page may not be up to standards. While stubs tend to be short and in need of additional information, pages marked with the cleanup notice are in need of editing to remove much of the information.

This article needs cleaning up in order to meet quality standards. You can help the Disco Elysium wiki by editing it.

{{Cite}}

This template should be used in place of a citation when a suitable source to back up claims cannot be located.

For example: "Alice DeMettrie is the daughter of one of the senior officers and has been in the station ever since she was old enough for her dad to take her with. She knows the station, the people in it and the many nooks and crannies of police work."[citation needed]

Spoiler Template[]

{{Spoilers}}

The spoiler warning template requires filling out with what is being spoiled, whether it's a secondary plotline such as tasks, lore from a character's backstory, or the main story. When completed, it should look like this:

{{Spoilers|What is being spoiled}}

SPOILER WARNING: Plot details for the main story follow. (Skip)

At the end of the section, place the {{EndSpoilers}} template. The button to skip the section will not work otherwise.

SPOILERS END HERE. (Return)

Quote Template[]

{{Quote}}

Quotes should be placed beneath the lead section wherever they are most relevant. The template is designed to automatically assign appropriate colours to dialogue based on the speaker's name (such as Authority being coloured purple or Harry's choices being coloured blue-grey).

When inserting a quote that does not contain a skill check, leave the section after the speaker's name blank. Note that it must still include the additional |, otherwise the template will not display correctly.

{{Quote|Limbic System||It was *him*. *He* is the infernal engine. He never stops. He only gets worse.}}

LIMBIC SYSTEM – It was *him*. *He* is the infernal engine. He never stops. He only gets worse.

If the quote contains a skill check, it should be filled out with the correct value, followed by whether it was a Success or Failure.

{{Quote|Authority|Medium: Success|No -- It's your soul, your blue soul.}}

AUTHORITY [Medium: Success] – No -- It's your soul, your blue soul.

Reference Template[]

{{RefD}}

References, also known as citations, are near-identical to the formatting of the Quote Template, but are instead used to replace the standard <ref></ref> reference tags. If a reader should roll over these citations with their mouse on desktop, a box will popup showing the contents, or they may be clicked on directly to be brought down to the References section (both mobile and desktop). References that are placed at the end of a relevant sentence should come after any punctuation.

Unlike the Quote Template, this template is able to contain multiple different speakers, separated by a |. Formatting should stay consistent between speakers, and multiple lines should NOT be combined, rather given their own consecutive speaker's tag instead.

Same speaker: {{RefD|Name of Speaker|Skill Check: Success\Failure (or left blank)|Quote text|Name of Speaker|Skill Check: Success\Failure|Quote text|Name of Speaker|Skill Check: Success\Failure|Quote text}}

Different speakers: {{RefD|Name of Speaker|Skill Check: Success\Failure (or left blank)|Quote text|Name of Next Speaker|Skill Check: Success\Failure|Quote text|Name of Next Speaker|Skill Check: Success\Failure|Quote text}}

Example text: Prior to joining the RCM Harry was a high school gym teacher[5] in Grand Couron.[6]

{{Reflist}}

At the end of a page, under a heading that reads ==References==, place the Reflist template, replacing the standard </ references> reference list tag. A number may be specified to split references into multiple columns ({{Reflist|2}} or {{Reflist|3}}), however, this is not recommended, as it does not display well on mobile devices.

See the Notes and References for more formatting notes and the bottom of this page for an example.

Images[]

File names should be unique and descriptive; avoid using names that may cause conflicts with other files. Instead of simply naming an image "Kim.png", include the character's full name and a short description of what the image is. For example, "Kim Kitsuragi - Unused Model Turnaround.jpg", "Kim Kitsuragi - Unused Model Portrait.jpg" and "Kim Kitsuragi - Unused Model Halfview.jpg". All three of these file names give brief descriptions of what the image displays (different views of the same unused character model) while still being distinct enough.


  • Images should ideally be in lossless .png format, unless an asset found in the game's files, or concept art from the official website are in .jpg format.
    • Do not crop, colour correct, convert or upscale any images. Everything should be taken from official sources and uploaded as-is.
  • The preferred aspect ratio for all in-game screenshots is 16:9, with 1,920 × 1,080 resolution.
    • Any screenshots showing item locations, character locations, or interactable objects should have the subject highlighted with the in-game outline visible (green or yellow depending on whether high Perception is required to see it) as well as the small menu showing its contents (if it is inside a container or is an obtainable item).

Galleries[]

When an article has many images, or can be improved by having more, and having inline images be detract from the readbility of an articles, the use of a <gallery> section is encouraged.

Captions should give a brief description of what the image displays, while retaining a neutral tone in-line with the rest of the article. A caption such as "Concept art of René Arnoux." is preferable to something short like "Art." or something opinionated, such as "Fascist dumbass."

Licensing[]

All files uploaded to the wiki must qualify for one or more of the following licenses and be tagged with the appropriate license. This makes the scope of a given file's use on the wiki clear and makes it known to readers, editors, and creators of derivative works what they can and cannot do with the file.

There is a licensing dropdown menu when uploading an file via Special:Upload which can be used to automatically add a licensing template to an image. A license may also be added or modified after the fact by adding a heading titled ==Licensing== below any other content, then adding the appropriate template below it.

Infoboxes[]

Every page should have an infobox. Infoboxes have been set up to auto-categorize pages so that manually adding [[Category:Characters]] to each character article is no longer necessary; however, this requires that the proper infobox be used on pages. Do not add the {{Infobox character}} to a page that should have {{Infobox item}}, for example. This wiki has for each page type, which can be accessed either by clicking "insert" > "infobox" button in the visual editor, or by typing one of the following into the source editor:

{{Infobox game}} This infobox is used on game pages, such as Disco Elysium.

{{Infobox character}} This infobox should be used on every character page. Examples of a completed character infobox: Harrier Du Bois, Kim Kitsuragi.

{{Infobox location}} This infobox is used on location pages, such as Bird's Nest Roy's or Cuno's shack.

{{Infobox task}} This infobox is used on task summary pages, such as Buy FALN pants from Cuno or Getting the body down.

{{Infobox achievement}} This infobox is used on achievement pages, such as Bother Kim After Hours or Hardie's Heroes.

{{Infobox skill}} This infobox is used on skill pages, such as Esprit de Corps or Savoir Faire.

{{Infobox item}} This infobox is used on item pages, such as Leather Jacket Pissf****t, Icosahedral Dice Set Sirens, Damaged Ledger, Villiers 9mm Pepperbox Pistol, Speed Bottle, From A to Zrieek! A Guide to Cockatoos, and many others.

For specific details on each template's usage and syntax, please refer to the template page itself.

Categories[]

Specific categories should be added to every article - a full list can be found on Special:Categories. The most important ones are Characters, Locations, Skills, etc. Most infoboxes have auto-categorization capabilities, however, if creating a page that does not have an infobox, they must be added manually.

  • When sorting categories, do NOT file articles under "[[Category:Disco Elysium]]". This category is NOT meant for characters, locations, items, etc.

Links and Navigation[]

Redirects[]

If a page is renamed, please leave a redirect with a link to the new page.

#REDIRECT [[PAGE NAME]]

The redirect should be the only text on the page.

Table of Contents[]

A table of contents will automatically appear in articles with a minimum of four headings (unless done manually). By default this will be left-aligned above the first section heading.

  • To the force a TOC position (left-aligned): __TOC__

Notes and References[]

The last sections, if they exist, should always be "See also", followed by "Notes", then "References". In the case of "See also", use bullets to list the internal links. {{Notelist}} should be placed under ==Notes==, while {{Reflist}} should be placed under ==References==. If both exist on a page, they may be separated into a heading called ==Notes and References== with further subheadings ===Notes=== and ===References===.

References[]

  1. YOU – "...all I'm saying is I'm surprised people's skin colour varies so drastically. And that I miss my mum."

    KIM KITSURAGI – "Once again, differences in skin colour are the result of melanin production, liver functions, regional adaptation, and various other factors."

    YOU – "I hope my mom isn't dead..."

  2. HORSEBACK MONUMENT – Wind makes the cardboard omen swing menacingly, like a pendulum ticking down to a dreaded epilogue...

  3. KLAASJE (MISS ORANJE DISCO DANCER) – "Good monologue!" She smiles, flashing her pearl-white teeth.

  4. TUTORIAL AGENT – You've gained a Thought! When this dialogue is over, go to your THOUGHT CABINET and INTERNALIZE it for special bonuses and effects.

  5. KIM KITSURAGI – "I am sure it has. In the time we've spent together, I must have covered 30 kilometres. He has a *track and field* approach to police work."

    INLAND EMPIRE [Easy: Success] – Isn't that odd? How *can* you run so much?

    ENDURANCE [Medium: Success] – Why not? You're a powerhouse.

    PHYSICAL INSTRUMENT [Medium: Success] – It's about DEDICATION, son. That and you're *probably* a gym teacher. Only a former gym teacher can think these thoughts and drink so much.

  6. JEAN VICQUEMARE – "Yes, you *taught gym* in Couron. I believe that's the term? Taught gym at a high school. You were a high school gym teacher."

Advertisement