Fandom

Wikihack

Wikihack:Style guide

2,035pages on
this wiki
Add New Page
Talk26

Wikihack has no formal style guide as of yet, but there are a few conventions in use. The following is a list of them. Changes should be discussed on the talk page.

Tone Edit

Wikihack is not just an encyclopedia of NetHack, but articles in the main namespace should be written in a largely encyclopaedic tone. That means clearly separating facts from comments, by putting strategy tips in their own section, and comments on the talk page and link building service page. Spelling and grammar should follow Americanized language rules.

Article names Edit

Try to be consistent with existing articles:

The first time the article name appears in the main text, it should be bolded. This includes the titles of any redirects redirecting to the article. In-game messages documented in a definition list will be bolded automatically:

; "You feel centered in your personal space."
: You gained teleport control through eating a corpse, while hallucinating

formats into

"You feel centered in your personal space."
You gained teleport control through eating a corpse, while hallucinating

RedirectsEdit

When creating a new article, redirect variations on that name to it, to avoid someone duplicating the article under a slightly different title.

For in-game messages, redirect the message (e.g. The golden haze around you disappears) to the article about the thing that caused it. If the message can have multiple causes, create a disambiguation page (e.g. Your skin feels warm for a moment).

The syntax for a redirect is like this:

#REDIRECT [[spellbook of protection]]

See Wikia:Help:Redirect for help creating redirects.

New articlesEdit

Do not create empty new articles or new articles that contain nothing but the {{stub}} message just in hopes of seeing someone add more content to them. Add the content yourself! A "{{stub}}"-only page is somewhat like applying a magic marker to write a blank scroll, though the scroll be already blank. If you don't know about the subject, learn about it or ask politely at the Community Portal for someone to create the article.

CapitalizationEdit

Use "Luck" when referring to the in-game attribute Luck, and "luck" when talking about a favorable outcome from the RNG. In addition, "Archon," "Angel," "Aleax," and the new SLASH'EM monsters "Planetar" and "Solar", despite not being proper nouns, are always capitalized in the game, and hence should also be capitalized on this wiki.

Headers Edit

The highest header level that should be used is ==This==. Do not use =These=, they are reserved for the article main title only. In each article, there should be a brief introduction before going into specifics. This introduction should not have a header, like ==Introduction==, because it is obvious and because when omitting it, the introduction appears before the table of contents as it is supposed to.

Section namesEdit

Some sections are common to many articles. Try to use one of these for the section header rather than a variant like "Messages given", "Behavior in previous versions", or "External Links". Known standard sections are:

  • Generation
  • Map(s)
  • Messages
  • Strategy
  • Mythology
  • History
  • Encyclopedia entry
  • References
  • External links

Generation should explain where and how the thing can be found or created.

The History section should be for explaining what the thing did in previous versions of NetHack. Actual history should go in Mythology (if the thing is based on real life, Origin may be a better heading).

The Encyclopedia entry should give the text of the thing's entry in the NetHack encyclopedia.

Categories Edit

Each new article should have at least one category assigned to it; read the category tree to find an appropriate one. Remember to update that tree if you create a new category.

Tables Edit

Many of our tables are pretty tables, the prettytable class from MediaWiki:Common.css can be used like this:

{|class="prettytable"
!Header 1
!Header 2
|-
|Cell 1
|Cell 2
|-
|Cell 3
|Cell 4
|}

to make this:

Header 1 Header 2
Cell 1 Cell 2
Cell 3 Cell 4

Colored NetHack glyphs Edit

Use the 16-color function templates for displaying individual symbols. For monsters you should usually use Template:Monsym. The symbols are padded, so they don't work for making ASCII screenshots. Yet.

Item pages Edit

Put the templates Template:scroll, Template:potion, Template:ring, Template:wand, Template:spellbook, Template:weapon, Template:armor, Template:comestible, and Template:tool at the top of the appropriate item page, or Template:item for any other type of item.

Each item page should also list the effects of the item, and any messages that item can generate. Tips and strategy relating to that item should go next, and if there is an entry from the NetHack encyclopedia, that can go at the bottom. Use potion of object detection, scroll of amnesia and scroll of genocide, pos software as guides.

SLASH'EM Edit

Prefer "SLASH'EM" to "Slash'EM". There is no consensus on which one is "official", but we need a convention, and SLASH'EM is clearly an acronym. If a thing's behavior is slightly different in SLASH'EM, put the differences in a ==SLASH'EM== section. If a thing is totally different, or exists only in SLASH'EM, give it its own article.

Source codeEdit

When writing a piece of factual information, you may wish to document it by linking to the source code like this:

The vibrating square level is not eligible to leave bones files
<ref>{{sourcecode|bones.c|32}} vibrating square does not leave bones</ref>.

which looks like this:

The vibrating square level is not eligible to leave bones files [1].

Make sure you include a <references/> tag at the bottom of the page, to create a list of footnotes:

  1. bones.c, line 32 vibrating square does not leave bones

The templates {{Sourcecode}} and {{Function}} are designed for use in source code references.

Annotations Edit

If you are a source diver, you can add annotations to any source file simply by putting your comments below the relevant line. Try to limit annotations to explanations of the source code; long discussions belong on the Talk page.

Other useful templates Edit

Main article: Wikihack:Templates

{{DOD}} should go at the bottom of every page which is based on a spoiler by Dylan O'Donnell.

{{disambig}} should go at the bottom of every disambiguation page, e.g. Fire. A disambiguation page is a list of links to articles all associated with the same title.

{{stub}} can be used on a page to plea for someone to expand it. From time to time, some editors will look over Category:Stubs for articles to expand. The template can take an optional parameter, for example:

{{stub}} on any page, or
{{stub|What's the strategy when dealing with him?}} on Wizard of Yendor

{{merge}} is a plea for someone to merge a page with another, or several others. You should give details of which other page you mean in the parameter:

{{merge|Some of this information belongs in [[this article]].}}

{{otheruses}} is for pages like whose title has multiple meanings, like Izchak. In many cases, a disambiguation page may be more appropriate, but where one meaning dominates the others, it deserves the page title. Also see the {{for}}, {{for2}} and {{distinguish}} templates.

{{main}} can be used to link to the main article for a topic, per this section:

{{main|Wikihack:Templates}}

Namespaces Edit

Anything to do with NetHack belongs in the main article space. Anything to do with Wikihack belongs in the Wikihack namespace.

User pages Edit

You can create a vanity page in the main namespace if you want to, but unless you are famous or otherwise notable it would be a better idea to create a Wikihack account and put personal information on your own User page.

Sign your posts Edit

When writing on articles'/users' talk-pages or on certain community pages, sign your posts with four tildes, ~~~~. That will automatically expand to your signature with timestamp, as in "ZeroOne 17:57, 15 August 2006 (UTC)".

General principles Edit

Ad blocker interference detected!


Wikia is a free-to-use site that makes money from advertising. We have a modified experience for viewers using ad blockers

Wikia is not accessible if you’ve made further modifications. Remove the custom ad blocker rule(s) and the page will load as expected.