Squad Wiki

A wiki style guide is necessary to ensure all editors produce consistent work. Without a style guide, one editor will do things one way, while other editors do it in other ways, eventually leading to inconsistent or maybe even confusing content. Editors still have a lot of freedom, but we have to agree on some essential standards. When you start editing, you will soon come across aspects of formating or style where you have multiple options. For the most common ones we should agree on one consistent style and list them here. You will see - this makes your life as editor easier, not harder.

General guidelines[ | ]

  • Read and comply to our Wiki Rules at all times - non-compliance may lead to bans.
  • American English. The language of the English wiki pages is English, obviously. For the sake of consistency, lets stick to American English spelling.
  • If you are referring to an in-game keyboard shortcut or buttons, make sure to make use of the template {{key_press|SPACE}} - it will look like this: SPACE. Credit for this template goes to TomNedry.
  • No duplication of content. Explain a topic on one page where it fits best. If you need to refer to that topic on another page, link back to the original page, do not re-create explanations/descriptions/facts twice. This would turn maintenance into a nightmare and invite inconsistency/contradiction. And it's plain bad practice.
  • Do not copy over text from Wikipedia or other similar web resources. If there is relevant and useful information, provide a link under the section "External links" or "See also" at the end of the page.
  • Links/cross-links.
    • Cross-links: When talking about a topic/term, link to that page from the text. Example: The text is referring to "Squad Leaders", then also link in the text to the main page Squad Leader.
    • Use cross-links as often as possible on all pages throughtout the wiki. This will make navigating much easier and will guide people to the important pages and topics the text is talking about.
    • Spell the "link text" in the grammatically correct way of your surrounding sentence (including upper- or lowercase). Example text: "When wounded, always true to apply your own field dressing first.".
    • External links must be accessible worldwide. Do not use region locked links. Example: Vehicle info on "Car And Driver" is not accessible in Germany and probably other regions outside the US.
  • Use consistent terminology, names, and spelling. Always use the same terms and names throughout the wiki. For example: if you are refering to the Russian faction, use a consistent name. Do not use different terms in different places, e.g. Russian Ground Forces, The Russians, Russian Army. When unsure about the correct terminology, search the terms on this wiki. If you are the first to introduce a new term, go to and check the Kickstarter description, the boot camp series and the Squad user manual.
    • Do not use abbreviations (e.g. do not use "SL" for Squad Leader but spell out the word "Squad Leader" every time you use it; if you find SL on some wiki pages, this is only a legacy from the original Squad user manual which was the basis when the wiki was first set up - please correct it).
    • When referring to roles/kits, such as Squad Leader or Automatic Rifleman, always use uppercase spelling to make the roles stand out from the surrounding text.
  • Consistency across the wiki. Go through all pages of the week, but most importantly related pages and make sure of consistency in terms of look, use of subheadings, formatting, style, text/topic depth, etc.
  • Text is concise and to the point. Keep it short, concise and structured. People come to the wiki to look for answer. They want to find the information quickly and be able to understand it. They do not want to read a long-winded novel.
  • Translation friendly. Whatever you do on the wiki, keep in mind that it will have to be transferred to other languages. Please do not make the job of the translators unnecessarily difficult.
    • Images: If possible, avoid adding English text to images. Keep explanations in the body text of the wiki pages - this will make resuse and translation for other languages much easier. If English text in the image is unavoidable, please upload the image also without the text.
    • (Work in progress). There will be many more guidelines regarding translation-friendliness. Feel free to add points here if you can think of them. Once translation has started in earnest, we will become much more aware of where the problems/challenges lie.
  • Keep images simple. When you create and add a screenshot, keep the composition and setup simple of the picture. The game is changing at the fast pace and any screenshot you add, will have to be updated many times over in the near future. If you make an overly elaborate and complicated screenshot, updating it will take equally long and only makes it unnecessarily difficult for others to do so. Don't waste your own and others time. This rules applies in general and exceptions are permitted, of course.
  • Choose page titles well.
    • 1) Think really hard whether a new page is really necessary. Does your new content not better fit onto an existing page?
    • 2) Make sure that pages does not already exist under a similar or different name (search for applicable or shortened keywords and look at All Pages).
    • 3) Think very hard about the most suitable title for the page. There are many ways to write a title, make an effort to choose wisely and with foresight. Choose the most approriate name.
    • 4) Comply to the following style guides regarding page titles.
      • All page titles are uppercase. Example: "Frag Grenades", not "Frag grenades". This does not apply to connecting works, e.g. "Advance and Secure". This rule is necessary for consistency. Also it makes it easier when writing links to other wiki pages if you know the case (links are case-sensitive, if you get the case wrong, instead of linking to the existing page, it will link to an empty and new page with the same name but different spelling).
      • In most cases using singular is better than using plural. Example: "Control Point" would be better than "Control Points". But it's a difficult call. Sometimes plural flows more naturally.
      • Keep page titles as short as possible.
      • Make them clear - looking at the page title should give a clear indication as to what content is on that page
      • Use consistent titles that go well with existing page titles. Cross-check Special:AllPages for existing pages for guidance before choosing a new title.
      • The rule "Use consistent terminology and names" from above also applies to titles, of course. Please read this rule.
      • WIKI_TASK: Add more guiding principles that help distinguish between good and bad titles.
  • For item-pages, use templates and categories. When you are working on item pages (repetitive individual pages on similar topics, e.g. Weapons, Maps, Factions, etc), you must use templates and categories on each page for consistency and easier maintenance, do not just edit plain wiki pages for every item. It might also make sense to create style guides for each of these item pages, just like the Terraria wiki did.
  • Always provide edit summary. Please always add a short summary description when you save your changes, even if your summary is just one or two words long (e.g. "typo"), it still helps to understand what you did to the page and why. It actually helps. Admins have the job of patrolling edits and other editors also should know why you did a change. Of course, if you did a huge writing task with 25 edits to one long page over an entire afternoon, it is enough if you provide a description of your edit in the summary at the beginning - for consecutive edits you don't have to repeat the same summary over and over again.
  • Desktop screens resolution. For desktops we make the assumption our visitors have screens with resolution of 1920x1080 and we optimize our pages accordingly for it.
  • Mobile view. Everything on the wiki must also work in mobile view (or at least be reasonably readable, even if it's less pretty).

Images[ | ]

In dealing with images, please comply to the following guidelines:

Creating and uploading images to the wiki[ | ]

  • Image resolution: please take screenshots in 1,920 × 1,080 pixels resolution
  • Try not to add additional text to images unless absolutely necessary - this will create conflicts with translations.
  • File names
    • This is a tricky one - we haven't yet defined a naming guideline and many of the media files have names all over the place. Until we have a guideline, please use best reasoning - most of the other media files probably do not make for good examples. But if you upload related images of existing images, maybe have a look at the names of similar media files.
    • Do not use the current Squad version in the file name (images get updated over the previous versions - see file history in this example: main menu)
    • Sometimes it's useful to add a comment, particularly if you do a re-upload
  • Licensing. Make sure to attribute a license to every uploaded file.
    • When uploading screenshots from the game, make sure to always select "This is from the game or its official website".
    • If you create images newly yourself, we recommand you upload it under "This is licensed under the Creative Commons Attribution-Non-Commerical-Share Alike License" - this is the license that applies to all written content of this wiki. If you upload it as "I created this file myself (not a screenshot)", it will automatically be marked as "public domain".
  • Please add an appropriate category to the image - see #Categories.
  • When you update an image with a newer version (e.g. because a newer version of Squad made it necessary), do not upload it as a complete new file under a new name. Please use the re-upload/update function "Upload a new version of this file" for the existing image (you find it on the media page of the image).
  • Important note for editors/translators: To ensure that images/files can be used for all subwiki languages (e.g. the German subwiki), it is recommended to upload the images/files onto English main wiki.

Using images on the wiki[ | ]

  • If you want to show images in large size:
    • Use left alignment
    • Use 700px size
  • If you want to add a caption text to an image, put it underneath it.
  • Keep the image link to its original file, do not link from images to other pages or websites - if you do this, viewers cannot enlarge the image and can also not see its license. Exception: If you have a overview table, of lets say images all maps or vehicles in Squad, it's ok to link to the corresponding pages.
02-03 02 1 ServerBrowser newlook5

Maps[ | ]

Map layer images[ | ]

All map layer images should comply to the following guidelines (for consistence of all map layer images):

  • You screen resolution is set to 1920x1080.
  • Start Squad and go into the Shooting Range.
  • Use the admin console command "AdminChangeMap" to change to the desired map layer.
  • Go into admin cam with Shift + P and move the admin cam off map - the admin cam symbol should not be visible on the in-game map. We use the admin cam because it shows all vehicles from both factions.
  • Use the commander menu Caps Lock to bring up the in-game map (this has the largest view of the map).
  • Use the following map UI settings:
    • Grid Opacity = 0
    • Flag Line Opacity = 1 (RAAS and Invasions layers should have an opacity of 0)
    • Map Icon Scaling = 1.2
    • Toggle View Spawns = Off
  • Take the screenshot - in Steam it's easy to do with F12, but you can also use any other tool. If you do not take a full screenshot but only a screen region, include just the map layer, no other part of the UI should be included (fine cropping happens in the next step).

This process is the same for all game modes, even though in some game modes the results might differ greatly.

After taking the screenshot with the above guidelines do the following steps on your image file:

  • Crop it (crop to just the map layer image). Ideally, this should be close around 700 x 703 pixels - but it doesn't have to be pixel perfect.
  • Give it a file name in exactly the following format: MapName_GameMode_Version.jpg (e.g. Al_Basrah_AAS_V1.jpg). Those parts in uppercase and lowercase are relevant, stick to it precisely, including for the extension ".jpg". Please look at existing map images to get the spelling 100% right for all parts of the file name - otherwise you will break automatically generated links and the image will not show up on all pages correctly.
  • Save the image in the image format jpeg (extension as ".jpg"!) (because all our existing map images so far are jpeg and you cannot update an existing media file with a different file format; also we have hard-coded in our scripts to only process jpeg files for the map layer images).
  • Upload the file here. Important: if the map layer image already exists, re-upload your image over the existing media files - do not upload as a new media file. If it's a new map layer, you upload the media file as a new file.
  • (Only if you created a new media file) Set the licensing to "This is from the game or its official website" also edit the media file and add "Category:Minimaps" to the end of the text.
  • The wiki page should auto-update with the new image. If it does not, double check the file naming. If the image is still not showing up contact an editorial member.
  • The Squad Wiki Editorial will usually also run some post-processing over those images to add watermarks and map names into the images - we can still do this later, so do not worry about that.

The image should look similar to this:

Al Basrah AAS V1 Style Guide Example

Vehicle infosheets[ | ]

For Vehicles we use image-based infosheets. We have created one unique sheet for every vehicle. On the sheet, the most important statistical information is shown. This way, we can show those infosheets multiple times anywhere on the wiki but only have to maintain one image with the latest stats - very handy. Example:

M939 Logistics Truck Statistics

The following guidelines apply to vehicle infosheets:

  • Please keep infosheets consistent. Always use the same stats, symbols and layout for all infosheets.
Supply icon Supply capacity: Indicates the total amount of Ammo and Construction points a vehicle can carry combined.
Vehicle ammo icon
Ammo capacity: Some vehicles can only carry Ammo
T role crewman T role pilot Crewmen/Pilots: Some vehicle require a special kit to be driven/piloted
Vehicle people icon Carrying capacity
Vehicle tickets icon Ticket value
Vehicle timer icon Respawn timer
  • Please refrain, unless absolutely necessary, to reproduce any of the numberical stats shown on the infosheet as wiki text on wiki pages. We only want to maintain those stats on the infosheets and not on 10 other wiki pages because someone has also (unnecessarily) copied the values down. If you want to show vehicle stats, just show the infosheet.
  • When updating an infosheet with the latest stats, ALWAYS re-upload it as a new version over the current infosheet (use "Upload a new version of this file"). NEVER upload it as a new image under a different file. NEVER.
  • NEVER create duplications of these infosheets, e.g to paste two infosheets together next to each other and reuploading it as a new image. We have to maintain one unique copy of each infosheet only. If you want to combine multiple images, use a table and the unique infosheets. Example:
Armored Technical DHsK Infosheet
Technical Armed Statistics

Background: The infosheets are currently created and managed by the Editorial, hence if you notice an incorrect, outdate or missing infosheet, let them know. They created a Photoshop project with all vehicle images and text overlays. Most vehicle pictures were created using the Squad SDK or taken from OWI artwork. As font we use the Squad Font. In the long-run, the Editorial want to make this Photoshop project available via GitHub, so anyone could update the infosheets.

Infoboxes[ | ]

Infoboxes are used on Weapon, Vehicle, Equipment and Faction pages to help structure the information provided. Each of the following can be acted by:

Tip: If you go to the template page and "Tools / What links here", you can see which pages use this infobox.

Tip: All infobox templates belong to Category:Infobox templates

Faction[ | ]

Link to edit template: Template:Faction infobox

{{Faction infobox
| name =
| image =
| uniform = 
| theaters = 

Vehicle[ | ]

Link to edit template: Template:Vehicle infobox

{{Vehicle infobox
| image =
| armaments =
| crew =
| respawn timer =
| ticket value =

Map[ | ]

Link to edit template: Template:Map infobox

{{Map infobox
| image =
| maplength = 

Weapon[ | ]

Link to edit template: Template:Weapon infobox

{{Weapon infobox
| image =

Templates[ | ]

Here are the most frequently used Templates:

How to use a template? Just add {{template-name}} to your wiki page (for notice templates usually at the very top of a wiki page). Some templates use optional or mandatory parameters - view the templates for their documentation.

Categories[ | ]

Categories (background info) are a useful way to group pages together in order to find them later. We frequently use the following categories. Please use the correct category(s) when creating new pages or templates.

As a rule of thumb: ALL pages MUST belong to one category (and ideally all media files too); it's also ok if a page belongs to several categories. Some sub-categories should be grouped into over-categories (example: Category:Vehicle infosheets is a sub-category of Category:Vehicles).

How to add a category to a wiki page or media file? Easy. Just "source edit" the page and add the following line with the correct category at the end:

[[Category:Vehicle infosheets]]

How to create a sub-category? Easy. Just "source edit" the child category and add the parent category the same way you add a category to a page.

Server Troubleshooting[ | ]

When working on Server Troubleshooting, please remember the following guidelines:

  • #General guidelines apply too, so please check them out.
  • Give a new issue a short and as descriptive page title as possible; describes the problem (not the solution or cause)!
  • To make your life much easier, you can copy this template into your new page - it will take care of most of the following points.
  • Add the template {{ServerTroubleshooting}} at the very top of the page (it will automatically add your new pages the category Category:Server Troubleshooting).
  • Next, describe what the problem looks like; do not yet describe the cause(s) or solution(s).
  • Next, create a new heading (level 2) for each possible cause and describe the root cause and how it can be diagnosed.
  • Next, describe the solution. If the solution differs for different platforms, create a new heading (level 3) for each of the platforms.
  • If you can, use screenshots to complement your description. You can also link to external websites or embed YouTube videos with detailed instructions if that is useful.
  • If the cause and solution has already been described on another issue page, just link to it - do not duplicate instructions multiple times.
  • Please do not duplicate information/instructions already found on Server Installation, Server Configuration or Server Administration - just link to the appropriate section there.
  • If there are similar issues, you can link to them under "See also" at the end of the page.
  • After your issue page is completed and saved, please add all "cause and solutions" sections from your new issue page also into the tab "Common Solutions" on Server Troubleshooting under the appropriate headings.

Modding[ | ]

You fill find extensive information on how to create mods for Squad on this wiki. There will also be places on the wiki to promote your mods. However, the Squad Wiki will not include newly created assets, e.g. vehicles, weapons, factions, etc. The Squad Wiki focuses on the vanilla Squad game.

Please add all modding pages and uploaded images related to modding in the Category:Modding.

Squad font[ | ]

This wiki uses the offical Squad font: Roboto Condensed

Squad colors[ | ]

The following colors are featured in-game for certain icons, fonts or other elements. We use the same colors for the same context on the wiki.

Usage RGB code (hex) Example
Squad yellow ffc200
Local Voice 00BFFF
Command Channel e1e1d6
Fireteam Alpha / Squad Channel 32CD32
Fireteam Bravo ffae00
Fireteam Charlie c77dde
Fireteam Delta ?

Other wiki's style guides[ | ]

Here you will find a list of wiki style guides from other wikis: