This page serves as a general guide for adding content to the wiki and explains how to maintain pages. If you're not familiar with editing wikis or want to contact a wiki staff person, check out our community portal for helpful links.

For policy on the general behavior and requirements for content deletion, see Honkai Impact 3 Wiki:Policy.

As each template page features detailed documentation on its own, refer to these for further instructions if necessary. Templates meant to be used on a specific type of article will be linked where applicable - generally, below the basic version of an empty page meant for copy&paste.

Key Terms[]

Here are some important things to keep in mind while reading this guide or editing the wiki in general.

• DPL - DynamicPageList is an extension used through the wiki. It can create a list of pages within specified categories and said list can then be formatted freely. It basically lessens the amount of manual work that needs to be done to update things like navigation templates. Use of DPL will always affect user performance even if the output format is kept minimalistic etc. so usually it'll be allowed to keep cached results. Preferably, most pages shouldn't be using more than 1 DPL-based template. You can read more on DPL at Extension:DPL3/Manual - Gamepedia Help Wiki.
• Cached - if something on a page is "cached" it means that what you see might not be up to date as it doesn't load new results every time you enter the page. A cached image file will show you an older revision of it. A cached DPL list may not show you the latest additions to the list. Most things are about 1 hour or 1 day behind but if you suspect that the page didn't update when it should have already, you can easily purge it.

• 

  Purge - option within the dropdown menu found next to the edit button. It clears the cache of the specific page you're on and therefore shows the most up-to-date version of it.
• Spoiler - crucial information important to the overall narrative presented in later game/manga/VN chapters that could potentially ruin the reading/watching experience for anyone who still hasn't reached that point. Pages with spoilers should have {{Notice/Spoiler}} at the top and the spoiler-blur class should be used to blur the spoilers from the lede and the {{Character Entry}} at a minimum, hopefully giving unsuspected readers an opportunity to close the page unscathed. This can be done with {{Spoiler}}, see Ana Schariac for example of usage. The Spoiler template shouldn't be used on text consisting solely of links.
• Lede - the first sentence/paragraph on an article (outside any templates)
• Variable - Container for storing data values, has multiple types. These terms are useful for understanding some documentation:
  • char - stores a single character (e.g. 'a' or 'B')
  • String - stores a collection of characters (e.g. "Hello") [This is the most used of these terms in documentation]
  • int - stores a whole number (e.g. '1' or '2')
  • float - stores a number with decimals (e.g. '1.23')
  • boolean - stores two states: true or false

Articles[]

Event Pages[]

Character Pages[]

PC[]

Playable characters should have their gameplay relevant info first, as such, a PC's main page serves more as a directory with links to all of her battlesuits and outfits those battlesuits can equip.

• {{Navigation Tabs}} adds links to /Dorm Chibi and /Outfit subpages.
• {{Valkyrie Entry}} stores some basic info available on the official website such as birthday but also voice actors whose mentions can be found on the official Youtube videos or Twitter posts. Information not present on the official website(s) shouldn't be added there.
• {{Lang}} should have the character's official English name in it, followed by the original Chinese name.
• {{Battlesuit Navbox}} automatically lists all battlesuits if character is stated in the parameter. You need to create a battlesuit page for it to show results.
• {{Outfit Navbox}} same as above but with outfits.
• {{Valkyrie Navbox}} needs to be manually edited with links to new character/battlesuit pages. Works only on desktop.

Battlesuit Pages[]

• {{Navigation Tabs}} adds a tab at the top to subpages.
• {{Battlesuit Introduction}} stores the most basic information about the battlesuit. Everything except "sort" can be easily found in-game or on the Chinese BBS wiki.
  • "Sort" is short for "shortkey" and it dictates under what symbol/number/letter the entry will appear in a category. Should use single-digit numbers, followed by letters in alphabetical order, to order battlesuits by release with the exception of Augment Core battlesuits which should be right after the original battlesuit. See Category:Bronya Zaychik Battlesuits for an example. This matters only for the battlesuit outfit lists.
• {{Lang}} should include the English name in bold followed by the original Chinese name.
• {{Battlesuit Skills}} stores skill info.

Battlesuit Dorm Chibis[]

Battlesuit Default Outfits[]

NPC[]

NPC pages should use the character's full name if it is known, like Lieserl Albert Einstein.

• Remove {{Stub}} if the page is complete and up to date.

Script Pages[]

Script pages are meant to store the story scripts in at least one language, usually English, up to 3 maximum--English, Chinese (simplified), and Japanese. They exist as a subpage for a specific stage, or similar instance, where the dialogue is happening.

Page Layout[]

(TBA)
==Script==
{{Notice/Script}}
{{Story Text Windowed
|character_1_image = 
|character_1       = 
|character_2_image = 
|character_2       = 
|story             =
}}

• The (TBA) is a placeholder text for the stage's summary that should be transcluded on a directory page via {{Main/Script}}, for Story chapters, that'd be the chapter's main page and for events, it'd be the Story subpage. Without the placeholder, the Main/Script template will include the whole script page instead, which is far from desired.
• The {{Notice/Script}} template adds a script category and acts as a disclaimer for anyone visiting, telling which errors are taken directly from the game and therefore should be marked instead of corrected and which ones are free to change (aka, the CN/JP romaji and translations).
• {{Story Text Windowed}} adds the base background layer for the scripts for a more uniform look and links all relevant characters at the top of the page where they're easy to find and negates the need to link the character pages in the stage summary.
  • Up to 10 characters can be listed.
  • An example image would be Scarlet Fusion (Avatar) for Himeko as she's a playable character with her battlesuit appearing in the story. For NPCs, it'd go something like Himeko (Story) (Avatar) with the avatar being a custom cut-out of the character in a way that matches Category:Battlesuit Avatars dimensions-wise. If the character already has a story avatar and needs another one, a number can be added after the character's name.
  • If the character isn't shown in person, the image parameter can be deleted.
• All dialogue should be placed after the story parameter with the help of the following templates:
  • {{Story Text}} - for text spoken outside combat. The template has 3 different styles, a visual-novel-esque dialogue box with the text color changing depending on the character speaking used for the majority of part 1 Story, a simpler white-yellow-black (for light mode)/black-yellow (for dark mode) dialogue box mimicking the comms windows used in a few early Story chapters and Chronicles like Everlasting Memory, and a starry dialogue box with gradient for all the newer chapters/events. The latter is the default.
    • Should the dialogue box not match the game, the Story Text template needs to be edited to include the root name (the main article that all subpages link to) where relevant.
  • {{Story Stage Text}} - for text spoken by characters outside dialogue boxes, often during combat or stage exploration.
  • {{Story Guide}} - for tips given by the characters, usually directed towards the player.
  • {{Story Comment}} - for editor's comments, such as what needs to be done inside the stage to progress further.
  • {{Story Choice}} - for text-based choices a player can pick from (for non-text-based choices, use the Story Comment template instead).
    • A style needs to be manually changed to modern for newer story entries.
    • The built-in comment can be used to tell the viewers that the choice doesn't yield any extra dialogue. In case it does however, the Story Choice template should be followed by the Story Comment template explaining which choice the extra text is related to, the Story Text holding the extra text, and another Story Comment saying that the extra section has ended.
  • {{Story Image}} - for placing images. The file extension needs to be included.
  • {{Story Video}} - for placing videos. The file extension needs to be included.

Regarding Video and Static Images[]

• Please do not record an animated cutscene to then post it as a video. If you don't know how to or can't extract/convert the video files yourself, use the Honkai CG Project Google Drive.
  • If the drive doesn't have a specific video you're looking for or you have a question, please join the wiki's discord server and look for a user called Luna.
  • Animations uploaded should have the name of the chapter, event, etc. in the file name, followed by a combination of the abbreviation "CG" and a number related to the number of animations that appeared in that chapter, and if the animation is voiced, the (CN) or (JP) text for Chinese and Japanese dubbing respectively. For example, Chapter VII CG01 (JP).mp4 is the first animation appearing in the 7th chapter of the game which is voiced in Japanese.
  • The video should have Category:Game Chapter CG category if it's for a Story chapter and Category:Game Event CG if it's for an event.
• A non-animated video can be uploaded to the wiki to provide extra context like a wiki comment would. Sometimes the characters' in-stage movements are story-relevant and a video is a better choice than multiple screenshots, although the two options are often equally sufficient.
  • The file name needs to start with the chapter or the event it comes from but the rest is free for the uploader to decide. Most important is that the name is unique and doesn't clash with any animations or other user-based videos.
  • The video should have Category:Game Chapter Context Videos category if it's for a Story chapter and Category:Game Event Context Videos if it's for an event.
• A video should not be followed by a screenshot from said video.
• Images, mostly screenshots, can be placed for extra context but are not necessary. The image should have Category:Game Chapter Context Images category if it's for a Story chapter and Category:Game Event Context Images if it's for an event. In case it's used for both, it should have both categories.
  • All screenshots should be .jpg or .webp. Any .png screenshots will be deleted in unspecified future times and replaced with a converted copy or a new, different image. This does not apply to images that aren't screenshots.

Character Names[]

• Some character names can be changed in-game. To reflect them accurately, templates have been made and should be used where appropriate.
  • Template:PJMS_NICKNAME is meant for Part 2's Dreamseeker. In both dubbing options they're referred to as "Dreamseeker", so it has been chosen as the display name instead of their default name, Entropy.

Outfit Pages[]

Weapon Pages[]

• {{Weapon Entry}} is meant to contain all the information about the weapon that's available in-game. If there's anything else that should be noted write it below the template, following the first premade sentence.
  • {{subst:PAGENAME}} will be automatically replaced with text that matches the page title once you click to save the edit. You do not need to replace it manually with the weapon's name.
• {{Weapon Navbox}} only needs the weapon type stated, it should be matching the individual weapon in the Weapon Entry template above it. It keeps cached results for better loading time so it may be outdated for the first few hours/days. Purge pages with outdated results if needed.

Stigmata Pages[]

Page Layout[]

{{Template:Stigmata Entry}}
==Sources==
==Trivia==
==Other Languages==
{{Template:Other Languages}}
==Notes==
<references group="note"/>
==References==
<references />

• Stigma(ta) pages mostly rely on the use {{Stigmata Entry}}, which stores the stigma(ta)'s stats and skill effects. The template also incorporates {{Lang}} to store Chinese and Japanese versions of the skill names, alongside their potential unofficial romanizations and translations.
  • Sources should be marked as yes/no in the Stigmata Entry template for Bunny bot on the official Honkai Impact 3rd Discord server to see them and be expanded upon under the Sources header.
• Trivia can be used to store interesting information, such as name of the person who the stigmata is potentially based on.
• {{Other Languages}} sits at the bottom of the page with the set name and individual pieces listed inside as either of the following:
  • <Set Name> set: <Stigmata Name> (T, M, B), for example Herrscher of Ice set: Ana Schariac (T, M, B)
  • <Set Name> set: <Slot T Name> (T), <Slot M Name> (M), <Slot B Name> (B), for example Shattered Swords set: Raksha (T), Sushang (M), Empyrea Phoenix (B)
• Reference sections shouldn't be removed even if they remain empty.

Preloads[]

4-star Stigmata[]

3-star Stigmata[]

2-star Stigmata[]

1-star Stigmata[]

ELF Pages[]

• Make a page for the ELF using Template:ELF Introduction, Template:ELF Main Skills, and Template:ELF Secondary Skills.

Item Pages[]