Wiki Guidelines

From Degrees of Lewdity Wiki

This wiki guide contains the rules and guidelines for the wiki. It is best to read these before making any edits or contributions.

The wiki's moderators are listed here: Wiki Administrators

A full list of the various categories can be seen here: Special:Categories

If you're having trouble looking for a specific event/character/anything else, use the Search bar at the top-right corner, or otherwise search by Categories.

Enjoy your time on the Degrees of Lewdity wiki!

Rules

The rules here are fairly straightforward. We appreciate all the help we can get.

  • This is a community-run wiki. Anyone is free to contribute. Do not feel pressured into contributing.
  • It goes without saying, but rude behaviour towards others is not accepted.
  • No vandalism of any kind. This includes removing information or adding irrelevant content. Check General Guidelines for more information.
  • "Separate fanon from canon."
    • Fan interpretations are merely headcanons, and do not reflect what is official. Do not add fanon in trivia sections, for example - this will be removed.
    • For instance, named NPCs such as Robin do not have a canon appearance. Other NPCs may have descriptions in-game about them, such as Whitney. Both NPCs can be both male or female - there is no canon choice of an NPC being a specific sex, to leave things up to the player's own interpretation. Refer to them as "they" rather than specific sexes.
    • However, fanart is accepted as there will be fan-art galleries dedicated to an NPC, to spice up the page as NPCs are only represented within the game as combat silhouettes - they will not have a set appearance visualized, only described. Statements such as "A popular fan interpretation is.." and so on are also allowed.
    • Try to provide official sources for certain canon, such as developer comments on transformations and key events. This is to avoid dismissive comments of what is described on the wiki as simply being "head canon".
  • Questions about the wiki can be asked in either the Official Discord in #wiki-discussion, or through direct messaging to the wiki's moderators.

General Guidelines

Here is a list of guidelines for those who wish to contribute. While you do not need to follow these to a tee, it's heavily advised to stick to the guidelines wherever possible.

DO
  1. First and foremost, just like the game itself we use British English. You do not need to know the difference between American and British English to edit at all, do not feel discouraged. Writing in American English is considered as perfectly acceptable. Small or large edits made to "correct" the language to American English are generally unnecessary. However, a reference is provided if you do wish to write in British English: https://www.spellzone.com/blog/Sixty_American_English_Words_and_their_British_English_Counterparts.htm
  2. When detailing events, make sure you write in third person. For example, instead of "You enter the building", it becomes "The player enters the building".
  3. Creating new pages is allowed, but make sure it has content first. Creating new categories is also allowed, but please do not go overboard with it.
  4. While cursing is allowed on pages, ensure that it's either included in event transcripts or included in speech marks to indicate it was said by an NPC.
  5. Update out-of-date information about the game on certain pages. This is a MUST. Ideally we want the wiki's content to be accurate with the most recent version of the game, and have the wiki have as much information as humanly possible.
  6. Add a quick reason to what you edited. While you do not have to do this every time (especially for minor edits) it would be recommended to do so for larger edits like adding new events to pages, or reformatting older pages.
  7. Mark articles as a stub if they are incomplete for convenience.
DO NOT
  1. Refer to the use of cheats. These are optional, and are not the recommended way of playing. Write an article as if the reader is playing casually without the use of cheats.
  2. Submit pages irrelevant to the wiki. Keep things on topic and about Degrees of Lewdity, please. Do not submit empty pages either.
  3. Type in all-caps on pages. Keep things looking professional. Use italics, bold text, underlining or any other way of text formatting however you want, just use it in moderation.
  4. Remove information. Grammar/typo fixes are perfectly acceptable, however. Adding information is always encouraged.
  5. Hyperlink to another page after you have already linked it previously within the same page. Some special exceptions may include pages like the Feats page, however. This guideline is considered more a tip than an actual guideline to follow, but please do keep it in mind.

Page Guidelines

Pages must follow a specific format. More details listed below.

NPC Format

  1. Description: A canon description of the character - i.e. Whitney is described as having blonde hair over one eye.
  2. First Meeting: An NPC's first initial encounter with the player.
  3. Schedule: The NPC's schedule. Robin's lemonade stand, where they can be encountered etc. For People of Interest, include Love stat etc.
  4. Relationship: Any specific stats they have? Dominance for Whitney, Jealousy for Kylar etc. If they do not have specific stats tied to them, how do they behave towards the player? Can the player influence their relationship?
  5. Personality: How does the NPC act towards others? What are their interests? What words can you use to describe the NPC?
  6. Walkthrough: Details the NPC's events beyond the first meeting, as well as any potential quests they have. Serves as an overall collection of events/questlines regarding the NPC and their interactions with the player character.
  7. Unlockables: Primarily used for any possible feats to be obtained with a specific NPC, such as virginity-related or Social feats.
    • Include a table structure for the feat, as the respective page handles it.
    • "There are X feats associated with <this NPC>, these are..."
  8. Trivia: Interesting facts about the character, community speculation etc.
  9. Gallery - Images of the NPC. Use fan-art people have made.

Example Pages: Sam, Bailey

Categories: Love Interests, People of Interest, Unlockable NPCs, Named NPCs.

Location Format

  1. Description: A canon description of the area.
  2. How to Enter: How can the player access this area?
  3. First Steps: The player's first time entering the area.
  4. Notes: Anything to note? What is the area like?
  5. People of Interest: Who works/lives here? i.e. Robin for Orphanage
  6. Walkthrough: How can the player navigate around the location? Anything to consider?
  7. Unlockables: Any items (i.e. pepper spray) to be obtained here? What about feats?
    • Include a table structure for the feat, as the respective page handles it.
    • "There are X feats associated with this location/area, these are..."
    • "There are several items to be obtained here, these are..."
  8. Trivia: Interesting facts about the location, community speculation etc.
  9. Gallery: Images of the location. Use fan-art people have made.

Example Pages: Brothel, Monster's Lair

Categories: Town Locations, Town Outskirts, Contains Places of Interest, Places of Interest.

Quest Format

  1. Synopsis: What is the quest about? Give a brief description of what the quest entails.
  2. Prerequisites: What does the player need to do to get the quest in the first place?
  3. Walkthrough: Is there a good method of getting through the quest, for instance? What are the steps required to complete the quest?
  4. Reward(s): What rewards does the player get from completing the quest?
  5. Trivia: Any interesting facts and/or community speculation about the quest?

Example pages: Blackmailing Leighton, Blood Moon

Categories: Quests, Hidden Quests.

Item Format

  1. Description: A description of what the item is. Use the in-game description of the item.
  2. Use(s): What can the item be used for? Any specific purposes such as quests?
  3. Locations: Where can the item be found?
  4. Value: How much is the item worth? Include buy and sell prices.
  5. Trivia: Any interesting facts and/or community speculation about the item?

Example pages: Pepper Spray

Categories: Items, Clothing, Accessories.

Toggle Format

  1. Requirements: What the toggle requires in order to access the content.
  2. Description: An overall description of what a toggle does, and how they behave.
  3. Locations: Where can the content within the toggle be found?
  4. Walkthrough: How can the player escape or deal with the encounter?
  5. Unlockables: Does the toggle have a unique trait tied to it? Items? Feats? If not, do not include this section.
    • Include a table structure for the feat, as the respective page handles it.
    • "There are X feats associated with this toggle, these are..."
    • "There are several items to be obtained via this toggle, these are..."
  6. Trivia: Any interesting facts and/or community speculation about the toggle?

Example pages: Beasts, Swarms

Categories: Parasites, Beasts etc.

Mechanics Format

  1. Overview: What the mechanic is about, and how it works.
  2. Prerequisites: Any possible requirements the player has to do first? If not, do not include this section.
  3. Locations: Where can the content for the mechanic be found?
  4. Walkthrough: What does the mechanic involve? Any tips?
    • Mechanic Types: Mechanics may have several types the player can encounter, but still fall under the same overall mechanic.
    • Where to Find/Mechanics List: Where can the content for the mechanic be found?
  5. Effects: Any effects the mechanic may have on the player? Stat-wise, or story-wise?
  6. Unlockables: Primarily used for any possible feats to be obtained with a specific mechanic. Further more, any unique traits? Items? If not, do not include this section.
    • Include a table structure for the feat, as the respective page handles it.
    • "There are X feats associated with this mechanic, these are..."
  7. Trivia: Any interesting facts and/or community speculation about the mechanic?

Example pages: Virginities, Machines

Categories: Gameplay Mechanics

Beast Format

  1. Requirements: What toggle/actions are required in order to access the beast content.
  2. Description: An overall description of what the beast does, and how they behave in combat.
  3. Locations: Where can the beast be found?
  4. Walkthrough: How can the player escape or deal with the beast encounter?
  5. Unlockables: Primarily used for any possible feats to be obtained with a specific beast. Further more, any unique traits? Items? If not, do not include this section.
    • Include a table structure for the feat, as the respective page handles it.
    • "There are X feats associated with this beast, these are..."
  6. Trivia: Any interesting facts and/or community speculation about the beast?

Example pages: Canines, Felines, Wasps

Categories: Beasts

Transformation Format

  1. Identity: How does the toggle vary depending on the player's gender?
  2. Traits: What are the transformation details listed in the "Traits" tab?
  3. Requirements: What is required to obtain the transformation?
  4. Progress: How much progress does the player have to make to achieve the transformation?
    • Make sure to include how many transformation points are required to obtain the TF.
    • Include how long the transformation will take from day one of the transformation, to the final stage.
    • Include a summary overview of the transformation, separated by stages of interest - typically, there are six stages. Stages 2, 4 and 6 are the most important.
    • List in order by how it is written in-game, for example:
      • "Despite everything, you have managed to remain a pure boy/girl/hermaphrodite. The thought makes you happy."
      • "You are pure and feel determined to keep it that way."
      • And so on.
  5. Effects: What effect does the transformation have on the player?
    • Include "Positive" and "Negative" sections.
    • Visual differences on the player sprite will also go here.
    • Other gameplay changes will go here as well.
  6. Unlockables: Any unique events tied to this transformation? Items? Feats?
    • Include a table structure for the feat, as the respective page handles it.
    • "There are X feats associated with this location/area, these are..."
    • "There are several items to be obtained here, these are..."
  7. Trivia: Any interesting facts and/or community speculation about the transformation?

Infobox Formatting

When formatting infoboxes, be sure to follow this format wherever possible.

Named NPC infobox format

  1. Name: Self-explanatory. The name of the character.
  2. Species: Human or non-human?
  3. Appearance: What the character looks like. For instance, Jordan has golden hair and blue eyes.
  4. Personality: How does the character behave? (i.e. Robin = Innocent, Kylar = Obsessed)
  5. Occupation: What job does this NPC have? (if they have none, use Role instead. Role = Robin: Player's Friend, Kylar: Stalker etc.)
  6. Relationship: How well is their relationship with the player? (If they have a love stat, use "Determinant on Love")
  7. Interests/Hobbies: What are they most often seen doing? (Robin has gaming, Kylar has the player for instance)

Example Pages: Bailey, Mason

Location infobox format

  1. Name: The name of the location.
  2. Description: How the location is described.
  3. Opening Hours: How long is the building open for? i.e 6AM-9PM
  4. Role: What purpose does the building serve? (Skulduggery? Dancing? Swimming? Safehouse?)
  5. Owner: Who is in charge of the location?
  6. Inhabitants: Who resides at the location?

Example Pages: Orphanage

Gallery Formatting

When formatting fan-art galleries, be sure to use this disclaimer before the gallery itself:

NPC: "The following images showcased below are fan interpretations of what this character looks like in-game. Despite canon descriptions existing within the game itself, visual depictions of the character akin to the player sprite are best left to the player's own interpretation."

Location: "The following images showcased below are fan interpretations of what this character looks like in-game. Despite canon descriptions existing within the game itself, visual depictions of the location akin to the location sidebar art are best left to the player's own interpretation, for the most part."

Templates

Use Templates wherever necessary when detailing things such as specific events - give colors to positive/negative effects, required stats, required ranks/grades and more.

How to use:

  • In source editor, write the following syntax
  • In visual editor, write {{. This will open up a menu. Choose the required template. It will then ask for a Field name<nowiki> - enter 1. Now you can write the desired text into the field and when happy, click "Insert"

In this case, the appropriate colour is automatically applied to the effect.

Colour Templates

Here's a list of every colour template there is as of now:

  • Positive (used for e.g. -Trauma or +Athletics)
  • Negative (used for e.g. +Trauma or +Pain)
  • Boost (used for e.g. cash or unlock prompts)
  • Stat1 (used for Lewdity Stats, e.g. Exhibitionism 1)
  • Stat2
  • Stat3
  • Stat4
  • Stat5
  • RankF (used for all kinds of skill, e.g. Skulduggery F or Science F).
  • RankD
  • RankC
  • RankB
  • RankA
  • RankS
  • Meek (used for every meek action)
  • Sub (used for every submissive action)
  • Brat (used for every bratty action)
  • Def (used for every defiant action)
  • State (primarily used for the Fallen Angel transformation)

Please note that there is no rank E, and + Ranks share the same colour as normal ranks.

Collapsible Text

This can be done to hide parts of articles with detail unnecessary for most readers, which makes the page feel too complex and cluttered. A good example of this is a list of all possible events related to a certain place/stat.

The following code must be added in the source editor (the visual editor interprets it as text):

<div class="mw-collapsible mw-collapsed mw-collapsible-heading-style">
    <div> VISIBLE PART </div>
    <div class="mw-collapsible-content mw-collapsible-content-style"> HIDDEN PART </div>
</div>

Note that the "VISIBLE PART" should be kept relatively short - a few words at most and that while it can contain a list, the visible part itself cannot be one. The result:

VISIBLE PART
HIDDEN PART

In order to make it not initially collapsed, the class "mw-collapsed" from the first div should be removed.