v50 Steam/Premium information for editors
  • v50 information can now be added to pages in the main namespace. v0.47 information can still be found in the DF2014 namespace. See here for more details on the new versioning policy.
  • Use this page to report any issues related to the migration.
This notice may be cached—the current version can be found here.

Dwarf Fortress Wiki:Community Portal

From Dwarf Fortress Wiki
Jump to navigation Jump to search
See the Help page for technical information. See the Wiki Introduction and Editing FAQ for an introduction to editing this wiki.

This page is for organizing the war effort against entropy. Also, please check out the Dwarf Fortress Wiki Improvement Drive!

We are doing this! Let us do it right.

  • Alphabet: Okay, the first rule is that there must be a rule for each letter of the alphabet. Thanks to the community, we now have all twenty-six rules (plus a few more)! (Inspired by Peristarkawan's nomic instincts)
  • Be bold! So says Wikipedia. If you see a mistake, be it a fact or a typo, change it. Don't leave it to someone else to clean up mistakes. Feel free to make changes. If you think an article needs a major rewrite, and you think you can do it, go ahead and do it! You can also use the discussion (talk) page to post suggestions.
  • For help getting started, see the Wiki Introduction and Editing FAQ.
  • Categories: When editing a page, stop to think about what categories it should be included in, and add them if necessary. Don't forget to consider categories that don't yet exist. Capitalize the tag like [[Category:Stub]]. (However, if the page and category are version-specific, you should use {{Category|CategoryName}} instead).
  • See also Categories Help and List of All Existing Categories
  • Discussion: Use the discussion page to voice suggestions and to ask questions. Try to limit inline comments. Before editing, check the discussion page to see if there are any changes being planned. The centralized discussion page is being used to announce such discussions to the general population, so as to make them findable for those who do not religiously keep up with Recent Changes. Please add your own discussions to it.
  • See Help:Talk pages and Wikipedia:Talk page guidelines for talk page conventions and a more in-depth explanation.
  • Eliminate fluff. This includes redirects that aren't linked to and wouldn't be typed in the search box. The {{deletion}} or {{del}} template is your friend. (See also the Deletion Policy.)
  • Facts: Keep your information factual. If you haven't confirmed something, post it on the discussion page. Don't create linkless one-liner pages. Add as much pertinent information as you can and avoid conjecture (possibly, maybe, could be, likely) by providing concrete examples from the game or links to other parts of the wiki.
  • Gameterms: To avoid confusion, use the terms the game uses whenever possible. For example, the game refers to "armor" and "aluminum" rather than "armour" or "aluminium", and the plural forms of "dwarf" and "bronze colossus" should be "dwarves" and "bronze colossuses" rather than "dwarfs" or "bronze colossi".
  • Headings: Organize the content of each page into sections of related information. After the introduction, use appropriate headings for each section, and follow the Naming style of this guide. Keep headings to a minimum; consider a list or a table if you have many repetitive facts.
  • Images: Images and screenshots should clearly depict the subject. Small diagrams can be constructed with <diagram> or {{RT}}, for easy editing, and to save on space. When uploading images, give them a name that is descriptive and unlikely to be duplicated. Names like "1", "screenshot", and "untitled" should be avoided. PNG images are preferred over JPEG where possible, as they don't lose visual quality during compression (and tend to be smaller anyways).
  • Jealousy: Don't be shocked if someone rewrites or removes your article; your hard work is not lost. Post suggestions on the discussion page and talk about the issue. All versions are stored in the history, so your material can be reused or merged with existing content if the rewriter left something out.
  • Keys: The original version of the game uses 100% keyboard input, so we have a template to improve the display of keys: {{k}} (abbreviation of {{key}}). For example, the syntax {{k|q}} will generate q, a standardized and visually pleasing representation of the "q" key. The enter key should be done as {{k|Enter}} (Enter), for example, and the arrow keys use arrow characters, found in the second row of this handy code page. The right arrow key, for example, appears as . {{k-}} can be used for sequences of keys - for example, {{k-|a|b}} produces a-b.
  • More people should use the raw files (found in your 'install dir\raw\objects' or data/vanila on Steam) to get information about creatures and objects. They have loads of good information that the game actually uses.
  • Naming: The titles of new pages should be singular nouns, with only the first word capitalized. Example: Screw pump, Metalsmith's forge, Gear assembly. Exceptions are proper nouns and terms that are always plural. Getting the wrong name can mean extra redirects and always means a page move. Screw pump is not the same as Screw Pump. Exceptions may be made in cases where two very different things would otherwise have the same page name, such as bar versus bars. Do not put question marks in the names of articles: due to the way they are handled in URLs it messes things up, though not irreversibly.
  • Original research is good! Forget what you've seen on That Other Wiki; personal experience is perfectly fine here. Without original research, this wiki would be a tiny fraction of its current self – so if you see something that seems wrong, needs verification, or just lacks information, load up the current edition and check for yourself (but please, say you've done so on the talk page).
  • Preview: Use the preview button to check for typos. Avoid cluttering the history of a page with multiple edits. Mark small changes as 'minor' so they can be (optionally) hidden from the recent changes page.
  • Queue: Check the special pages for work still to be done! There are lists of dead end pages, uncategorized categories, broken redirects, and others that all need work occasionally. Or try looking up pages by quality and trying to improve lower-quality ones to a higher quality level.
  • If you feel more like writing content than maintaining the wiki, the list of stub pages is a good place for you to start, followed by the short pages that exist.
  • If you feel like doing research about how the game works, have a look at Rule V.
  • Redundancy: Before creating a new page, do a search to find out if the topic is already discussed in detail somewhere else. If you find that redundant pages already exist, merge their content and have one redirect to the other. This rule also refers to redundant material inside pages.
  • Style: In general, try to follow the Wikipedia Manual of Style when writing articles. For example, introduce keyword articles by highlighting the first keyword in bold, such as Rules.
  • Also see DF:Manual of Style for information specific to this wiki.
  • Timelessness: The wiki is intended as a guide for all players, even new ones. As such, references to differences from or similarities to old major versions of DF should be moved to the appropriate version page. Avoid phrases like "now marble can be used to make steel" or "before, farms required two floodgates", etc. Specific references to minor versions in the same namespace are acceptable - for example, "minecarts were added in v0.34.08", or "creatures do not breed by spores as of v0.40.19". For facts that are likely to change in the future, or placeholder features, use the {{Version}} template, and for bugs that have yet to be fixed, use the {{Bug}} template. Note that references to differences from or similarities to newer versions of DF may be acceptable on pages for old versions.
  • User pages: Introduce yourself, let the community know who you are. If you have a comment on someone's actions on the wiki, praise or otherwise, post it on their talk page, and they'll get notified next time they log in. Avoid editing other users' user pages unless it's absolutely necessary (for example, removing a user page from an inappropriate category). Keep this place civilized; avoid flame wars, personal attacks and insults.
  • Verify: Many loosely based assumptions are floating around. Verify your information and check Category:Articles needing further verification if you think you can help verify others. If you have something that is not verified, use the {{verify}} tag right after it.
  • Wit can be hard to recognise once it has been written down. It is best if it is used on clearly humour/story-related pages, talk pages, or user pages, but kept to a minimum in fact-based articles like Dwarf or Summer. Use an appropriate template such as {{D for Dwarf}} if there might be confusion.
  • Xeniality: Be nice to people who are new to Dwarf Fortress.
  • Ye Olde Info: It's outdated - update it. Keep the wiki up to date. Remember, sieges were only buggy in a few old versions! Also make sure you're looking at the correct version of a page, especially when editing - if you're playing the latest released version, the information present in the "v0.34", "v0.31", "40d", or "23a" pages is likely to be outdated and incorrect for you, but people playing those old versions will want information that is accurate for them.
  • Z: the mark of Zorro. Sign each of your 'Talk' entries with your own --~~~~.

More rules

  • Redirects: Redirects should almost always be created in a versioned namespace (e.g. Main). For example, instead of creating a redirect from Kitten to Cat, create a redirect from Main:Kitten to Main:Cat. Doing this makes links to Kitten work from both Main pages and pages in the main namespace. Redirects should almost never be created in the main namespace. See DF:REDIR for more information.
  • Spelling: American and British spellings are both acceptable, unless they violate Rule G.

Notice Templates

There are templates available for marking pages needing improvement. Ideally, you should make appropriate changes and move on, but if you are unable to access the required information, post a notice to flag an issue up. Using template notices provides a consistent way of flagging a page. Notices in use can be tracked through category pages. Notices based on rules from this page should all use the Category:Pages that break Community Portal rules category.

This section is far from complete.

Template for Notice Templates

{{Colored Notice Box|#FF00FF|Contents of the message}}

Image Rules Notice

{{Image Rules Notice}}

Timelessness Notice

{{Timelessness Notice}}

New Notices

If several pages arise that break the same rule, create a new template based off one of the above templates. Remember to include the Category:Pages that break Community Portal rules tag at the bottom, or some other appropriate category so that other users can track pages that need reworking. To create a new template, type [[Template:Rule name notice]] into an article, or directly into the address bar of your browser.