UESPWiki:Spin-off Series Completion Project

The Spin-off Series Completion Project is a project aimed at fully documenting the several spin-off games in the Elder Scrolls series by bringing old articles up to standard and creating pages for overlooked or hard-to-get information.

For similar projects focused on Shadowkey and Legends, see the Shadowkey Documentation Project and Legends Namespace Completion Project respectively. For projects about ESO, see Online Quest Project and Online Collectible Images Project

Project Overview
The wiki's coverage of the spin-off games ranges from inadequate to pitifully incomplete. These games include Battlespire and Redguard, which have received little to no attention in recent years, and the four released Travels games, which have been extensively documented but left incomplete. These games are not widely available and are largely incompatible with modern software, meaning that documentation is limited and difficult. This project aims to provide a list of tasks which need to be completed to bring the spin-off namespaces up to par with the rest of the wiki's content.

Task List
Battlespire
Place pages: This information is strongly tied to the levels, and is currently integrated into the quest walkthroughs. By significantly shrinking the walkthroughs to be more concise, the place info can be migrated to a separate page with more detailed descriptions and images.
Images: Battlespire images are severely lacking on the wiki. Unique images licensed to UESP would be preferable to images taken from other sites/official images, but all are acceptable.
Each labeled point on the walkthrough maps now has at least one image, but there are still many opportunities for more. 
Dialogue: Extracting all lines of dialogue is a top priority. Recording it in game is doable (as evidenced by the folks over at TIL), but would be incomplete due to multiple choice and possible errors during transcription.
NPC and creature dialogue is complete, but should be checked in-game.
Game data: Extracting information straight from the game files will likely be necessary for this.
Items: Fill in missing information.
Stats: Investigate damage formula, jumping, etc.
Improve quest pages: After place pages are created, quest articles will likely need to be overhauled.
Multiplayer information
A lot of this has now been documented but we are still missing pages on the Team v Team maps.

Redguard
NPCs: Each NPC needs an introduction with the following information: race, location(s), occupation, and quest involvement. Their infobox should include location(s), race, gender, possibly faction, and if they can be fought, attack and health data. Related quests, notes, and bugs come after the introduction. Finally, all dialogue should go at the bottom of the page. There are five generic NPC classes that do not follow this convention, but still have dialogue.
Health and attack data is missing.
 : Every line of dialogue should be documented on the relevant NPC's page. Each topic has a section and its subtopics are below it. For clarity, the spacing between topics is 2 spaces, whereas subtopics are separated with 1. If a topic does not appear the first time you talk to an NPC, it should have the conditions for unlocking it in parentheses. If it disappears once asked, note that as well. Subtopics that appear because of their topic do not need to include any conditions. Responses that span multiple lines only have an end quote on the last line. Cyrus' responses are bold and the NPC's responses are in italics. As an example, see Gerrick.
 : Rather than have dialogue from scenes duplicated on NPC pages, the scenes an NPC features in should be included just above the dialogue section. Below this should be a short summary of what they say or do.
 : Creatures are not as detailed as NPCs so individual pages are unnecessary unless they have dialogue.
 : Faction pages need an overview of their history as described in the game.
 : Quests should be rewritten in a straightforward paragraph format. If the quest has a map, refer to the letters for simpler directions. As an example, see Escape the Catacombs.
 : Many Redguard images have the interface and Cyrus in the way. Cyrus should only be visible if he is somehow relevant to the picture.
Place pages: All notable places are documented on  with a short summary. Places with an interior like Gerrick's Goods have enough detail to justify a descriptive page. These should include the location, occupants, and information about the exterior and interior. Any objects Cyrus can interact with must be noted along with any dialogue he says (except item descriptions). Redirects have been created for all potential pages and can be found here.
Jail, Old Quarter, and League Hideout are not done.
 : Two pages with mostly the same content exist: First Time Players and Hints. They must be completely rewritten with an emphasis on clarity and usability. Spoilers should be avoided in First Time Players, but not in Hints. Other distinctions can be found by looking at Morrowind (1, 2), Oblivion (1, 2), and Skyrim's (1, 2) similarly named articles.

Stormhold
Leveling
Attributes/Skills
Game data
 : Maps are generated pseudorandomly. May not be possible to document.
Quest walkthrough
Diseases: All information about these is missing.
Bestiary:   Needs game data.

Dawnstar
Leveling
Attributes/Skills
Game data
 : Maps are generated pseudorandomly. May not be possible to document.
 
Page has been completed as of October 2019‎.
 
Page has been completed as of November 2019‎.

Oblivion Mobile
Leveling
XP System
Attributes
Place pages
Maps

Necessary Tools
The most important tool is a copy of the games. Note that none of these are open-source, and they weren't very popular when they were released, so it will be difficult to actually find copies of the games.

The UESP does not condone piracy.

Update 26/8/2015: Battlespire and Redguard are currently available for digital purchase at GOG.com.

DOS Games
In order to play Battlespire or Redguard, you need either:
An old computer with a copy of Windows 95/98 (because a newer computer will be too fast, due to the inability to slow down execution speed)
A modern, relatively powerful computer running DosBox.
For more information on running either game, read this article.

Mobile Games
In order to play Stormhold, Dawnstar, or Oblivion Mobile you need either:
A Java-enabled cell phone (note that iPhones do not work);
An emulator, such as Kemulator.

In addition, in order to play Shadowkey, you need either: 
A Nokia N-Gage (recommended) or N-Gage QD;
An emulator, as described on the guide page.

The advantage of running the mobile games on their intended devices is that they will have maximum stability and require no configuration. The advantage of running them on an emulator is the ability to take screenshots, speed hacks, and other standard emulator features. For the purposes of this project, an emulator is preferred. It should be noted that the save function in Dawnstar and Stormhold may not work on an emulator.

Project Members
AldmerProfessor
DCSG
Dillonn241
Echo
Gaggle Zealot
Jak Atackka
Legoless
Reath
SarthesArai
Savor Valandros
Thal-J

Project Ribbon
Anyone taking an active part in the project may use the project  :