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. In a nutshell, experimental content never replaces early access content, but is rather presented alongside it and marked as experimental.

History sections are exempt of this rule, as mentioned below.
 * 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 is marked with  or its shorthand.
 * Example: The Fluid Freight Car can carry 1600 m of fluid.
 * UI icons are not replaced with the experimental only version, nor are they reuploaded as a separate file.
 * If a recipe was changed in any way (ingredient, crafting duration, building etc.), it is stored as another separate recipe set to experimental and the name marked with.
 * If a feature was removed in experimental, it is marked by appending it with  (the   template is for completely removed content only), and the removal is mentioned in the History section.
 * Example: Biofuel is an item that can be crafted from Biomass.
 * Pages are not moved to stay in trend with new names of features.
 * Example: Patch 0.3.6 introduced Mk.2 Pipelines and simultaneously appended "Mk.1" to "Pipeline" to more clearly distinguish them. If both Pipelines were maintained on separate pages, this would mean that Mk.1 Pipelines would be on a page named "Pipeline" (consistent with Early Access), while Mk.2 Pipelines would be on a page named "Pipeline Mk.2".

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

 * Spell out numbers below 10 (zero to nine) when used in sentences. Use numeric symbols for numbers greater than 10.
 * 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.
 * Only include information immediately relevant to the page (e.g. Assembler's building cost is changed and no longer requires Modular Frames – this is mentioned in the Assembler's history, but NOT in the Modular Frame history).
 * 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 changes".
 * 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.
 * If there are changes that are not mentioned in any patch notes, or the exact patch in which the change occured is not known:
 * Use "Unknown Patch before/after (link to patch)" or "Unknown Patch between (link to patch) and (link to patch)" for when it was added into the game.
 * Alternatively, "Unknown Update X patch" can be used (where a certain update refers to any patch during the development of that update).
 * Include references if possible.
 * Use language similar to official patch notes.

Examples of good history sections: Geothermal Generator, Cable, Electric Locomotive

Images
Images should follow these general guidelines:
 * All images:
 * Categorize and apply the license on all images on upload.
 * Use simple, short, recognizable filenames. "Raw Quartz node in a cave.jpg" is a far better filename than "Picture of a quartz node I found in a cave full of spiders while exploring rocky desert.jpg".
 * For user-made in-game screenshots:
 * If taking a screenshot of a subject, ensure there is nothing intrusive in the way. If UI is not relevant in the screenshot, use Photo Mode to hide the UI. Unequip any equipment, which usually takes up a lot of the screen.
 * Unless transparency is necessary, use JPG, aiming for filesizes of about 300 kB or less. WebP is another alternative which allows for transparency. The resolution of the screenshot can be usually reduced as well.
 * PNGs can be compressed using tools online, which can reduce their size by 30-70% without any visual loss of quality.
 * For user-made infographics or similar non-screenshot images:
 * Just as with in-game screenshots, avoid intrusive elements in the image and aim for the smallest filesize.
 * Screenshots of third-party tools using assets from Satisfactory use.
 * For UI icons extracted from the game:
 * Use the highest resolution available (as there are usually two or three resolutions of the same UI icon).
 * Do not alter the images in any shape or form.

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".

= 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.

Recipes
If the building is used for any recipes, they are listed here using.

Overclocking
If the building is a powered consumer or generator, information about overclocking is listed here using.

Types
If the page is a merged page, this section has a table outlining the key differences between the individual types of structures.

Construction
This section outlines information about how the building is built, which is usually used for non-interactible logistics structures, or building where how they are built is important for their functionality. Otherwise, it is excluded completely.

Usage
This section elaborates on the usage of the building. Can be excluded for buildings used solely for crafting recipes.

Remaining sections
Tips, Trivia, Current issues, Gallery, History, References and See also sections are identical to the item page format.

= Patch notes format = Patch Notes: Early Access (EXPERIMENTAL) (if experimental, always noted in the header) - v0.0.0 - Build 000000. This patch was released on Month Day, Year.

The original post can be viewed on Satisfactory's Discord,(direct link to the patch notes message in the server) Reddit,(direct link to the post) and Steam.(direct link to the Steam Community post using the Share button, acquired from here)

If a major patch, official logo precedes the mean section, see Patch 0.1.5, Patch 0.2.1, Patch 0.3.3.3 and Patch 0.3.5.

If there was a hotfix released that didn't increment the version number but changed the build number, it should be mentioned in the mean section. If there was an additional note added to the patch notes, it should be in its own section named Hotfix that is placed before the intro. See Patch 0.3 for an example.

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.