Satisfactory Wiki:Style guide

This page is a guide to creating or editing mainspace pages at Satisfactory Wiki in accordance with the established article style. These guidelines are not set in stone, but they should generally be followed in order to maintain consistency across pages, unless there is a good reason to make an exception.

Language and units
The default game language is US English, therefore, the wiki should use US English as well (this is why the american spelling of Aluminum or Sulfur is used), same applies to the formatting of numbers, discussed below.

The units page discusses units present on the wiki. The US spelling of "meter" should be used, not "metre".

Experimental content
The wiki prefers content in the stable branch of the game over experimental, as discussed here.


 * If a feature is only available in the experimental branch (e.g. a building or mechanic), the page is marked as experimental content using.
 * If there was a change to a feature already in the stable branch, experimental only content can be marked with.
 * Example: The Fluid Freight Car can carry 1600 m of fluid.
 * History sections are exempt of this rule, as mentioned below.

Upcoming content
Upcoming content is content that has been officially teased and is expected to be introduced to the game in a future update.


 * In order to prevent many stub pages being created (as there is usually little or just not enough information about teased features), all upcoming content should be listed on the Future content page.
 * Certain exceptions can apply, which are situational (e.g. dedicated servers belong more on the Multiplayer page, although being an upcoming feature).
 * Even if enough information for a feature is gathered, it should remain on the Future content page. Pages created despite this should be marked as upcoming content using.

Numbers

 * Where large numbers are mentioned, every 3 digits should be separated with a comma, such as 1,234,567,890. Spaces are not required.
 * Periods should be used as decimal separator, such as 0.5 etc.
 * Where superscript is to be used, prefer template over Unicode as the latter is smaller and thus more difficult to read. These templates is a shorthand to call
 * = 45 m
 * = 300
 * = 30 km

History
This section of the page should list changes to the article topic based on game patches. It should generally follow the official changelog, but sometimes there are undocumented changes introduced in updates. In those cases, the information should be based on in-game testing.


 * Entries are listed retroactively: The most recent change is at the top and the oldest at the bottom.
 * Entries start with the patch that is always linked.
 * If there was only one change in a patch, the entry is on one line.
 * If there were multiple, all notes for that patch are indented, and the first line only has the patch.
 * If it has zero entries,  is used to mark it as missing.
 * If it has some entries but is either outdated or there are uncertainities,  is used to mark it as such.
 * If it has been introduced as brand new, the entry should say just "Introduced". If it was implemented from being previously unobtainable (unreleased), it should say that it "has been made officially available".
 * If it never has changed, there should be only one point saying "No recorded history".
 * Unlike the rest of the wiki, entries prefer experimental over stable. Therefore, if something changes in experimental before it goes to stable, only the experimental change is mentioned.
 * This is because something can change in experimental and then be reverted back, which would result it not being mentioned at all.

Other

 * Every page should be categorized except for buildings, which are automatically categorized as 'Buildings' as long as the infobox on the page has 'craftedIn = Build Gun' and has a defined subcategory, as in build menu.
 * Whilst the Discord role is a capitalised singular term "COFFEESTAINER", the mixed-case usage appears on the Coffee Stain website as "Coffee Stainer".

Tables and images
Tables and images, if used correctly, can greatly reduce the amount of text.

= Item page format =

This is a brief description of the item that either mentions how it is obtained or used. is used, and is placed before this mean section, but after any notices there may be on the page (such as,   or  ).

Unlocking
If unlocked via M.A.M. research,  is used.

If unlocked via the AWESOME Shop,  is used.

Resource acquisition
For a raw resource,  is used.

Crafting
If craftable, recipes are entered using  and rendered using. If multiple items are present on the same page, use ...

Space Elevator
Only for Space Elevator parts, mentions that it is used to complete deliveries in the following format:

Part Name is used to complete deliveries in the Space Elevator.

Research
If used in any M.A.M. research chain,  is used.

Equipment
If equipment, its usage should briefly be explained here, better here than in the mean section.

If used as ammo for any tool or weapon, this should be mentioned here.

Crafting
is always used, as when it cannot be crafted into anything, the template will say so.

AWESOME Sink
is always used, as when it cannot be sunk, the template will say so. When there are multiple items in the same page, use.

Tips
If there are any tips to be mentioned, they shall be listed here.

Trivia
If there is any trivia, it shall be listed here.

Current issues
If there is any bugs, glitch or their work-around, it shall be listed here. Besides that, make sure to report such bugs to https://questions.satisfactorygame.com/.

Gallery
If the page has any specific images to be displayed, it shall be here in its own gallery section.

History
History follows general guidelines as mentioned above.

Intro
The intro text that precedes the actual patch notes.

Patch note sections
Each patch note section has its own header, which is not in all caps (as formatted by default) and uses sentence case instead. Note that patch notes from Discord have preformatted bullet points (•), those should be replaced with normal lists:

• Change 1 • Change 2

Correct formatting:
 * Change 1
 * Change 2

The page should be categorized to Category:Patch notes and have  at the bottom.