Mod:Mods Guidelines

In order to ensure that all pages on the Hollow Knight Wiki follow the same standards of quality, this article details the guidelines for editing articles about Mods.

Please read the Editing Guidelines to learn the basics first!

If this page was confusing or did not answer a specific question, feel free to ask on our Discord!

Mod Qualifications

• Submitted mods must be in a functional, safe state. This means no broken/dangerous mods, and "work-in-progress" mods have to be stable. Texture Swaps must have all textures stated in their description, even if in a rough draft state.
• Anyone adding mods to the wiki must have approval from the mod's creator. Some creators prefer to keep all info consolidated within their own sites or repositories, and we wish to respect them as we would with any other creator.
• Stay within the game's Age Rating. This is more flexible than it may seem at first. See Pegi 7 and ESRB 10+ for examples of content that meets the same rating as Hollow Knight and Silksong.
• No NSFW content. Nudity, obscene profanity, and any gore that exceeds the amount shown in the base game are not allowed.
• No bigoted/hateful content. Any racist, sexist, homophobic, xenophobic, or otherwise bigoted imagery such as slurs, iconography, or phrases will not be allowed, and result in an immediate IP ban from the wiki.
• Submitted mods must follow the Formatting Guidelines as closely as possible
• All mods on the wiki are for PC modding only. (see Legal Requirements below)

Legal Requirements

• Mods will not be hosted on this wiki. Like the main game, the Hollow Knight Wiki is a place for consolidating information, not resources. All mod content must be hosted off-site, and connected to the wiki article with links only.
• Do not provide information about pirating content or modifying a console. While we are aware that both of these realms of accessing content exist, the Hollow Knight Wiki does not endorse any illegal acts or acts that may result in voiding warranties.

Formatting Guidelines

Full Articles vs List Entries

Not every mod needs its own article. If a mod is a tweak to an existing larger mod, consider putting it in a tabled list within that larger mod's main page.

• For example, no Custom Knight skins should have their own page, and should instead go in the tabled lists under Mod:Custom Knight.
  • Do not include any screenshots of the texture swap in the table. A name, description, and link will suffice.
• If the larger mod does not have an article, consider suggesting the article's creation on Discord. It is possible that the mod's creator does not want their mod included on the wiki.

Titles and Links

• All mods must use the Mod: namespace, for example: Mod:Pale Court.
  • Adding a pipe | after the link will allow you to hide the namespace. Example: [[Mod:Pale Court|Pale Court]] becomes Pale Court.
• Separate pages relating to the same mod (for example, a Boss in a Content Pack) must use a subpage under the main mod page. Example: Mod:Pale Court/Mighty Hegemol.
  • To link to this page on the main mod's page, you may use just a forward slash instead of the full namespace and page name
  • To remove the forward slash from the formatting, you may put a second forward slash after the page name.
• DO NOT include links to Mod articles in main articles. This helps ensure a clear distinction between fan content and canon content. You may include links to main articles within mod pages.

Templates and Categories

• Use Template:ModNotif at the top of the mod page. This will help ensure mods are clearly separate from canon content, as well as automatically add Category:Mods to the page. Include additional Categories as appropriate, for example:
  • Category:Mods (Charms)
  • Category:Mods (Installers)
  • Category:Mods (Dependencies)
  • Category:Mods (Gameplay Changes)
  • Category:Mods (Content Packs)
  • Category:Mods (Bosses)
  • Category:Mods (NPCs)
  • Category:Mods (Spells and Abilities)
  • Category:Mods (Items)
  • Category:Mods (Areas)
• Use Template:Infobox_Mod for the infobox of single mod articles or content pack "home pages"
  • To find the Lumafly link for the install parameter, use the Lumafly Download Command page
• Pages for individual mods such as Charms or Bosses may use standard templates relating to that specific page (such as Template:HK_Infobox_Charm), though they will require extra input such as `title1` for page titles, and other parameters such as fixed links for Template:HK Table Charm Interactions. Refer to each template's page for more info.
  • Alternatively, you may create a new Template with the format Template:[Mod Name]/[Template Name], example: Template:Lost_Artifacts/Infobox_Artifact. This is useful for Gameplay Changes that add new mechanics not covered by existing templates.
• Use Template:ModAchievement for custom Achievements. This requires you to follow the image name formatting File:Mod_Achievement_(name).png for it to function.

Images

• Follow all Image requirements from the main Editing Guidelines page
• File names must include the word Mod at the beginning, with a space or underscore after it.
  • Otherwise, follow image formatting for normal images. For example, images for custom Achievements images must be formatted as File:Mod_Achievement_(name).png
• All images from modded content must include [[Category:Mod Images]] in the description. This can be done during or after upload.
• Image Descriptions must include a link to the mod page in which it appears and a creator credit where possible (sprites/artwork may have a different creator from the mod itself).

Page Examples

• Charm: Mod:Pale Court/Vessel's Lament
• Installer: Mod:Lumafly
• Dependency: Hollow Knight Modding API
• Gameplay Changes: Mod:Lost Artifacts
• Content Pack: Mod:Pale Court