|
|
| (41 intermediate revisions by 12 users not shown) |
| Line 1: |
Line 1: |
| {{cleanup}} | | {{subpage|move info to specific guide pages}} |
| {{All Game Nav|game=StrategyWiki:Guide}} | | {{Header Nav|game=StrategyWiki:Guide}} |
|
| |
|
| After the initial planning stage, the next issue is how to organise the content. Unlike Wikipedia, StrategyWiki uses subpages (e.g. Game Name/Walkthrough). Unlike traditional walkthroughs, information in StrategyWiki guides should be separated into subpages when it reaches a certain length. While most games will require three or four pages at the very least, some games, like [[Sega Swirl]], are simple enough that they can be covered on a single page. | | After the initial planning stage, the next issue is how to organise the content. Unlike traditional walkthroughs, information in StrategyWiki guides should be separated into subpages when it reaches a certain length. While most games will require three or four pages at the very least, some games, like [[Sega Swirl]], are simple enough that they can be covered on a single page. |
|
| |
|
| ==Single-page vs. multi-page==
| | Unlike Wikipedia, StrategyWiki uses subpages (e.g. Game Name/Walkthrough). All pages must be sub-pages of the main game page. |
| {|
| | |
| |width=50% valign=top|
| | ==Capitalisation== |
| The single-page layout covers absolutely everything on a single page. Such games might include:
| | As with [[StrategyWiki:Guide/Layout#Headings|headings]], page names should be capitalised correctly, with the main page of a guide taking the game's name, and sub-pages taking [[wp:sentence case|sentence case]], apart from '''Table of Contents''' which is special. So, for example, a page on a fictional quest called "The gates of Valhalla" would be ''Game name''/'''The gates of Valhalla'''. The only exception to this rule is if the quest name is referred to within the game with different capitalisation, the page titles here can be capitalised to match. |
| * some [[racing]] games
| | |
| * many [[Puzzle]] games
| | For information on the benefits of using sentence case in titles, see [[wp:Title case#Sentence case versus title case|Wikipedia]]. |
| * some [[platform]]ers
| |
| * games with very simple gameplay
| |
| If the game can be feasibly covered in full on a single page, add the <code>onepage=true</code> variable to {{tl|All Game Nav}}; this will disable the [[#Walkthrough|Walkthrough]] and [[#Table of Contents|Table of Contents]] links that appear by default.
| |
| ||
| |
| |width=50% valign=top|
| |
| The multi-page layout starts with an introduction page and can feature anywhere from four to 40 subpages, each of which focusses on a single aspect of the game. Such games include: | |
| * [[RPG]]s
| |
| * [[Adventure]]/[[Action-adventure]] games
| |
| * [[FPS]]es
| |
| * games with many levels
| |
| If the game is too complex to feasibly be covered on a single page it will need a [[#Table of Contents|Table of Contents]] linking to all the subpages it encompasses.
| |
| |}
| |
|
| |
|
| ==Types of subpages== | | ==Types of subpages== |
| There are many types of subpages that make up the guide as a whole. The most common types are explained below. | | There are many types of subpages that make up the guide as a whole. The most common types are explained below. |
|
| |
| ===Getting Started===
| |
| An important page in many guides. This may go under different names depending on the game, but will always serve the same purpose: to describe the controls, gameplay and other general features of the game. New and returning players should be able to read or even skim this page to get a general refresher on the bare minimum of what's involved. Even things covered in the manual should still be covered in case players don't have the manual for whatever reason (sometimes, re-releases don't even include a manual).
| |
|
| |
| Complicated games might need to have this separated into different pages, but a non-linked "Getting Started" header can still be used on the [[#Table of Contents|Table of Contents]].
| |
|
| |
| ===Controls===
| |
| A portion of every guide is often dedicated to explaining a game's controls. Unless included in [[#Getting Started|Getting Started]], this page is crucial. This information should be roughly modeled after an instruction booklet. Buttons should be listed with a button template wherever possible, but if there is no image for the button, it should listed in '''bold''' in bulleted form, followed by its function(s), separated by a semicolon (;). Any notes about a specific button or action are bulleted below. It should be noted whether games allow button customization, and the default configuration settings for each game should be used. The controls should be listed in the following sort of format:
| |
| * {{gc|Neutral|Control}}: Move character
| |
| * {{gc|A}}: Jump
| |
| ** The height of the jump varies with how long {{gc|A}} is heald
| |
| * {{gc|B}}: Attack; block
| |
| ** Press {{gc|B}} at the same time as your opponent to block an attack.
| |
| For lists of large but irregular numbers of buttons, consider listing the description first and the buttons second. You can also use tables to line things up better.
| |
|
| |
| If no template exists for this system, or you don't know what its controls are, use <code><nowiki>{{needcontrols|System Name Here}}</nowiki></code> to tag it and write out the buttons in full like this:
| |
| * '''Analog Stick''': Move character
| |
| * '''A Button''': Jump
| |
| ** The height of the jump varies with how long the A Button is held.
| |
| * '''B Button''': Attack; block
| |
| ** Press the B Button at the same time as your opponent to block an attack.
| |
|
| |
| Some games use the mouse and keyboard for control ({{tl|mouse}} and {{tl|kbd}} exist for this purpose). Some games also distinguish the typing of lowercase and uppercase letters. For example, in [[NetHack]], pressing {{kbd|z}} zaps a wand while {{kbd|Z}} zaps a memorised spell. If the capitalisation does not matter, list the key with a capital as this is the way it is displayed on a real keyboard.
| |
|
| |
| ===Walkthrough===
| |
| The heart of many guides is the walkthrough. For simple games, this page should include all the levels or stages needed to finish the game, covered in as much detail as necessary.
| |
|
| |
| If the game is very complicated or the descriptions become very long it should instead cover only the introduction—e.g. the opening cutscene or character creation (unless that is involved enough to earn its own subpage)—or perhaps the first level of the game. The aim is to make the automatic Walkthrough link on {{tl|All Game Nav}} as useful as possible.
| |
|
| |
| Other walkthrough pages should be subpages of the main guide (e.g. Game/Level 1) rather than of the walkthrough (e.g. Game/Walkthrough/Level 1). If it has an official name you might consider using that instead a generic numbered page.
| |
|
| |
| Remember to put {{tl|All Game Nav}} at the top and {{tl|Footer Nav}} on the bottom so that readers can easily progress through the pages.
| |
|
| |
| As a general rule, if something is not necessary to complete the game ("complete" in this sense means seeing the ending if there is one) it can be considered a secret or sidequest, and should be covered elsewhere (although mentioning it with {{tl|sidebar}} is still a good idea).
| |
|
| |
| ===Table of Contents===
| |
| While the [[#Walkthrough|walkthrough]] is the heart, the Table of Contents is the veins. It should link to '''all''' the pages used in the guide to enable quick access from anywhere to anywhere else.
| |
|
| |
| First of all, the ToC should be generic, simple and similar to other ToCs. For example, you should have a '''Getting Started''' (followed by basics) and '''Walkthrough''' page (an explanitory page followed by sections) and then an '''Appendices''' section with extra information. Usually controls, and background information is listed under the Getting Started section, guide areas are listed under the walkthrough sections and lists, maps and other information that wouldn't be considered one of the other sections goes in the Appendices section. Specific guides are also usually listed under Appendices (for example [[Mega Man 7/Boss guide]]).
| |
|
| |
| Page links should be visually tiered, e.g.:
| |
| * Controls
| |
| * Walkthrough
| |
| ** Level 1
| |
| ** Level 2
| |
| * Items
| |
| However this is only the layout; as a general rule, the actual page locations only need to be tiered once (e.g. Game/Level 1 instead of Game/Walkthrough/Level 1). This prevents pages from having complicated titles (e.g. Game/Walkthrough/Core Missions/Ric/Bombs Away, Baby) and also makes linking easier.
| |
|
| |
| To get you started, here are some generic ToC layouts for various genres:
| |
|
| |
| <div style="width: 25%; float: left;">
| |
| '''Adventure'''
| |
| * Characters
| |
| * Commands
| |
| * Game Overview
| |
| * FAQs
| |
| * Walkthrough
| |
| * Items
| |
| * Secrets
| |
| </div><div style="width: 25%; float: left;">
| |
| '''RPG'''
| |
| * Characters
| |
| * FAQs
| |
| * Walkthrough
| |
| * Sidequests
| |
| * Enemies
| |
| * Items
| |
| * Weapons
| |
| * Armor
| |
| * Spells
| |
| </div><div style="width: 25%; float: left;">
| |
| '''Racing'''
| |
| * Controls
| |
| * Cars
| |
| * Tracks
| |
| * Cups
| |
| </div><div style="width: 25%; float: left;">
| |
| '''Fighting'''
| |
| * Controls
| |
| * Moves
| |
| * Tactics
| |
| * Tips and Tricks
| |
| </div>
| |
| {{-}}
| |
|
| |
| ===FAQ===
| |
| A FAQ (Frequently Asked Questions) is a list of common questions players have asked (or might ask). These have gone out of style in the last few years, and gamers are now in the habit of looking for answers in the appropriate section. If the game is particularly complicated or has specific information that is constantly asked (e.g. which characters are in which version, or if the existence of a nude skin is a hoax) a FAQ might still be a good idea, but as a rule any FAQ entries that could be rewritten and placed on a subpage instead should be. Because the FAQ will be read by players at any stage in the game, use {{tl|spoiler}} for spoilers of any sort.
| |
|
| |
| ===Optional activities===
| |
| Things that are not required for completion of the main storyline go on pages like these. Activities that are required at one point of the walkthrough but can be optionally done at other times as well should be covered in both places. If the game has a lot of sidequests you should of course split the page accordingly.
| |
|
| |
| ===Move lists===
| |
| As a rule, only fighting games and beat-'em-ups have these. Handle beat-'em-up move lists much the same way as [[#Controls|controls]] pages. Fighting games, however, are handled differently. Unlike most pages, move lists are instead placed at Move Lists/Company Name/Game. Check [[:Category:Move lists]] to see the ones already made; if a variant of the game you're writing for already has some moves that are performed identically you can just duplicate them from there. You will also need to create a character page in the format Move Lists/Company Name/Character. Talk to [[User:Procyon|Procyon]] for more information regarding Move Lists standards.
| |
|
| |
|
| ===Strategy=== | | ===Strategy=== |
| Mostly used for strategy/tactical/simulation/squad-based games, this page should provide general strategies. Mission-specific strategies should probably be covered on the page for that mission. It's also useful to spread a few handy reminders (e.g. "remember, Night Elves deal only half damage against Fell Orcs unlike the rest of their race") throughout the walkthrough. | | Mostly used for strategy/tactical/simulation/squad-based games, this page should provide general strategies. Mission-specific strategies should probably be covered on the page for that mission. It's also useful to spread a few handy reminders (e.g. "remember, Night Elves deal only half damage against Fell Orcs unlike the rest of their race") throughout the walkthrough. |
|
| |
|
| ===Cheats/Codes=== | | ===Move lists=== |
| This section can have either title (as they are mostly synonymous). As a general guideline, if a game has only button-press and cheat device codes, call the page Codes; if the game has glitches and other sorts of non-cheat cheats call it Cheats. As a rule patch codes cannot be copyrighted, so taking them from other sites is OK as long as you describe the code's function in your own words.
| | As a rule, only fighting games and beat 'em ups have these. Handle beat 'em up move lists much the same way as [[#Controls|controls]] pages. Fighting games, however, are handled differently. Move lists are typically found in games that have a series, such as [[Street Fighter II]]. Move lists are put in two places: |
| | | # The Moves page for the game for which the list applies (e.g. [[Street Fighter Alpha 2/Moves]]). This page includes the complete move lists for the game in question. |
| ===Lists===
| | # The character page for the series (e.g. [[Street Fighter Alpha/Ryu]]). This page includes biographical and possibly technical information about the character in question, as well as all of the move lists that apply to this character in the particular series. The move list is transcluded to this page using the {{t|Movelist}} template to prevent the need to copy the information in two places. |
| Lists are very helpful, and should usually be kept separate from any other page so they can be easily accessed from anywhere via the [[#Table of Contents|Table of Contents]]. As a rule, pages with large amounts of statistics should be presented in tables. If the lists become extremely long consider splitting by type. As a general rule, use an identical layout for each entry or section, leaving parts blank that don't apply to that thing.
| |
|
| |
|
| ==Foreign Language guides== | | ==Non-English guides== |
| At present, StrategyWiki only hosts English-language guides. If enough interest is shown in other languages, support for them can be added much like at Wikipedia. | | At present, StrategyWiki only hosts English-language guides. If enough interest is shown in other languages, support for them can be added much like at Wikipedia. Note that this doesn't mean you can't write a guide for a game which isn't in English (although that might be hard) — it just means that currently, all guides have to be written in English. |
|
| |
|
| {{Footer Nav|game=StrategyWiki:Guide|backpage=Research|backname=Researching more information|here=Organising the pages|nextpage=Talk pages|Discussing major issues}} | | {{Footer Nav|game=StrategyWiki:Guide|prevpage=Researching more information|nextpage=Adding more information}} |
Split into subpages
This page needs to be split into subpages. move info to specific guide pages
Please add some links to the Table of Contents and split this page to separate pages, then remove this template.
After the initial planning stage, the next issue is how to organise the content. Unlike traditional walkthroughs, information in StrategyWiki guides should be separated into subpages when it reaches a certain length. While most games will require three or four pages at the very least, some games, like Sega Swirl, are simple enough that they can be covered on a single page.
Unlike Wikipedia, StrategyWiki uses subpages (e.g. Game Name/Walkthrough). All pages must be sub-pages of the main game page.
Capitalisation[edit]
As with headings, page names should be capitalised correctly, with the main page of a guide taking the game's name, and sub-pages taking sentence case, apart from Table of Contents which is special. So, for example, a page on a fictional quest called "The gates of Valhalla" would be Game name/The gates of Valhalla. The only exception to this rule is if the quest name is referred to within the game with different capitalisation, the page titles here can be capitalised to match.
For information on the benefits of using sentence case in titles, see Wikipedia.
Types of subpages[edit]
There are many types of subpages that make up the guide as a whole. The most common types are explained below.
Strategy[edit]
Mostly used for strategy/tactical/simulation/squad-based games, this page should provide general strategies. Mission-specific strategies should probably be covered on the page for that mission. It's also useful to spread a few handy reminders (e.g. "remember, Night Elves deal only half damage against Fell Orcs unlike the rest of their race") throughout the walkthrough.
Move lists[edit]
As a rule, only fighting games and beat 'em ups have these. Handle beat 'em up move lists much the same way as controls pages. Fighting games, however, are handled differently. Move lists are typically found in games that have a series, such as Street Fighter II. Move lists are put in two places:
- The Moves page for the game for which the list applies (e.g. Street Fighter Alpha 2/Moves). This page includes the complete move lists for the game in question.
- The character page for the series (e.g. Street Fighter Alpha/Ryu). This page includes biographical and possibly technical information about the character in question, as well as all of the move lists that apply to this character in the particular series. The move list is transcluded to this page using the {{Movelist}} template to prevent the need to copy the information in two places.
Non-English guides[edit]
At present, StrategyWiki only hosts English-language guides. If enough interest is shown in other languages, support for them can be added much like at Wikipedia. Note that this doesn't mean you can't write a guide for a game which isn't in English (although that might be hard) — it just means that currently, all guides have to be written in English.
