The Corepunk Wiki strives for a comprehensive archive of information about the videogame Corepunk. As such, anybody is able to contribute, no matter how big or small the contribution. Users do not need to register to contribute to the wiki. If editors do not register, their edits will be identified with their IP address.


This section outlines important editing guidelines. Anyone editing the wiki should familiarize themselves with these rules.


Content should be written in American English, in an unbiased, formal manner. They should be as concise as possible whilst still being readable to most users and without loss of information. Content should be relevant and should not be a narrative short story.
If a page is long, a summary section containing key information should be written at the top of the page.


Editors must ensure articles have a consistent and standardized appearance. This is done through the use of templates. Articles must be format in a way that is clear and easy-to-understand.


The following table lists the most widely used text formatting options:

Text Editor Result Use
''Italic Text''
Italic Text Used for emphasis or to distinguish a title of a certain work.
'''Bold Text'''
Bold Text Used for emphasis. Typically used to emphasize words under a section heading.
  • 1st
    • 2nd
      • 3rd
  • 4th

Used for unordered bullet-point lists. First-level bullet-point lists have mostly been replaced with the {{arrow}} template.

  1. 1st
    1. 2nd
    2. 3rd
  2. 4th

Used for numbered lists.

== Section ==
=== Subsection ===
==== Sub-Subsection ====




Used for separating content. Usually written in title case.


Paragraphs are separated by an empty line.<br>
Force new lines with the HTML break tag.


Paragraphs are separated by an empty line.
Force new lines with the HTML break tag.

Paragraph formatting.

: Indented text
:: Double-indented text
::: etc.


Indented text
Double-indented text

Used for indents. They most commonly can be seen documenting NPC dialogue trees, with the {{dialogue icon}} template.


The following table lists different ways to link to internal or external pages:

Text Editor Result Description
[[Corepunk Wiki]]
Corepunk Wiki Simple internal link to an article.
Help:Example Internal links to non-existent pages are displayed in red.
Heroes Characters immediately following the ending brackets but before a space are automatically appended to the link text.
[[red mushroom]]
Red mushroom The first character of an internal link is automatically converted to upper case.
[[Corepunk Wiki|Main Page]]
Main Page Text following the "|" character is displayed as the link text.
[https://corepunk.com Corepunk]
Corepunk If only single square brackets are used, an external link is created. Note that unlike in the previous example, no "|" character is used to change the displayed link text.


All images, with the exception of icons, should be uploaded as .jpg files (80% compression). This makes load times for pages with many images significantly faster.
Icons should be uploaded as .png files with the highest resolution possible, preferably from Corepunk's game files or the Official Press Kit.
When taking screenshots, ensure the image quality is the highest possible before compressing. This means all graphics settings should be set to their maximum values.
All files must have the correct license attributed to it, and editors must use the file in accordance with the license.


All content on the Corepunk Wiki must be properly sourced. The use of all copyrighted images must qualify under fair use. In most cases, this means that copyrighted images must be used for educational purposes only.


Upon submitting an edit, users can mark it as either a Minor Edit or a Major Edit. Additionally, users can use Dummy Edits to update pages.
Users can optionally fill in the Summary text box below the editing area to explain the content of the edit. Before clicking the "Save changes" button, it is encouraged to click the "Show preview" to ensure the page's content and format is correct.

Minor Edits[edit]

A minor edit signifies that a small, superficial change has been made to a page. This may include, but is not limited to: fixing typos, spelling and/or grammatical mistakes; altering page appearance and/or structure; updating inaccurate information; or addition of detail that is of little importance to the overall article. A minor edit is an alteration that the editor believes requires no review and could never be the subject of a dispute.

To signify a minor edit, tick the checkbox labeled "This is a minor edit" above the "Save changes" button. Marking an edit as minor does not mean the contributor should forgo writing an edit summary. Editors should not feel that marking an edit as minor devalues their contribution in any way.

Major Edits[edit]

Major edits are edits not considered to be minor. Editors should first consider adding to to the relevant talk page and getting consent from relevant editors first before making the contribution. If an edit takes place over an extended period of time, consider saving the page and using the {{in use}} template to prevent edit conflicts and ensure progress isn't lost if the web browser crashes.

Dummy Edits[edit]

Dummy edits are changes to a page's wikitext that have no effect on the rendered page. They are useful for updating templates used on a page or any uploaded images.
To perform a dummy edit, users can:

Arrow.pngremove the newline character at the bottom of the text.
Arrow.pngadd a comment.

Article Creation[edit]

Before article creation, ensure that it is necessary and relevant to Corepunk. Novice editors are reccommended to begin with smaller edits first before creating a new article. The easiest way to create a new article is to find and click through a red link, such as Help:Example.

Talk Pages[edit]

Talk pages are used to discuss possible changes to a particular article before it becomes a submitted contribution. If an editor is unsure about a contribution, it is reccommended to ask in the article in question's related talk page. Editors should sign their contributions to a talk page with their signature with four tildes (i.e. "~~~~").


The average user should be able to look at a page's source and understand its general function. A page's source should be documented with comments if it is hard to read and/or understand. This means all code that isn't self-explanatory should be commented.

Naming Conventions[edit]

Pages and headings should be named formally, concisely and sensibly. It should convey a general idea of what the section is about.


Templates are snippets of wikitext to be included in articles. They are used as a means of standardization and ease of use. In general, if a snippet is repeated across multiple pages, it should be abstracted into a template.
Comments in templates should be adjacent to the line it is commenting on, or directly above the relevant section.

All templates should be documented with the following headings (if necessary):

Arrow.pngDescription (required)
Arrow.pngUsage (required, using the {{T}} template)
Arrow.pngParameters (using the {{parameter}} template)
Arrow.pngTemplate-Specific Headings (for clarity)
Arrow.pngErrors (any and all usages of {{error}} should be documented here)