%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
% Stylish Article
% LaTeX Template
% Version 2.0 (13/4/14)
%
% This template has been downloaded from:
% http://www.LaTeXTemplates.com
%
% Original author:
% Mathias Legrand (legrand.mathias@gmail.com)
%
% License:
% CC BY-NC-SA 3.0 (http://creativecommons.org/licenses/by-nc-sa/3.0/)
%
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

%----------------------------------------------------------------------------------------
%	PACKAGES AND OTHER DOCUMENT CONFIGURATIONS
%----------------------------------------------------------------------------------------

\documentclass[fleqn,10pt]{SelfArx} % Document font size and equations flushed left
\usepackage{mathtools}
\usepackage{amssymb}
\usepackage{outlines}
\usepackage{enumitem}
\usepackage{units}  % Required for slanted fraction nicefrac{}
\usepackage{attrib} % Required for quotation attribution
\usepackage{url}
\usepackage{lipsum} % Required to insert dummy text. To be removed otherwise



%----------------------------------------------------------------------------------------
%	COLUMNS
%----------------------------------------------------------------------------------------

\setlength{\columnsep}{0.55cm} % Distance between the two columns of text
\setlength{\fboxrule}{0.75pt} % Width of the border around the abstract

%----------------------------------------------------------------------------------------
%	COLORS
%----------------------------------------------------------------------------------------

\definecolor{color1}{RGB}{0,0,90} % Color of the article title and sections
\definecolor{color2}{RGB}{0,20,20} % Color of the boxes behind the abstract and headings

%----------------------------------------------------------------------------------------
%	HYPERLINKS
%----------------------------------------------------------------------------------------

\usepackage{hyperref} % Required for hyperlinks
\hypersetup{hidelinks,colorlinks,breaklinks=true,urlcolor=color2,citecolor=color1,linkcolor=color1,bookmarksopen=false,pdftitle={Title},pdfauthor={Author}}

%----------------------------------------------------------------------------------------
%	ARTICLE INFORMATION
%----------------------------------------------------------------------------------------

\JournalInfo{Kansasfest, July 2014} % Journal information
\Archive{Rockhurst University --- Kansas City, Kansas USA} % Additional notes (e.g. copyright, DOI, review/research article)

\PaperTitle{\emph{STAR SAGA: ONE Beyond the Boundary}\\Play-by-Email (or Solo) Using the VASSAL Engine} % Article title

\Authors{Michael Sternberg} % Authors
%\affiliation{\textsuperscript{1}\textit{Arlington Texas, USA}} % Author affiliation
%\affiliation{*\textbf{Corresponding author}: john@smith.com} % Corresponding author

\Keywords{} % Keywords - if you don't want any simply remove all the text between the curly brackets
\newcommand{\keywordname}{Keywords} % Defines the keywords heading name

%----------------------------------------------------------------------------------------
%	ABSTRACT
%----------------------------------------------------------------------------------------

\Abstract{\emph{STAR SAGA: ONE Beyond The Boundary} and its sequel are members of a class of computer game that is difficult to play without possessing the original game materials. This document proposes using the VASSAL engine to simulate the use of the game board and paragraph booklets needed to play the game.}

%----------------------------------------------------------------------------------------

\begin{document}

\flushbottom % Makes all text pages the same height

\maketitle % Print the title and abstract box

\tableofcontents % Print the contents section

\thispagestyle{empty} % Removes page numbering from the first page

%----------------------------------------------------------------------------------------
%	INTRODUCTION
%----------------------------------------------------------------------------------------

\section*{Introduction} % The \section*{} command stops section numbering

\addcontentsline{toc}{section}{Introduction} % Adds this section to the table of contents

\emph{STAR SAGA: ONE Beyond the Boundary} is a hybrid role-playing/tabletop/computer game developed by Rick Dutton, Walter Freitag, Andrew C. Greenberg, and Mike Massimilla and released in 1988 for the Apple II/IIgs family of computers, the IBM PC and its clones, and the Tandy 1000 \cite{SS1AD}. Due to the scarcity of surviving physical copies of the game and its reliance on a hefty set of non-digital components (booklets, maps, etc), a present-day Apple II user may miss the opportunity to explore this unique game design.

One solution proposed here is to use the VASSAL Engine. VASSAL is a modern software system for playing computerized adaptations of traditional tabletop board games. It can be used to provide access to the non-digital components, maintain the state of the game board, and allow a multiplayer game to be conducted across the Internet (Play by Email).

The purpose of this document is to guide the reader through the steps involved in acquiring, configuring, and using the software components needed to conduct a game of \emph{STAR SAGA: ONE Beyond the Boundary} using an Apple II emulator and a \emph{STAR SAGA: ONE} module for VASSAL.

%----------------------------------------------------------------------------------------
%	HISTORICAL CONTEXT
%----------------------------------------------------------------------------------------

\section{Historical\ Context}

\subsection{Real-World Role-Playing Games}
By the late 1970's and early 1980's, role-playing games such \emph{Dungeons \& Dragons} had become a cultural phenomenon. Some people began finding ways to take the role-playing game out into the real world. At MIT, participants in the \emph{Assassins' Guild} played both the role of hit man and target with the campus providing the game's boundary. In 1981, a group in Boulder, Colorado asked the authors of \emph{Dream Park}, a science-fiction novel published the same year involving immersive, hologram-fueled role-playing games, to adopt the name of the book's the ruling committee, the International Fantasy Gaming Society, as the name for their own club.

\subsection{Society for Interactive Fiction}It was in this environment that university students, Walter Freitag, Michael Massimilla, and Rick Dutton, founded the Harvard Society for Interactive Literature in 1982. This was later shortened to the Society for Interactive Literature or SIL. The group innovated a theatre-style form of role playing game and in 1983 SIL began organizing weekend-long game events called Rekon (Recon-1, Rekon-2, etc) which were played at the Boskone science fiction conventions held in Boston. Two years later SIL would begin to host their own annual event, SILiCON, which, as of 2014, continues as Intercon \cite{OSTED98}.

\subsection{From SIL to Star Saga}
Just before Rekon-2, Michael Massimilla, had a chance encounter with Andrew C. Greenberg, creator of the \emph{Wizardry} series of computer adventure games, when both competed in a bridge tournament. Massamilla introduced Greenberg to Dutton and Freitag. This led to Greenberg attending Rekon-2 and sparked the idea to capture the experience in the form of a computer game. So Dutton, Frietag, Greenberg, and Massamilla set out to create a trilogy of computer role-playing games using some of the elements of Rekon. The first game of the trilogy was \emph{STAR SAGA: ONE Beyond the Barrier} \cite{SS1HG}.

\subsection{Critical Reception}
Reviews of the game ranged from favorable to enthusiastic with the highest accolades coming from \emph{Computer Gaming World}. Here are excerpts from several computer and game magazines that reviewed \emph{STAR SAGA: ONE - Beyond the Boundary}:
\begin{quote}
...Star Saga is a genre-buster. It can be compared to no other game on the market. The best way to describe Star Saga's playing experience is to compare it to participating in the \emph{Foundation} series of books by Issac Asimov. We're talking grand scale adventure here, folks.
\attrib{\emph{Computer Gaming World} August 1988 - pp. 30}
\end{quote}
\begin{quote}
$\star$$\star$$\star$$\nicefrac{1}{2}$  (of 5)\newline
Patience, the ability to read text and instructions, and a willingness to use the computer only as a record keeper are the keys to this game's enjoyment. After the first few turns, even the most addicted computerphile will enjoy this text and book-based adventure.
\attrib{\emph{Dragon} \# 142 - pp. 48}
\end{quote}
\begin{quote}
The game seems far more social event than a computer game, for much of its entertainment value comes from the interaction between players, not between human and computer.
\attrib{\emph{Compute!} August 1988 - pp. 60}
\end{quote}
\begin{quote}
CGG's \textbf{Special Award for Literary Achievement} goes to Masterplay for \emph{Star Saga One: Beyond the Boundary} - \emph{[Ed: This is the first time CGW has ever given an award for the fiction presented in a computer game.} Star Saga One \emph{is the most marvelously well-written adventure game ever presented on a computer. Although the game lacks any on-screen graphics, sound effects, or technical chrome, this humorous, challenging, frustrating, exciting, and addictive game holds its own as a benchmark of adventure gaming on the computer.]}
\attrib{\emph{Computer Gaming World} October 1989 - pp. 8}
\end{quote}



%----------------------------------------------------------------------------------------
%	THE GAME
%----------------------------------------------------------------------------------------

\section{The Game}

\subsection{Overview}
\emph{STAR SAGE: ONE Beyond the Boundary} is a turn-based, science fiction-themed game for one to six players. Each player chooses to be one of six available characters. The characters travel between different planets to trade goods, acquire resources, improve their spacecraft's capabilities, and progress through the game's narrative. A text-only  program called the Computer Game Master (or CGM) maintains the game's state. Players plot their moves using colored stone-like tokens on a game-board map and take turns entering their actions into the CGM. The program returns the results. Often this requires having the player read one or more narrative passages found in a set of thirteen booklets.

\subsection{Object of Game}
The players are assigned a set of goals unique to their chosen characters. These goals are intended to remain undisclosed to the other players and can only be completed by exploring and interacting with the game's universe. The game is won for the player when the character has completed its assigned goals. Play can continue for the other players who have not yet completed their goals.

\subsection{Original Game Components}
The original game included many physical components. \textbf{(See figure \ref{fig:components}.)} It would be meaningless to play the game without possessing these items (or facsimiles of these items).

\begin{itemize}[noitemsep] % [noitemsep] removes whitespace between the items for a compact look
\item (1) Host Guide / Player Reference Manual
\item (1) small map used during the tutorial phase
\item (1) large map used after the tutorial phase (not shown in figure \ref{fig:components}
\item (6) Colored tokens to indicate players' locations on map
\item (6) "Dear Player" cards  - starting point for the game
\item (6) Character biographies / tutorials
\item (2) 5.25" or (1) 3.5" floppy diskette
\item (13) Paragraph narrative books (labelled A-M) containing entries numbered 1-888
\item (1) Computer system instructions
\end{itemize}

\begin{figure*}[ht]\centering % Using \begin{figure*} makes the figure take up the entire width of the page
\includegraphics[width=\linewidth]{components}
\caption{Original Game Components}
\label{fig:components}
\end{figure*}

%----------------------------------------------------------------------------------------
%	SOFTWARE COMPONENTS NEEDED
%----------------------------------------------------------------------------------------

\section{Software\ Components\ Needed}

\subsection{Overview}
To conduct a game of \emph{STAR SAGA: ONE Beyond the Boundary} using digitized game components will require these items.

\begin{itemize}[noitemsep]
\item The VASSAL Engine
\item The VASSAL module for \emph{STAR SAGA: ONE}
\item Apple II or IBM PC DOS emulator
\item Disk images for \emph{STAR SAGA: ONE}
\end{itemize}

%-------------------    VASSAL

\subsection{VASSAL}
The VASSAL Engine is a contemporary, open source, cross-platform software system that enables people to play traditional tabletop board or card games by email or across the Internet. Modules for specific board games are downloaded from the Internet and added to your VASSAL game library.

There is no artificial intelligence inherently provided by VASSAL. The purpose for the system is to provide board game hobbyists a way to play against others without geographic restrictions. Initially created to enable play-by-email games of \emph{Advanced Squad Leader}, over time the engine has been generalized to support a vast number of games through community-created game modules.

VASSAL provides a graphical user interface for managing installed modules. Modules will normally contain a facsimile of the game board, game pieces, and/or cards. The movements of game pieces or the playing of cards, along with text-based chats are stored into a log file that is shared with the opponent. The opponent is able to play back the log file to advance the game to its current state, then record his/her own turn to be shared with the original player. And thus, log files are traded back and forth to progress the game to its conclusion.

%-------------------    GAME MASTER PROGRAM

\subsection{Game Master Program}
The tokens, game board, and narrative booklets provide the majority of the game's experience for the players. However it is \emph{STAR SAGA: ONE}'s Game Master program that manages the details of the game. It generates random events, provides an interface for players to enter their moves, returns the results of player actions, coordinates trades, etc.

The Game Master program was available for the four platforms listed in \textbf{Table \ref{tab:platforms}}.

\begin{table}[hbt]
\caption{Game Master Platforms}
\centering

\begin{tabular}{lll}
\toprule
Computer & Operating System & Media \\
\midrule
Apple II   & ProDOS 8  & (2) 5.25" diskettes \\
Apple IIgs & ProDOS 16 & (2) 3.5" diskette \\ 
IBM PC     & MS-DOS    & 5.25" or 3.5" diskettes\\
Tandy 1000 & MS-DOS & \\
\end{tabular}
\label{tab:platforms}
\end{table}

%-------------------    EMULATOR

\subsection{Emulator}
To host a game of \emph{STAR SAGA: ONE} requires running the Game Master program on a real or emulated computer. When playing a solitaire or multiplayer game where all participants are at the same physical location, then you are free to choose to run the Game Master program on a real computer or your favorite emulator and operating system. 

If organizing a multiplayer game to be played via email, you must select an emulator that that satisfies two conditions: 

\begin{enumerate}[noitemsep] 
\item the emulator includes a save state feature
\item the emulator is available for all participants' platforms / operating systems
\end{enumerate}

These two requirements are necessary because the Game Master's save function is only accessible at the start of each turn. Once any player begins their turn, the save game function is not available again until all the players have plotted their moves. See \textbf{Table \ref{tab:emulators}} for a list of commonly used emulators and whether a save state feature is currently available for each.

\begin{table}[hbt]
\caption{Emulators capable of executing the Game Master program}
\centering

\begin{tabular}{lllc}
\toprule
Emulator & Target & Native OS & Save State \\
\midrule
Virtual II    & II   & OSX & \checkmark \\
AppleWin      & II   & All\footnotemark[1]{} & \checkmark \\
JACE		  & II	 & All & \---\footnotemark[2]       \\
Linapple	  & II   & Linux & \checkmark \\
Sweet 16      & IIgs & OSX & \---       \\
Kegs/GSport   & IIgs & Linux/OSX & \--- \\
DOSBox        & PC   & All & \checkmark \footnotemark[3]

\end{tabular}
\label{tab:emulators}

\begin{enumerate}[noitemsep]
\item Using WINE under OS X or Linux
\item Possibly under development
\item Using Game Wizard Pro 32 Utility and Microsoft MS-DOS
\end{enumerate}

\end{table}

%----------------------------------------------------------------------------------------
%	STAR SAGA: ONE Mechanics Implemented in VASSAL
%----------------------------------------------------------------------------------------

\section{\emph{STAR SAGA: ONE} Game Mechanics in VASSAL}
\subsection{Overview}
This section concentrates on reviewing the game mechanics employed in the original game, such as player movement, taking notes, etc. and comparing these to each one's counterpart as implemented within the VASSAL module for \emph{STAR SAGA: ONE}.

%-------------------    GAMEBOARDS AND PLAYER TOKENS

\subsection{Game Maps and Player Tokens}
Two poster-like game maps were included with \emph{STAR SAGA: ONE}.  The smaller one, titled "Starweb" is used only during the tutorial phase. The larger map, titled "Document Two", is used throughout the remainder of game play. Each space on the map is defined by a colored and uniquely numbered triangle (or "trisector" in the game's idiom). Most trisectors are void. A few contain planets.

Each player's current location on the map is marked by the placement of a stone-like token within the boundary of a trisector. \textbf{(See figure \ref{fig:starweb_tokens})}. In the original game, the assignment of colored tokens to player characters is arbitrary; players may choose any token to represent their characters. However in the VASSAL module, each of the token colors have been assigned to a specific character. A cross reference between token color and player character is available by clicking on the \emph{Help} $\rightarrow$ \emph{Player Tokens} menu items. \textbf{(See figure \ref{fig:player_tokens_menu} and figure \ref{fig:player_tokens}).}

Movement of player tokens on the map is only allowed from the current trisector to one of the three immediately adjacent trisectors that share the sides of the triangle (not the vertices). Through a clever distribution of colors across the trisectors, an unambiguous path can be described given the current trisector and an ordered list of the colors along the route. \textbf{(See figure \ref{fig:starweb_movement}).} Player movements on the gameboard must also be entered in the Computer Game Master program. Only legal moves will be allowed by the CGM program.

\begin{figure}[h]\centering
\includegraphics[width=\linewidth]{starweb_tokens}
\caption{Gameboard and tokens within VASSAL}
\label{fig:starweb_tokens}
\end{figure}

\begin{figure}[h]\centering
\includegraphics[width=\linewidth]{player_tokens_menu}
\caption{Click on \emph{Help} $\rightarrow$ \emph{Player Tokens} to review token assignment }
\label{fig:player_tokens_menu}
\end{figure}

\begin{figure}[h]\centering
\includegraphics[width=\linewidth]{player_tokens}
\caption{Cross-reference between token color and character available in the VASSAL module}
\label{fig:player_tokens}
\end{figure}


\begin{figure}[h]\centering
\includegraphics[width=\linewidth]{starweb_movement}
\caption{An example path described as 114 to Orange, Violet, Green, Yellow, Red}
\label{fig:starweb_movement}
\end{figure}

%-------------------    PLOTTING SHEET

\subsection{Plotting Sheet}
If you were conducting the original game with multiple players sharing the same computer, it would become apparent a need exists to minimize a player's time at the terminal. It is not the place for the player decide which moves to make. Instead the game's designers recommend planning the next move while away from the computer and writing down the intended moves on a piece of paper. \textbf{(See figure \ref{fig:plotting_sheet_orig})}. This way, the player only needs to enter the moves and obtain results when it is his his/her turn at the terminal.

To simulate this, a virtual Plotting Sheet is available in the \emph{STAR SAGA: ONE} VASSAL module and can be found by accessing (right-clicking) the context menu bound to a player's token. \textbf{(See figure  \ref{fig:plotting_sheet_menu})}. A simple spreadsheet will appear where moves can be entered. \textbf{(See figure \ref{fig:plotting_sheet_vassal})}. On first use, you may be required to enter column headers and row numbers. The VASSAL engine will save the spreadsheet contents as part of the log file and can be recalled and appended on later turns.

\begin{figure}[h]\centering % Using \begin{figure*} makes the figure take up the entire width of the page
\includegraphics[width=\linewidth]{plotting_sheet_orig}
\caption{Example of plotting turns 1 and 2 as found in the original manual}
\label{fig:plotting_sheet_orig}
\end{figure}

\begin{figure}[h]\centering % Using \begin{figure*} makes the figure take up the entire width of the page
\includegraphics[width=\linewidth]{plotting_sheet_menu}
\caption{Accessing the Plotting Sheet menu item in VASSAL}
\label{fig:plotting_sheet_menu}
\end{figure}

\begin{figure}[h]\centering % Using \begin{figure*} makes the figure take up the entire width of the page
\includegraphics[width=\linewidth]{plotting_sheet_vassal}
\caption{Example of plotting turns 1 and 2 using VASSAL}
\label{fig:plotting_sheet_vassal}
\end{figure}

%-------------------    CARGO SHEET

\subsection{Cargo Sheet}
At the start of the game each player's ship has the capacity to store ten units of cargo. The Computer Game Master will maintain the current state of cargo. But you can also make note of it within VASSAL by accessing the Cargo Sheet from your token's context menu. \textbf{(See figure \ref{fig:cargo_sheet_menu})}. A free-form spreadsheet will appear where you can enter data as needed. \textbf{(See figure \ref{fig:cargo_sheet})}.

\begin{figure}[h]\centering
\includegraphics[width=\linewidth]{cargo_sheet_menu}
\caption{Accessing the Cargo Sheet menu item in VASSAL}
\label{fig:cargo_sheet_menu}
\end{figure}

\begin{figure}[h]\centering
\includegraphics[width=\linewidth]{cargo_sheet}
\caption{Cargo Sheet in VASSAL}
\label{fig:cargo_sheet}
\end{figure}

%-------------------    ITEMS AND ABILITIES

\subsection{Items and Abilities}
Similar to the Cargo Sheet, another free-form spreadsheet is available from your player token's menu for recording special items and abilities gained during play. Use this as needed.

%-------------------    PASSAGE FINDER

\subsection{Passage Finder}
The original game included thirteen booklets labelled A through M, containing passages numbered 1 through 888. Throughout much of the game, the Computer Game Master will instruct a player to read a specific passage from one of the books. These passages form the game's narrative.

The VASSAL module contains scans of these passages created by an early abondonware/archival group called \emph{The Underdogs} and a user named Ranger55\cite{UD09}. They developed a  javascript program to retrieve individual passages requested by the player. In VASSAL, select \emph{Help} $\rightarrow$ \emph{Passage Finder} to open the Passage Finder tool \textbf{(see figure \ref{fig:passage_finder_menu})}. Then enter the requested passage number in the text box on the form \textbf{(see figure \ref{fig:passage_finder})}. Whenever necessary, enter passage 000 to return to the title page.

\begin{figure}[h]\centering
\includegraphics[width=\linewidth]{passage_finder_menu}
\caption{Accessing the Passage Finder tool from the VASSAL Help menu item}
\label{fig:passage_finder_menu}
\end{figure}

\begin{figure}[h]\centering
\includegraphics[width=\linewidth]{passage_finder}
\caption{Passage Finder tool}
\label{fig:passage_finder}
\end{figure}


%-------------------    PLANET LOG

\subsection{Planet Log}
Much of playing \emph{STAR SAGA: ONE} involves trading goods between planets. Planets may also provide opportunities to perform actions, such as searching through a junkyard for special items. The game's designer's recommend creating a planet log on paper to record the exchange rates for goods and the special activities available for a particular planet.

Virtual planet log sheets are available in the VASSAL module. As described in more detail later, you will pull a new Planet Log game piece for each planet visited. In order to keep Planet Logs private between players, a Planet Log piece placed on the map is accessible only to its owner. For this reason, a separate palette exists for each character. Select the palette for your character before adding a new Planet Log piece to the game.

The game designers intended for the details for a particular planet to be known only to the players that have visited a planet. Therefore, in the VASSAL module the Planet Label game piece can be toggled to be invisible to other players.

Upon visiting a new planet, perform the following steps.

\begin{enumerate}[noitemsep] 
\item Click on the \emph{Planet Log} button to toggle the display of the Planet Log palette  \textbf{(See Figure \ref{fig:planet_log_toolbox})}.
\item Find the palette for your character.
\item Drag a new Planet Log game piece and drop it on the game board on top of the planet you are currently visiting.
\item Right click on the new Planet Log and select the "Rename" menu item. Rename the log to match the planet being visited. \textbf{(See Figure \ref{fig:planet_log_menu}).}
\item Right click again on the renamed Planet Log and select the "Planet Log" menu item. A blank spreadsheet will appear.
\item Enter relevant information as required onto the spreadsheet. \textbf{(See Figure \ref{fig:planet_log})}.
\item Right click again on the Planet Log and select \emph{Toggle Visibility} so that the Planet Log is not visible or accessible by other players.
\end{enumerate}

\begin{figure}[h]\centering % Using \begin{figure*} makes the figure take up the entire width of the page
\includegraphics[width=\linewidth]{planet_log_toolbox}
\caption{The \emph{Planet Log} button in the toolbar (A) toggles the display of the Planet Log palette (B)}
\label{fig:planet_log_toolbox}
\end{figure}

\begin{figure}[h]\centering % Using \begin{figure*} makes the figure take up the entire width of the page
\includegraphics[width=\linewidth]{planet_log_menu}
\caption{After dragging a new Planet Log piece to the gameboard, right click to access its context menu}
\label{fig:planet_log_menu}
\end{figure}

\begin{figure}[h]\centering % Using \begin{figure*} makes the figure take up the entire width of the page
\includegraphics[width=\linewidth]{planet_log}
\caption{Example of data entered into the Planet Log spreadsheet}
\label{fig:planet_log}
\end{figure}

%-------------------    PLANET LABELS

\subsection{Planet Labels}
After the tutorial phase is complete, the larger map, labeled \emph{Document Two}, is used for the remainder of play. The \emph{Document Two} map contains many yet-to-be-discovered planets denoted as black dots. To provide replayability, the Computer Game Master program will randomly assign planets to map locations at the start of each new game. Once a planet is visited, the players will discover its name. The original documentation instructs players to lightly write the name of discovered planets using a pencil on the \emph{Document Two} map. 

Unlike the details found in the Planet Log, the name of the new planet is intended to be shared with all players. Therefore, within VASSAL, a game piece called a Planet Label is used as a way to virtually write the planet name on the map.

Upon discovering a new planet, a player should perform the following actions in VASSAL:

\begin{enumerate}[noitemsep]
\item Click on the \emph{Planet Label} button in VASSAL's toolbar area so the \emph{Planet Label} palette is visible. \textbf{(See figure \ref{fig:planet_label_menu})}
\item Drag the \emph{Planet Label} game piece (currently with the label "New Planet" from the planet to the black dot on the map \textbf{(See figure \ref{fig:planet_label})}
\end{enumerate}


\begin{figure}[ht]\centering
\includegraphics[width=\linewidth]{planet_label_menu}
\caption{Click on the \emph{Planet Label} button (A) to toggle the display of the Planet Label palette.}
\label{fig:planet_label_menu}
\end{figure}

\begin{figure}[ht]\centering
\includegraphics[width=\linewidth]{planet_label}
\caption{Accessing the Cargo Sheet menu item in VASSAL}
\label{fig:planet_label}
\end{figure}


%-------------------    HOW TO CONDUCT A GAME

\section{How to Conduct a Multi-Player Game}

\subsection{System Preparation}
\begin{outline}[enumerate]
\1 Download and Install the VASSAL engine
\1 Download the \emph{STAR SAGA: ONE} module for VASSAL
\1 Open the \emph{STAR SAGA: ONE} module in VASSAL
	\2 Click \emph{File} $\rightarrow$ \emph{Open Module}
	\2 When the \emph{Welcome} splash screen, Click \emph{Cancel}

\1 If Play-by-Email then it's recommended to install AppleWin emulator
	\2 Download AppleWin
	\2 If Mac OS X Mavericks then install WINE
		\3 Install \emph{XCode} from App Store
		\3 Enable command line tools in XCode
			\4 From Terminal, run
\begin{verbatim}
xcode-select --install
\end{verbatim}
		\3 Install \emph{MacPorts} for OS X Mavericks
		\3 Update \emph{MacPorts}
\begin{verbatim}
sudo port selfupdate
\end{verbatim}
		\3 Install WINE using \emph{MacPorts}
			\4 From Terminal, run
\begin{verbatim}
sudo port install wine-devel
sudo port install winetricks
\end{verbatim}
		\3 Install Windows MFC 4.2 for WINE
			\4 From Terminal, run
\begin{verbatim}
winetricks mfc42
\end{verbatim}
		\3 Test AppleWin
			\4 From Terminal, run
\begin{verbatim}
wine <path-to-exe>/Applewin.exe
\end{verbatim}
where \texttt{<path-to-exe>} is the path to the directory containing the Applewin.exe executable file.
	\2 If x86 Linux then install WINE
		\3 From Terminal, run
\begin{verbatim}
sudo apt-get install wine-devel
sudo apt-get install winetricks
\end{verbatim}
		\3 Install MFC 4.2 for WINE
			\4 From Terminal, run
\begin{verbatim}
winetricks mfc42
\end{verbatim}
		\3 Test AppleWin
			\4 From Terminal, run
\begin{verbatim}
wine <path-to-exe>/Applewin.exe
\end{verbatim}
where \texttt{<path-to-exe>} is the path to the directory containing the Applewin.exe executable file.
			
\end{outline}

%-------------------    INITIAL SETUP

\subsection{Initial Setup}
\begin{outline}[enumerate]

\1 Launch Apple II Emulator
	\2 Load \emph{STAR SAGA: ONE} disk images in VASSAL
		\3 Insert image for \emph{STAR SAGA: ONE} DISK A BACK  into S6D1
		\3 Insert image for \emph{STAR SAGA: ONE} DISK B FRONT into S6D2
	\2 Boot Apple II	
\end{outline}

%-------------------    Player 1 Turn 1

\subsection{Player 1 - Turn 1}
\begin{outline}[enumerate]
\1 Launch VASSAL
	\2 Open the \emph{STAR SAGA: ONE} module in VASSAL
		\3 Click \textbf{\emph{File} $\rightarrow$ \emph{Open Module}}
		\3 Browse to the directory containing the \emph{STAR SAGA: ONE} module
	%\2 Select \emph{Star_Saga_One-v1.0.vmod}.
		\3 At the \textbf{\emph{Select Play Mode}} prompt, choose \textbf{\emph{Start New Game}} and click \textbf{\emph{Next}}
		\3 At the \textbf{\emph{Choose Side}} prompt, select a character to be used by Player 1 and click \textbf{\emph{Next}}
		\3 At the \textbf{\emph{Select Board}} prompt, choose the map named \textbf{\emph{Map 1 (Starweb)}} and click \textbf{\emph{Finish}}
	\2 Click \textbf{\emph{Help} $\rightarrow$ \emph{Manuals and Dossiers}} and read the \textbf{\emph{Host Guide and Player Reference}}
	\2 Click \textbf{\emph{Help} $\rightarrow$ \emph{Manuals and Dossiers}} and read the \textbf{\emph{Dear Player Card}}
	\2 Click \textbf{\emph{File} $\rightarrow$ \emph{Begin Logfile}} to start recording any moves
	\2 Click \textbf{\emph{Help} $\rightarrow$ \emph{Manuals and Dossiers}} and read the Player 1 character's biography
	\2 As you read the biography, you will be taught how to use the game system. Use the VASSAL features described earlier in the document (Plotting Sheet, Planet Log, etc) and the Computer Game Manager running on the Apple II as instructed.
\1 Switch to the Apple II Emulator
	\2 When your turn is complete within the Computer Game Manager, save the state of the session using \emph{Save State} feature of the emulator. (On AppleWin, it is found under the \textbf{\emph{Advanced}} tab in the \emph{AppleWin Configuration} dialog.) Note: AppleWin will work best if you save the state file in the same directory as the \emph{STAR SAGA: ONE} disk images.

\1 Switch to VASSAL

	\2 When your turn is complete, click \textbf{\emph{File} $\rightarrow$ \emph{End Logfile}} and save the logfile to a convenient location, such as a "Saved Games" folder. Be sure to name the file that somehow encapsulates the turn and move, such as \textbf{\emph{TURN001M1.vlog}}.
	\2 Exit the \emph{STAR SAGA: ONE} module and return to the VASSAL \textbf{\emph{Module Library}} dialog.
	\2 Right-click on the \emph{STAR SAGA: ONE} entry in the \emph{Module Library} dialog and select \textbf{\emph{Add Saved Games Folder}}. Browse to the location where you saved your logfile.

\1 Share Files
	\2 Share the log file \textbf{\emph{TURN001M1.vlog}} and the AppleWin save state file with the other players in the group using email or a file-sharing service such as Dropbox.
	
\end{outline}

%-------------------    Player 2 Turn 1

\subsection{Player 2 - Turn 1}
\begin{outline}[enumerate]

\1 Obtain the log file \textbf{\emph{TURN001M1.vlog}} created by the first player and store it in a convenient location, such as a directory called "Saved Games".

\1 Launch VASSAL
	\2 Open the \emph{STAR SAGA: ONE} module in VASSAL
		\3 Click \textbf{\emph{File} $\rightarrow$ \emph{Open Module}}
		\3 Browse to the directory containing the \emph{STAR SAGA: ONE} module
	\2 At the \emph{Welcome} screen, select the radio button labelled \textbf{\emph{Load Saved Game}} and click \textbf{\emph{Next}}. \textbf{(See figure \ref{fig:load_saved_game}).}
	\2 On the next screen, browse to the location of the saved games and select the log file \textbf{\emph{TURN001M1.vlog}} and click \textbf{\emph{Open}}.
	\2 Back at the \textbf{\emph{Welcome}} screen, click \textbf{\emph{Finish}}.
	\2 After the game board appears, adjust the scale as needed using the zoom-in or zoom-out buttons in the VASSAL toolbar.
\1 Launch Apple II Emulator
	\2 Load the state file created by Player one. (The load state button is found in the \textbf{\emph{Advanced} }tab under the AppleWin configuration dialog.) It's best if the state file is located in the same directory as the disk images. Also, ensure the files for the disk images have the same name as used by Player one. Otherwise the state file may be confused when it can't find disk images.

\1 Switch to VASSAL
	\2 Play back Player one's moves by clicking on the "Play" button found in the toolbar. Alternatively, you may press the \textbf{\emph{Page Down}} key on your keyboard.
	\2 At the end of the log file, a dialog appears asking to start a new logfile. Answer affirmatively. \textbf{(See figure \ref{fig:start_new_logfile}).}
	\2 Click \textbf{\emph{Help} $\rightarrow$ \emph{Manuals and Dossiers} }and read the Player 1 Character's Biography
	\2 As you read the biography, you will be taught how to use the game system. Use the VASSAL features described earlier in the document (Plotting Sheet, Planet Log, etc) and the Computer Game Manager running on the Apple II as instructed.
	\2 When your move is complete, click \textbf{\emph{File} $\rightarrow$ \emph{End Logfile}}.
	
\1 Switch to the Apple II Emulator
	\2 When your turn is complete within the Computer Game Manager, save the state of the session using \textbf{\emph{Save State}} feature of the emulator. (On AppleWin, it is found under the \textbf{\emph{Advanced}} tab in the \textbf{\emph{AppleWin Configuration}} dialog.) Note: AppleWin will work best if you save the state file in the same directory as the \emph{STAR SAGA: ONE} disk images.
	
\1 Share Files
	\2 Share the log file \textbf{\emph{TURN001M1.vlog}} and the AppleWin save state file with the other players in the group using email or a file-sharing service such as Dropbox.
	
\end{outline}

\begin{figure}[ht]\centering
\includegraphics[width=\linewidth]{load_saved_game}
\caption{Radio Button for \emph{Load Saved Game}}
\label{fig:load_saved_game}
\end{figure}

\begin{figure}[ht]\centering
\includegraphics[width=\linewidth]{start_new_logfile}
\caption{Dialog box that appears at the end of playing back a log file}
\label{fig:start_new_logfile}
\end{figure}

%-------------------    Player 3 Turn 1

\subsection{Player 3 through \emph{N} - Turn 1}
If you have more than two players participating in the game, the remaining players should follow the instructions for \textbf{\emph{Player 2 - Turn 1}}, with the exception that they must:
\begin{outline}[enumerate]
\1 Load the most recent save-state file in the AppleWin emulator.
\1 Play back the log files, in sequence, created by each of the previous players. To play back more than one log file, click \textbf{\emph{File} $\rightarrow$ \emph{Load Continuation}} and select the next log file.
%\1 Perform actions as required in VASSAL and the Computer Game Manager
%\1 End logfile in VASSAL and save state in AppleWin.
%\1 Share log and save-state files.
\end{outline}

\subsection{Player 1 through \emph{N} - Turn 2 through \emph{N}}
Similar to the instructions for \textbf{Player 3 through \emph{N} - Turn 1}, in Turn 2 and thereafter, each player should:
\begin{outline}[enumerate]
%\1 Load the most recent save state file in the AppleWin emulator
\1 Play back all the log files, in sequence, created by each player since the current player's previous turn.
%\1 Begin a new logfile
%\1 Perform actions as required in VASSAL and the Computer Game Manager
%\1 End logfile in VASSAL and save state in AppleWin.
%\1 Share log and save-state files.
\end{outline}

\clearpage
 
\section{Resources}

\begin{table}[hbt]
\caption{Disk Image Resources}
\centering

\begin{tabular}{lll}
\toprule
Computer & Resource & URL \\
\midrule
Apple II & disk image  & ftp://ftp.apple.asimov.net/pub/apple\_ii/images/games/rpg/misc/STAR\_SAGA\_ONE\_DISKA\_FRONT.dsk \\
 & disk image & ftp://ftp.apple.asimov.net/pub/apple\_ii/images/games/rpg/misc/STAR\_SAGA\_ONE\_DISKA\_BACK.dsk \\
 & disk image & ftp://ftp.apple.asimov.net/pub/apple\_ii/images/games/rpg/misc/STAR\_SAGA\_ONE\_DISKB.dsk \\
Apple IIgs & disk image & ftp://ftp.apple.asimov.net/pub/apple\_II/images/gs/games/adventure/Star\_Saga\_One.zip \\
 & disk image & ftp://ftp.apple.asimov.net/pub/apple\_II/images/gs/games/adventure/Star\_Saga\_Two.zip \\ 
  & scans & http://mocagh.org/loadpage.php?getgame=starsaga \\
JVM & VASSAL & http://www.vassalengine.org/ \\
 & module & http://www.vassalengine.org/mediawiki/index.php?title=Category:Modules\&from=S \\
  & or & http://bit.ly/star\_saga\_one\_module \\
  
\end{tabular}

\label{tab:urls}
\end{table}

%------------------------------------------------
%\phantomsection
%\section*{Acknowledgments} % The \section*{} command stops section numbering
%
%\addcontentsline{toc}{section}{Acknowledgments} % Adds this section to the table of %contents
%
%So long and thanks for all the fish \cite{Figueredo:2009dg}.

%\footnotetext[1]{Using WINE under OSX or Linux}
%\footnotetext[2]{Possibly under development}
%\footnotetext[3]{Using Game Wizard Pro 32 Utility and Microsoft MS-DOS}
%----------------------------------------------------------------------------------------
%	REFERENCE LIST
%----------------------------------------------------------------------------------------
\phantomsection
%\bibliographystyle{unsrt}
%\bibliography{sample}

\begin{thebibliography}{9}

\bibitem[Mst88a]{SS1AD} 
Masterplay Publishing Corp, Advertisement for \emph{STAR SAGA: ONE - Beyond the Boundary}, \emph{Computer Gaming World Number 50}, Golden Empire Publications, August 1988, pp. 38.

\bibitem[Mst88b]{SS1HG} 
\emph{STAR SAGA: ONE - Beyond the Boundary - Host Guide and Player Reference Manual}, Masterplay Publishing Corp, 1988, pp. 46.

\bibitem[OD98]{OSTED98} Gordon Olmstead-Dean, \emph{Theatre Style Live Roleplaying Events}, available at \url{http://www.interactivedramas.info/papers/theatredean.pdf}, 1998, pp 95-97.

\bibitem[UD09]{HOTUD09} Underdogs, \emph{Star Saga: One} article currently available at \url{http://www.hotud.org/component/content/article/38-content/games/adventure/23072-sp-1023092192} March 21, 2009

\end{thebibliography}

%----------------------------------------------------------------------------------------

\end{document}