Download the Liquipedia app here!Download the Liquipedia app to follow Brood War!Want personalized updates on Brood War esports? Download the Liquipedia app on iOS or Android to never miss your favorite tournaments and matches!
Liquipedia app match pages updated! Liquipedia app match pages are overhauled! Download on Android or iOS! Liquipedia app's match pages got completely revamped with game data, standings, VODs and more! Download the the latest version on iOS or Android and read our update blog here.

Help:Strategy

From Liquipedia StarCraft Brood War Wiki

Overview[edit]

This tutorial focussing on creating strategy articles. It will list the required Wiki-Code with explanations, the basic structures, a general overview of policies and style guides.

to view an example for a standard strategy guide, see also: Example Strategy Article


Sections and Boxes[edit]

A strategy guide should have following sections and Boxes:


  1. Strategy Infobox
  2. Overview
  3. Build Order Table
  4. Execution
  5. Counters
  6. Notable Maps
  7. Notable Games


Information about the content and the function of each section will be explained below. Sections and a Table of Contents is automatically created when the Wiki-Code for headers are used:

==Section 1==
==Section 2==
===Section 2.1=== 
===Section 2.2===


The Infobox[edit]

The Infobox offers a brief overview about the strategy and futher, less important information. Nonetheless, it should be added, as it also allows a reader to quickly navigate from one article to each race's overall strategy page.



Overview Section[edit]

The Overview section should give a very short glimpse on the following article. It should have following information in a few sentences:

  • The name of the article in bold.
  • The match up for which the strategy was designed.
  • The underlying goal of the strategy / Build Order.
  • Whether or not this Build Order can be categorized as "modern"/"still viable", "outdated" and/or "risky" or "standard". This categorization helps beginners to understand the context and the most important parts of a strategy.


Build Order Box[edit]

The Build Order Box can theoretically be left out for very abstract strategies. However, it still is an effective tool to list even abstract tipps. The box itself is a Template, which generates a pre-designed Table, linking to a tutorial about Build Orders in general and offers an in-built reference-section.





Wiki-Code[edit]



Filling out the Table[edit]

The Information in the table either lists a full Build Order or Abstract Timings in case of late game strategies. It usually follows the format of text based Build Order instructions given in forum posts or external sources. However, a few tipps and conventions are in place.

  • Bullet Point Lists are used to write instructions (* 8/9 - Pylon)
  • The standard format is "Supply Count - Instruction" (8/9 - Pylon)
    • The Supply Count is should always be fully written, not only one number, but both if possible (8/9 opposed to only 8)
    • Unit, Building and Upgrade names can be linked when they appear for the first time (e.g. Pylon)
  • Timing based instructions are always marked with an @ (@100 Gas - Lair)
  • Positions on the map should always be written out (at Natural Expansion)
  • Instructions should be as precise as possible, while using as little text as needed (8/9 - Pylon at Natural Expansion opposed to 8/9 - Pylon build somewhere in the Natural Expansion)
  • The entire Build Order should be written in a first draft, clearifications and references can be added afterwards (see below)
  • If instructions happen simultaneously,


Clearifications and References[edit]

Some instructions need further clearifications. A simple example would be a clearification when to skip workers or when to scout. This information does not belong in the basic instruction text. Instead references can be added, which will create a footnote at the bottom of the table.


Wiki-Code - References
8/9 - Pylon<ref name=WorkerSkip>Stop producing Worker</ref>
  • the <ref name= > starts the footnote
  • the name= adds a name to the footnote. Use Roman Symbols (and optionally a number; numbers only and other symbols might not work). The name of the footnote will not be displayed, instead a number will be generated, which links to the foot note text.
  • in between <ref name=> and </ref> the text of the footnote will be written.
  • the </ref> tag closes a reference
  • references are written after the bullet points / the instructions


Sometimes a Build Order splits at a special timing; usually whenever a player has two or more options to continue from his Build Order. It is up to the editor to list all of them in one article or to create own articles for each follow-up. If the editor choses to add both options, he can either add two Build Order Tables or split the Build Order Table in half with the help of Columns. The first option is self explaining.

Wiki-Code - Columns
  • Wiki-Code: {{Col}}Build List{{col-break}}List2{{EndCol}}
    • {{Col}} starts a new column
    • {{col-break}} starts the second column
    • {{EndCol}} ends the column
  • If more columns are added, it might be neccessary to adjust the width of the Build Order table


Execution Section[edit]

The Execution Section usually starts by picking up the red line started in the Overview Section. One or two sentences explain the underlying idea of a Build Order. Afterwards the list of instructions written down in the Build Order Box are explained with more details. The goal is to stay on point and not list all possible scenarios. Explanations should focuss on which situation should be forced by the player following the Build Order List and what situations to avoid.

If a Build Order is rather complex or only gives instructions about the early game, another section for "Transitions" can be added. It is pivotal to only explain the most common cases and not every possible outcome.

A few general rules:

  • The text should be easy to understand. Specific Terms should either be linked or explained or linked and explained
  • The text should be small enough to underline the point without boring the readers
  • The instructions list helpful tricks for beginners if possible


Counters Section[edit]

The Counters section is straight forward and only needs few lines of text. It should, combined with the Execution and the Overview Section, help a beginner to understand if a strategy is still viable if other counters are to be expected. Counters explain in which situations the strategy works best and worst.

Notable Maps Section[edit]

Maps supporting the strategy especially well or making the strategy nearly impossible to perform should be listed. However, popular maps change over time, hence abstract concepts might be explained instead of simply adding a list of good/bad "modern" maps.

Notable Games Section[edit]

This section should simply give a few examples for players to watch. Either replays or VODs can be added. In most cases the "Replay Box" is used.


No thumbnail available
Date:
Patch:



Optional Sections[edit]

Theoretically, a few more sections can be added to the article.

  1. "Historical Context": This usually features less important information about the players, who developed and popularized a strategy. It can list a context describing how the strategy changed the meta game.
  2. "External Links": In these links to longer Build Order guides on forums can be added.
  3. "Related Articles": A list of articles on the Wiki related to the guide. E.g. "Reaver Harassment" for "Corsair/Reaver".