Update of /cvsroot/netrek/client/netrekxp/resources/htmlhelp/html
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv23922/resources/htmlhelp/html

Added Files:
	basics.html commandline.html configfile.html configsyntax.html 
	controlsintro.html dashboard.html defaultmap.html galaxy.html 
	gamecontrols.html generalconfig.html intro.html 
	jointhegame.html loginscreen.html macrosconfig.html main.css 
	mainwindows.html messages.html metaserver.html motdwindow.html 
	playerlist.html plistconfig.html remapping.html 
	serversettings.html tactical.html teamselect.html 
	windowsconfig.html 
Log Message:
Update to version 4.4.0.3

--- NEW FILE: gamecontrols.html ---
<html>
<head>
<style>@import url(main.css);</style>
<link disabled href="main.css" rel="stylesheet" type="text/css">
<title>Game Controls</title>
</head>
<body>
<h1>Game Controls</h1>
<p>
In this section you will learn how to use mouse and keyboard to fly your ship,
change options, etc.
<p>
Section topics:
<br>
<ul>
<li><a href="controlsintro.html">Introduction to game controls</a></li>
<li><a href="remapping.html">Changing Defaults</a></li>
<li><a href="defaultmap.html">Default Bindings</a></li>
</ul>
</body>
</html>
--- NEW FILE: intro.html ---
<html>
<head>
<style>@import url(main.css);</style>
<link disabled href="main.css" rel="stylesheet" type="text/css">
<title>Introduction</title>
</head>
<body>
<h1>Introduction</h1>
<p>
NetrekXP Mod is a client for Netrek - multiplayer battle simulation game.
<bp>
The program is modification of existing client called NetrekXP (yeah, this is
where 'Mod' comes from). All Netrek clients have some similarities and some
differences. I would recommend trying each and every one of them before
making decision on what client to play with.
<p>
This reference will help you to get familiar with the program, its configurations
and possible customizations.
<p>
Manual Sections:
<ul>
<li><a href="basics.html">The Basics</a></li>
<li><a href="gamecontrols.html">Game Controls</a></li>
<li><a href="configfile.html">Configuration File</a></li>
</ul>
</body>
</html>
--- NEW FILE: windowsconfig.html ---
<html>
<head>
<title>Windows Configuration</title>
<style>@import url(main.css);</style>
<link disabled href="main.css" rel="stylesheet" type="text/css">
</head>
<body>
<h1>Windows Configuration</h1>
<p>
First of all let's list names of NetrekXP Mod windows:
<ul>
<li><b>netrek</b> - Main window</li>
<li><b>local</b> - Tactical window</li>
<li><b>map</b> - Galaxy window</li>
<li><b>warn</b> - Warning window. Here all warnings are displayed</li>
<li><b>message</b> - Message window. Here you type messages</li>
<li><b>review</b> - Review window</li>
<li><b>review_all</b> - Window that receives All messages</li>
<li><b>review_team</b> - Window that receives Team messages</li>
<li><b>review_your</b> - Window that receives Personal messages</li>
<li><b>review_kill</b> - Window that receives Kill messages</li>
<li><b>review_phaser</b> - Window that receives Phaser messages</li>
<li><b>planet</b> - Planet list window</li>
<li><b>player</b> - Player list window</li>
<li><b>war</b> - War declaration window</li>
<li><b>fed</b> - Federation selection window</li>
<li><b>ori</b> - Orion selection window</li>
<li><b>rom</b> - Romulan selection window</li>
<li><b>kli</b> - Klingon selection window</li>
<li><b>quit</b> - Quit countdown window</li>
<li><b>option</b> - Option menu window</li>
<li><b>rank</b> - Rank window</li>
<li><b>stats</b> - Statistics window</li>
<li><b>help</b> - Help window</li>
<li><b>udp</b> - UDP options window</li>
<li><b>pingstats</b> - Ping statistics window</li>
<li><b>xtrekrc_help</b> - xtrekrc help window</li>
<li><b>macro</b> - Macros window</li>
</ul>
<p>
<code><b>&lt;window&gt;.map: [on/off]</b></code> - show window on startup
<p>
Example:<br>
<code>pingstats.mapped: on</code>
<p>
<code><b>&lt;window&gt;.parent: &lt;value&gt;</b></code> - set parent window of &lt;window&gt;
<p>
Example:<br>
<code>fed.parent: map</code> - will move Feds selection window from tactical to galaxy
<p>
<code><b>&lt;window&gt;.geometry: &lt;geometry&gt;</b></code> - set window placement and size
<p>
<code>&lt;geometry&gt;</code> parameter can be presented by three different states:
<ul>
<li><code><b>&lt;window&gt;.geometry: &lt;width&gt;x&lt;height&gt;+&lt;xpos&gt;+&lt;ypos&gt</b></code>
	<ul>
	<li><code><b>&lt;width&gt;</b></code> - window width</li>
	<li><code><b>&lt;height&gt;</b></code> - window height</li>
	<li><code><b>&lt;xpos&gt;</b></code> - window x coordinate</li>
	<li><code><b>&lt;ypos&gt;</b></code> - window y coordinate</li>
	</ul>
</li>
<li><code><b>&lt;window&gt;.geometry: &lt;width&gt;x&lt;height&gt;</b></code>
	<ul>
	<li><code><b>&lt;width&gt;</b></code> - window width</li>
	<li><code><b>&lt;height&gt;</b></code> - window height</li>
	</ul>
</li>
<li><code><b>&lt;window&gt;.geometry: +&lt;xpos&gt;+&lt;ypos&gt</b></code>
	<ul>
	<li><code><b>&lt;xpos&gt;</b></code> - window x coordinate</li>
	<li><code><b>&lt;ypos&gt;</b></code> - window y coordinate</li>
	</ul>
</li>
</ul>
<p>
Examples:<br>
netrek.geometry: 1024x768+0+0 - default main window geometry<br>
netrek.geometry: 1024x768 - only size parameters<br>
netrek.geometry: +0+0 - only placement parameters
<p>
Above options can be used with any window.
<p>
Next option can only be used with message windows:
<p>
<code><b>&lt;message window&gt;.allow: [A][T][I][P][K]</b></code> - choose type of messages printed in message window
<ul>
	<li><b>A</b> - All messages</li>
	<li><b>T</b> - Team messages</li>
	<li><b>I</b> - Personal (Individual) messages</li>
	<li><b>P</b> - Phaser messages</li>
	<li><b>K</b> - Kill messages</li>
</ul>
So if for instance you would like to make bigger review_team, but still don't want to mess it with review_all you
can just define '<code><b>review_team.allow:&nbsp;TIPK</b></code>' to watch after any except All messages.
</ul>
</body>
</html>
--- NEW FILE: dashboard.html ---
<html>
<head>
<title>Dashboard</title>
<style>@import url(main.css);</style>
<link disabled href="main.css" rel="stylesheet" type="text/css">
</head>
<body>
<h1>Dashboard</h1>
<p>
Dashboard window contains vital ship information and weapons used:
<p>
<img src="images\dashboard.gif">
<p>
The window is divided roughly in two parts - <b>Flags</b> and <b>Gauges</b>
<p>
Let's get familiar with them:
<ul>
<li>Flags from left to right:</li>
	<ul>
	<li>S - shields on</li>
	<li>G/Y/R - flag that shows proxymity alert. G for green, Y - yellow, R - red</li>
	<li>L - you are locked on something (player or planet)</li>
	<li>R - you are repairing</li>
	<li>B - you are bombing</li>
	<li>O - you are orbiting planet</li>
	<li>D - you are docking startbase (or if you are starbase then docking is enabled)</li>
	<li>C - you are cloaked</li>
	<li>W - your weapons are hot</li>
	<li>E - your engine is hot</li>
	<li>P/T - you are pressoring or tractoring somebody</li>
	<li>u/d - you are beaming armies up or down</li>
	</ul>
<li>Gauges:</li>
	<ul>
	<li>Sp - ship speed</li>
	<li>Sh - shields damage points</li>
	<li>Da - hull damage points</li>
	<li>Ar - armies carried</li>
	<li>Wt - weapons temperature</li>
	<li>Et - egnine temperature</li>
	<li>Fu - fuel available</li>
	<li>Kills - number of kills</li>
	</ul>
</ul>
</body>
</html>
--- NEW FILE: loginscreen.html ---
<html>
<head>
<title>Login Screen</title>
<style>@import url(main.css);</style>
<link disabled href="main.css" rel="stylesheet" type="text/css">
</head>
<body>
<h1>Login Screen</h1>
<p>
After successfull connection to the server you will see the main game window. It is
divided to four parts initially, but we will get familiar with each of them in the
next topics.
<p>
If your client isn't configured to automatically login you to the game you will be
asked to supply your username and password to join the game (or observe the game).
<p>
The login window is located on the top left of main screen:
<p>
<img src="images\loginscreen.gif">
<p>
There are two types of logins on most servers - <b>guest user</b> and <b>authenticated user</b>.
<p>
If you type "guest" as your name or push Ctrl-g you will not be required to supply password. There are
some differences between guest users and authenticated users. The major difference is
that no information is written to the server players database for guests. So when you
disconnect from the game all your statistics are wiped out.
<p>
For authenticated users everything is saved to players database, so when you come next
time to the server and supply your name and password you will start the game with statistics
that were saved for you from the last session.
</body>
</html>
--- NEW FILE: macrosconfig.html ---
<html>
<head>
<title>Macros Configuration</title>
<style>@import url(main.css);</style>
<link disabled href="main.css" rel="stylesheet" type="text/css">
</head>
<body>
<h1>Macros Configuration</h1>
<p>
Macros can be divided in two main categories:
<ul>
<li>Regular Macros</li>
<li>Receiver Configurable Distress Macros</li>
</ul>
The main difference between two is that you send the first type by yourself while second
type is actually how you want other's macros to be showed on your client.
<p>
In order to trigger any of these you should enter Macro Mode. Some macros are used
by players very frequently, so in order to speedup the process you can use
following configuration option:
<p>
<code><b>singleMacro: &lt;keys list for one-push macros&gt;</b></code>
<p>
Example:<br>
<code>singleMacro: FE^q</code> - will allow triggering macros defined for F, E and Ctrl-q
by single key push.
<p>
<h2>Regular Macros</h2>
Regular macros can be either single or multiline and their general syntax is:
<p>
<code><b>mac.&lt;key&gt;.&ltrecipient&gt;: &lt;macro string&gt;</b></code>
<p>
<ul>
<li>
<code><b>&lt;key&gt;</b></code> - key to press in macro mode to send macro
<p>
The key can be in form of:
	<ul>
	<li><b>char</b> - press key on keyboard</li>
	<li><b>^char</b> - press Ctrl+key on keyboard</li>
	</ul>
</li>
<p>
<li>
<code><b>&ltrecipient&gt;</b></code> - recipient of the macro
<p>
Recipient can be one of:
	<ul>
	<li><code><b>(empty)</b></code> - you will be asked to specify recipient after macro activation</li>
	<li><code><b>A</b></code> - send to All</li>
	<li><code><b>T</b></code> - send to your Team</li>
	<li><code><b>F</b></code> - send to Federation</li>
	<li><code><b>K</b></code> - send to Klingons</li>
	<li><code><b>O</b></code> - send ti Orions</li>
	<li><code><b>R</b></code> - send to Romulans</li>
	<li><code><b>a-z</b></code> - send to player</li>
	<li><code><b>%I, %i, %c</b></code> - send to yourself</li>
	<li><code><b>%U, %u, %p</b></code> - send to player nearest your mouse pointer</li>
	<li><code><b>%Z, %z, %t</b></code> - send to a team whose player nearest your mouse pointer</li>
	<li><code><b>%g</b></code> - send to friendly player nearest your mouse pointer</li>
	<li><code><b>%h</b></code> - send to enemy player nearest your mouse pointer</li>
	</ul>
</li>
<p>
<li>
<code><b>&lt;macro string&gt;</b></code> - text string
<p>
In addition to regular text, macro string can contain:
	<ul>
	<li><code><b>%a</b></code> - armies carried by sender</li>
	<li><code><b>%d</b></code> - sender damage percentage</li>
	<li><code><b>%s</b></code> - sender shields percentage</li>
	<li><code><b>%f</b></code> - sender fuel percentage</li>
	<li><code><b>%w</b></code> - sender wtemp percentage</li>
	<li><code><b>%e</b></code> - sender etemp percentage</li>
	<li><code><b>%t</b></code> - team id character of target planet</li>
	<li><code><b>%T</b></code> - team id character of sender team</li>
	<li><code><b>%c</b></code> - sender id character</li>
	<li><code><b>%n</b></code> - armies on target planet</li>
	<li><code><b>%E</b></code> - 1 if etemped, 0 if not</li>
	<li><code><b>%W</b></code> - 1 if wtemped, 0 if not</li>
	<li><code><b>%S</b></code> - sender two character ship type</li>
	<li><code><b>%p</b></code> - id character of target player</li>
	<li><code><b>%g</b></code> - id character of target friendly player</li>
	<li><code><b>%h</b></code> - id character of target enemy player</li>
	<li><code><b>%P</b></code> - id character of player nearest sender</li>
	<li><code><b>%G</b></code> - id character of friendly player nearest sender</li>
	<li><code><b>%H</b></code> - id character of enemy player nearest sender</li>
	<li><code><b>%l</b></code> - three character name of target planet</li>
	<li><code><b>%L</b></code> - three character name of target planet in capitals</li>
	<li><code><b>%i</b></code> - sender full player name</li>
	<li><code><b>%I</b></code> - sender full player name in capitals</li>
	<li><code><b>%u</b></code> - full name of target player</li>
	<li><code><b>%U</b></code> - full name of target player in capitals</li>
	<li><code><b>%z</b></code> - three letter team id of target planet</li>
	<li><code><b>%Z</b></code> - three letter team id of target planet in capitals</li>
	<li><code><b>%b</b></code> - planet nearest sender</li>
	<li><code><b>%B</b></code> - planet nearest sender in capitals</li>
	<li><code><b>%o</b></code> - three letter sender team name</li>
	<li><code><b>%O</b></code> - three letter sender team name in capitals</li>
	<li><code><b>%k</b></code> - sender number of kills</li>
	<li><code><b>%K</b></code> - number of kills target player has</li>
	<li><code><b>%(SPACE)</b></code> - adds space to message</li>
	<li><code><b>%v</b></code> - average ping round trip time</li>
	<li><code><b>%V</b></code> - standard deviation of ping round trip time</li>
	<li><code><b>%y</b></code> - percentage of total packet loss identified by server</li>
	<li><code><b>%m</b></code> - the last message you sent</li>
	<li><code><b>%M</b></code> - the last message you sent in capitals</li>
	</ul>
<p>
It is also possible to create complex macros using conditional tests:
	<ul>
	<li><code><b>&lt;condition&gt;%{output if true%!output if false%}</b></code></li>
	<li><code><b>%?</b></code> - introduce test</li>
	<li><code><b>=</b></code> - equivalence</li>
	<li><code><b>&lt;</b></code> - less</li>
	<li><code><b>&gt;</b></code> - greater</li>
	</ul>
</li>
</ul>
<p>
Examples:
<pre>
      mac.F.T:   Help!  Carrying %a!!
      mac.f:     Help!  Carrying %a!!
      mac.c.T:   %p++ near %l
      mac.b.T:   %?%n>4%{bomb %l at %n%!bomb%}
      mac.d.T:   %E%{%!%W%{%!I'm fine.  How are you? %}%}%E%{ETEMPED!!!  %}
                 %W%{WTEMPED!!!  %}Carrying %?%a>0%{%a armies!%!NO armies.%}
      mac.a.T:   %E%{ETEMPED!!!  %}%W%{WTEMPED!!!  %}Carrying %?%a>0%{%a 
                 armies! %!NO armies.%}
      mac.R.A:   I'm a %?%S=SB%{star base!%!twink!%}
      mac.K.A:   KissMy%S
      mac.t:     thanks
      mac.y:     yes
      mac.n:     no
      mac.B:     bye, getting hungry/sleep/horny
      mac.e.T:   need escort going to %l%?%a>0%{, carrying %a armies!%}
      mac.v.%t   %T%c PING stats: Average: %v ms, Stdv: %V ms, Loss: %y%%
</pre>
<p>
<h2>Receiver Configurable Distresses</h2>
<p>
As we already told RCD is opposite to the macro. You decide what do display instead of something that was received
from another player.
<p>
There is a limited amount of RCDs because server doesn't actually send any text to you, but instead it tells
your client that player 'x' sent RCD number 'y'. The client then looks what should be displayed when receiving
RCD 'y' and creates text that is only displayed in your client.
<p>
RCD syntax also defines key that will trigger RCD to be sent to others. The distress text will be shown same
whether you send specific RCD or you receive it from other player:
<p>
<code><b>dist.&lt;key&gt;.&lt;distress name&gt;: &lt;distress text&gt;</b></code>
<ul>
<li><code><b>&lt;key&gt;</b></code> - same as in regular macros</li>
<li><code><b>&lt;distress name&gt;</b></code> - predefined distress name
	<ul>
	<li><code><b>save_planet</b></code> - general distress call for help</li>
	<li><code><b>base_ogg</b></code> - distress to prepare for enemy starbase ogg</li>
	<li><code><b>help1</b></code> - general distress call for help</li>
	<li><code><b>help2</b></code> - general distress call for help</li>
	<li><code><b>asw</b></code> - ASW (Anti Scout War) distress</li>
	<li><code><b>asbomb</b></code> - distress for bomb request</li>
	<li><code><b>doing1</b></code> - general distress</li>
	<li><code><b>doing2</b></code> - general distress</li>
	<li><code><b>pickup</b></code> - calls armies pickup of enemy player</li>
	<li><code><b>pop</b></code> - calls planet pop</li>
	<li><code><b>other1</b></code> - general distress</li>
	<li><code><b>other2</b></code> - general distress</li>
	<li><code><b>help</b></code> - distress for help</li>
	<li><code><b>escorting</b></code> - escorting friendly player distress</li>
	<li><code><b>taking</b></code> - taking planet distress</li>
	<li><code><b>ogg</b></code> - ogg distress</li>
	<li><code><b>ogging</b></code> - ogging distress</li>
	<li><code><b>carrying</b></code> - carried armies call</li>
	<li><code><b>free_beer</b></code> - free beer enemy call</li>
	<li><code><b>crippled</b></code> - crippled enemy call</li>
	<li><code><b>controlling</b></code> - space controlling distress</li>
	<li><code><b>space_control</b></code> - space control call</li>
	<li><code><b>bomb</b></code> - bomb call</li>
	<li><code><b>no_gas</b></code> - no gas distress</li>
	<li><code><b>bombing</b></code> - bombing distress</li>
	</ul>
</li>
</ul>
<p>
All RCDs are predefined by client and can be changed if needed.
</body>
</html>
--- NEW FILE: messages.html ---
<html>
<head>
<title>Message Windows</title>
<style>@import url(main.css);</style>
<link disabled href="main.css" rel="stylesheet" type="text/css">
</head>
<body>
<h1>Message Windows</h1>
<p>
There are roughly 5 types of messages in Netrek:
<ul>
<li>All - such message is seen by everyone in game</li>
<li>Team - this message is seen only by team (race) that it was sent to</li>
<li>Individual - this message is only see by person it was sent to</li>
<li>Phaser - this message is sent from GOD (server) to player that used phaser. The message contains statistics information on damage</li>
<li>Kill - this message is sent by GOD (server) to everyone. Every message contains data on who was killed by whom, what kind of weapon caused death and how much credits were earned</li>
</li>
</ul>
<p>
There are 6 different windows that can be used to see these messages:
<ul>
<li>Review - any message is seen there</li>
<li>All - only messages to everyone are seen there</li>
<li>Team - only team messages are seen there</li>
<li>Individual - only messages sent to you are seen there</li>
<li>Phaser - phaser messages are see there</li>
<li>Kill - only kill messages are seen there</li>
</ul>
<p>
This is how Review window looks:
<p>
<img src="images\messages.gif">
<p>
The default client setup is to show only Review window, so all messages your client receives are displayed there.
It is common to argue about best message window setups. Most veterans tend to play with only one Review
window. This way they know exact time flow of messages (with multiple windows it is impossible to find out what message
arrived before or after any given one).
</body>
</html>
--- NEW FILE: playerlist.html ---
<html>
<head>
<title>Player List</title>
<style>@import url(main.css);</style>
<link disabled href="main.css" rel="stylesheet" type="text/css">
</head>
<body>
<h1>Player List</h1>
<p>
Player list window contains information on players in the game. 
<p>
<img src="images\playerlist.gif">
<p>
The window contains both players and observers, but can be configured to display only part of the at a time.
<p>
Today servers allow 32 players to exist in game - half playing, half observing. It is easy to see players from
observers by looking at their player number (letter). Anyone below hexadecimal 'f' (15) will be player, others are
observers.
<p>
The list contains useful information on other players, such as their name and login, statistics, hours spent playing, etc.
You will get familiar with all details after some time of playing.
</body>
</html>
--- NEW FILE: configfile.html ---
<html>
<head>
<style>@import url(main.css);</style>
<link disabled href="main.css" rel="stylesheet" type="text/css">
<title>Configuration File</title>
</head>
<body>
<h1>Configuration File</h1>
<p>
Any of program configuration options can be saved in configuration file. This
way after finding all valuable settings for you it is easy to automatically load
them when you fire up the client to play another game.
<p>
NetrekXP Mod searches for following files (in order from top to bottom) in the
executable directory:
<p>
<ul>
<li><b>netrekrc</b></li>
<li><b>netrekrc.txt</b></li>
<li><b>xtrekrc</b></li>
<li><b>xtrekrc.txt</b></li>
</ul>
So if you have one of these file it will be read at startup and change application
defaults to whatever values set in the configuration file.
<p>
Section topics:
<ul>
<li><a href="configsyntax.html">Configuration File Syntax</a></li>
<li><a href="generalconfig.html">General Configuration Options</a></li>
<li><a href="macrosconfig.html">Macros Configuration</a></li>
<li><a href="windowsconfig.html">Windows Configuration</a></li>
<li><a href="plistconfig.html">Player List Configuration</a></li>
</ul>
</body>
</html>
--- NEW FILE: mainwindows.html ---
<html>
<head>
<title>Main Game Windows</title>
<style>@import url(main.css);</style>
<link disabled href="main.css" rel="stylesheet" type="text/css">
</head>
<body>
<h1>Main Game Windows</h1>
<p>
Congratulations, Captain. You sucessfully joined Netrek Universe:
<p>
<img src="images\mainwindows.gif">
<p>
Next topics will give you short explanation about windows that compose it:
<ul>
<li><a href="tactical.html">Tactical (Local) Window</a></li>
<li><a href="galaxy.html">Galaxy (Map) Window</a></li>
<li><a href="dashboard.html">Dashboard</a></li>
<li><a href="messages.html">Message Windows</a></li>
<li><a href="playerlist.html">Player List</a></li>
</ul>
</body>
</html>
--- NEW FILE: generalconfig.html ---
<html>
<head>
<style>@import url(main.css);</style>
<link disabled href="main.css" rel="stylesheet" type="text/css">
<title>General Configuration Options</title>
</head>
<body>
<h1>General Configuration Options</h1>
<p>
Following table contains all possible general configuration options and their defaults:
<table border=1 cellspacing=0 cellpadding=3>
<tr>
<td><b>Name</b></td>
<td><b>Action</b></td>
<td><b>Possible Values</b></td>
</tr>
<tr>
<td><code><b>agriCAPS</b></code></td>
<td>ARGI planet names in capital letters on galaxy</td>
[...1059 lines suppressed...]
<td>
	<ul>
	<li><b>on (default)</b></li>
	<li><b>off</b></li>
	</ul>
</td>
</tr>
<tr>
<td><code><b>windowMove</b></code></td>
<td>Enable moving internal windows</td>
<td>
	<ul>
	<li><b>on</b></li>
	<li><b>off (default)</b></li>
	</ul>
</td>
</tr>
</table>
</body>
</html>
--- NEW FILE: galaxy.html ---
<html>
<head>
<title>Galaxy Window</title>
<style>@import url(main.css);</style>
<link disabled href="main.css" rel="stylesheet" type="text/css">
</head>
<body>
<h1>Galaxy Window</h1>
<p>
Galaxy or Map is the window where you will collect very useful information on
what the hell is happening here.
<p>
This is a picture of the whole galaxy. All planets have fixed location
(though there is a server setting that allows galaxy to rotate). The only resourse
that doesn't change from game to game is the planet name, so try to remember planet
names. This will be very useful.
<p>
<img src="images\galaxy.gif">
<p>
Every planet can be owned by one of four races or can be independent.
The ownership of the planet is defined by armies the planet has. If there are
Romulan armies on it then it is owned by Romulan Empire. The ownership of the planet
can be changed by dropping your armies on enemy planets. 1 army kills 1 enemy army.
When you kill all enemy armies the planet becomes not owned by anyone and thus can
be taken.
<p>
Initially only your team planets are visible (i.e. have resources like fuel/repair/agri
visible when you try to get info on planet). Other planets are grayed out and you can't
get any information on them. In order for planet to become visibile to your team one
of team players should orbit it.
<p>
</body>
</html>
--- NEW FILE: basics.html ---
<html>
<head>
<style>@import url(main.css);</style>
<link disabled href="main.css" rel="stylesheet" type="text/css">
<title>The Basics</title>
</head>
<body>
<h1>The Basics</h1>
<p>
This section will give you short introduction on client look and feel.<br>
You will also find some useful information on how to use different windows.
<p>
Section topics:
<br>
<ul>
<li><a href="commandline.html">Command Line options</a></li>
<li><a href="metaserver.html">Metaserver Window</a></li>
<li><a href="loginscreen.html">Login Screen</a></li>
<li><a href="jointhegame.html">Joining The Game</a></li>
<li><a href="mainwindows.html">Main Game Windows</a></li>
</ul>
</body>
</html>
--- NEW FILE: metaserver.html ---
<html>
<head>
<title>Meta Server Window</title>
<style>@import url(main.css);</style>
<link disabled href="main.css" rel="stylesheet" type="text/css">
</head>
<body>
<h1>Metaserver Window</h1>
<p>
This will probably be the first window you will see starting the client.
The window appears after successfull connection to metaserver that
holds list of available netrek servers.
<p>
Here is how it looks:
<p>
<img src="images/metawindow.gif">
<p>
There are several types of games played in Netrek Universe. It could be Bronco,
Hockey, Chaos, Dogfight and some others. Most of servers you'll see these days
are either Bronco or Hockey. Bronco is the most popular type of Netrek, so go on
and click on some Bronco server to connect to the game.
<p>
In order to join the game to play you should point on one of the servers and click
<b>left</b> mouse button.<br>
If you wish to observe the game instead of playing - click <b>right</b> mouse button.
<p>
Clicking on one of yellow links will open your browser on the link's main site
</body>
</html>
--- NEW FILE: teamselect.html ---
<html>
<head>
<title>Team Selection</title>
<style>@import url(main.css);</style>
<link disabled href="main.css" rel="stylesheet" type="text/css">
</head>
<body>
<h1>Team Selection</h1>
<p>
Right below MOTD window you have Team (Race) Selection part:
<p>
<img src="images\teamselect.gif">
<p>
There are four races exist in Netrek - Federation, Romulans, Klingons and Orions
<p>
Each of the races has different ship pictures (though the ships have exactly same
power and weapons among the races).
<p>
In the races selection you will see number of players playing per-race. If there is
a T-mode you will only be allowed to join one of the two playing races. Otherwise you
are allowed to select at least one of three teams.
<p>
In order to select team you should do one of two:
<ul>
<li>click with left mouse button on the team box. This will make you join the team in default ship 
that is defined for client</li>
<li>point with mouse at the team box and press one of the following keys to select one of the ship
types:
<ul>
<li><b>s</b> - Scout (SC)</li>
<li><b>d</b> - Destroyer (DD)</li>
<li><b>c</b> - Cruiser (CA)</li>
<li><b>b</b> - Battleship (BB)</li>
<li><b>a</b> - Assault (AS)</li>
<li><b>o</b> - Starbase (SB)</li>
</ul>
</ul>
<p>
If you want to quit - click on the clock box.
<p>
After death you will be presented same team selection window. If you want to change your
team or ship you should use explanation above. However if you want to get back to same team
in the same ship you can push <b>'space'</b> button and you are back.
</body>
</html>
--- NEW FILE: plistconfig.html ---
<html>
<head>
<title>Player List Configuration</title>
<style>@import url(main.css);</style>
<link disabled href="main.css" rel="stylesheet" type="text/css">
</head>
<body>
<h1>Player List Configuration</h1>
<p>
Player list can be configured to show custom columns
<p>
Syntax for playerList option is as follows:
<p>
<code><b>playerList: &lt;string of columns&gt;</b></code>
<p>
<code>&lt;string of columns&gt;</code> can contain any of:
<p>
<ul>
<li><code><b>(space)</b></code> - White Space</li>
<li><code><b>b</b></code> - Armies Bombed</li>
<li><code><b>d</b></code> - Damage Inflicted (DI)</li>
<li><code><b>k</b></code> - Max Kills</li>
<li><code><b>l</b></code> - Login Name</li>
<li><code><b>n</b></code> - Ship Number</li>
<li><code><b>p</b></code> - Planets Taken</li>
<li><code><b>r</b></code> - Ratio</li>
<li><code><b>s</b></code> - Speed</li>
<li><code><b>v</b></code> - Deaths per Hour</li>
<li><code><b>w</b></code> - War Status</li>
<li><code><b>B</b></code> - Bombing</li>
<li><code><b>C</b></code> - Curt (Short) Rank</li>
<li><code><b>D</b></code> - Defence</li>
<li><code><b>H</b></code> - Hours Played</li>
<li><code><b>K</b></code> - Kills</li>
<li><code><b>L</b></code> - Losses</li>
<li><code><b>M</b></code> - Host Machine</li>
<li><code><b>N</b></code> - Name</li>
<li><code><b>O</b></code> - Offence</li>
<li><code><b>P</b></code> - Planets</li>
<li><code><b>R</b></code> - Rank</li>
<li><code><b>S</b></code> - Stats</li>
<li><code><b>T</b></code> - Ship Type</li>
<li><code><b>V</b></code> - Kills per Hour</li>
<li><code><b>W</b></code> - Wins</li>
</ul>
<p>
Examples:
<p>
<code>playerList: nTRNKWLr O D d</code> - Old style<br>
<code>playerList: nTK  RNlr Sd</code> - Kill watch style<br>
</body>
</html>
--- NEW FILE: tactical.html ---
<html>
<head>
<title>Tactical Window</title>
<style>@import url(main.css);</style>
<link disabled href="main.css" rel="stylesheet" type="text/css">
</head>
<body>
<h1>Tactical Window</h1>
<p>
Tactical or Local is the window where you will have most of fun in Netrek.<br>
It is on the top left of the main screen. Your ship is always centered in it and probably looks tainted by your team color over
white.
<p>
<img src="images\tactical.gif">
<p>
</body>
</html>
--- NEW FILE: controlsintro.html ---
<html>
<head>
<style>@import url(main.css);</style>
<link disabled href="main.css" rel="stylesheet" type="text/css">
<title>Introduction to Game Controls</title>
</head>
<body>
<h1>Introduction To Game Controls</h1>
<p>
You will need both mouse and keyboard to fully control the game.
<p>
There are several keys that you probably want to learn in order to control
the main window:
<br>
<ul>
<li><b>Alt+Enter</b> - toggle title bar of client window. This gives you an option to
quickly see what server you are playing on in case of multiple netrek windows are
opened</li>
<li><b>Alt+End</b> - minimize current netrek window</li>
<li><b>Shift+Esc</b> - kill the client really fast. This will not perform any cleanup
procedures, so please, don't use this to logout</li>
</ul>
<p>
And now let's discuss main game controls:
<h2>Mouse</h2>
<p>
Let's leave mouse buttons aside for a while and discuss only mouse pointer.<br>
First of all the client will behave absolutely identical in <a href="tactical.html">
Tactical</a> and <a href="galaxy.html">Galaxy</a> windows.<br>
No matter where you point in one of the windows your client will take mouse 
coordinates relative to your ship and depending on command you submitted will process it.
<p>
The main purpose of mouse is to add coordinates to every action that you want to
perform.
<p>
For instance if you want to shoot (left mouse button or 't' on keyboard) the torps
will fly to where your mouse pointer is located.
<p>
Every mouse has buttons and you can use them to perform whatever action you want.
The default settings for 3-button mice are:
<ul>
<li><b>Left button</b> - fire torpedoes</li>
<li><b>Middle button</b> - fire phaser</li>
<li><b>Right button</b> - change direction</li>
</ul>
<p>
It is possible to change defaults by remapping (reassigning) mouse buttons to different
actions. It is also possible to use button clicks in conjunction with Ctrl+Shift, Ctrl or Shift keys. 
We will discuss all of these in <a href="remapping.html">Changing Defaults</a> section.
<p>
<h2>Keyboard</h2>
<p>
Well, there is nothing special about keyboard in Netrek. It behaves exactly same as
in any other application. You press key and something happens.
<p>
The only thing you should remember when dealing with keyboard is that every action
(well, almost every one) will use your mouse pointer coordinates to complete. So when
you want to kill someone you should use your mouse to point at him and only then press
your favorit weapon key to shoot.
<p>
Technically there are default bindings for keys in Netrek, but I will not list all
of them here. You can check them under <a href="defaultmap.html">Default Bindings</a>
section.
</body>
</html>
--- NEW FILE: main.css ---
/* Cascading Style Sheet for HTML Help Workshop */

body		{ font-size: 75%; 
			line-height: 125%;   		
			font-family: Verdana, Arial, Helvetica,  }

a:link		{ color: #0000FF; } 

a:active	{ color: #FF33CC; }

a:visited 	{  color: #800080; }

a:hover		{color: #800080;
			font-weight: bold; }

a:sidebar	{color: #339900; }

h1		{ font-size: 125%; 
		margin-bottom: .5em;
		line-height: 125%; }

h2		{ font-size: 115%;  
		margin-top: 1.5em;
		margin-bottom: .5em;  }

h3		{ font-size: 100%; 
		margin-top: 1.2em;  
		margin-bottom: .5em;  }

h4		{ font-size: 100%;
        color: darkmagenta;
		margin-top: 1.2em;  
		margin-bottom: .5em;  }

p		{ margin-top:6pt; margin-bottom: 6pt;	}

p.margin {
	margin-left: 57pt;
	margin-top: -47pt; }
	
p.margin2 {
	margin-left: 57pt; } 
	
li p		{ margin-top: .6em;
		margin-bottom: 0em;  }
		
big		{  font-weight: bold; 
		font-size: 105%;  }
		
ol		{margin-top: .5em; 
		margin-bottom: 0em }	
	
ul		{margin-top: .6em; 	
		margin-bottom: 0em;
		margin-left: 2.75em;  }	

ol ul		{  list-style: disc; margin-top: 2em;  }

li		{padding-bottom: .3em;
		margin-left: -1.25em;  }

dl ul		{ margin-top: 2em;  
		margin-bottom: 0em;  }	/*list item inside a def/term*/

dl		{ margin-top: -1em;  }

ol dl	{ margin-top: -1.5em;
		 margin-left: 0em;  }		/*term/def list inside a numbered list*/

ol dl dl	{  margin-top: 0em;
		margin-left: .2em;  }		/*term/def list inside a term/def list*/

dd		{ margin-bottom: 0em;	/*not currently working*/
		margin-left: 1.5em;  }

dt		{  padding-top: 2em;
		font-weight: bold; 
		margin-left: 1.5em;  }

code	{font-family: Courier; }

pre		{ margin-top: 0em;
		margin-bottom: 1.5em; 
		font-family: Courier;
		}

table 	{ font-size: 100%;
		text-align: left;
		margin-top: 1em;
		}

tr		{ margin: .50em;
		vertical-align: top;
		}
			
th 		{ text-align: left;
		margin: .50em;
		vertical-align: top;
		background: #dddddd;
		}
						
td		{ margin: .50em;
		vertical-align: top;
		}

/* Only use this for sidebars that ARE in a list */
DIV.sidebartext {
	position: relative;
	left: -22px;
	height: 72px;
	width: 300px;
	margin-top: .6em;
	margin-right: 3em;
	margin-left: 0;
	margin-bottom: .6em;
	padding-top: .75em;
	padding-right: 6px;
	padding-left: .75em;
	padding-bottom: .75em;
	cursor: hand;
	border-left: 4pt solid #339900;
	background-color: #F0F0F0; }

/* Only use this for sidebars that are NOT in a list */
DIV.sidebartbl {
	height: 72px;
	width: 300px;
	margin-top: .6em;
	margin-right: 3em;
	margin-left: 0;
	margin-bottom: .6em;
	padding-top: .75em;
	padding-right: 8em;
	padding-left: .75em;
	padding-bottom: .75em;
	cursor: hand;
	border-left: 4pt solid #339900;
	background-color: #F0F0F0; }
	
a:visited.sidebar: {
	color: #339900;
	text-decoration: none; }
	
a:hover.sidebar: {
	text-decoration: underline; }

.endlink {
	line-height: 6pt;
	position: relative;
	top: 1pt;
	background-color: transparent;
	font-weight: bold;
	font-size: 7pt;
	font-style: italic;
	color: black;
	text-decoration: none;
	cursor: hand;
	width: 20px;
	height: 8pt;
	padding-top: -2pt;
	padding-bottom: 1pt;
	margin: 0pt;
	border-bottom: 1pt solid #cc0033;
	border-top: 1pt solid #cc0033; }





--- NEW FILE: jointhegame.html ---
<html>
<head>
<title>Joining The Game</title>
<style>@import url(main.css);</style>
<link disabled href="main.css" rel="stylesheet" type="text/css">
</head>
<body>
<h1>Joining The Game</h1>
<p>
After successfull login you will be presented following window:
<p>
<img src="images\jointhegame.gif">
<p>
Next topics will give you short explanation about windows that compose it:
<ul>
<li><a href="motdwindow.html">Message Of The Day</a></li>
<li><a href="serversettings.html">Server Settings</a></li>
<li><a href="teamselect.html">Team Selection</a></li>
</ul>
</body>
</html>
--- NEW FILE: serversettings.html ---
<html>
<head>
<title>Server Settings</title>
<style>@import url(main.css);</style>
<link disabled href="main.css" rel="stylesheet" type="text/css">
</head>
<body>
<h1>Server Settings</h1>
<p>
The top right part of the main screen after successfull login will contain
server settings. These settings define what type of server it is, whether RSA
client is required to play a game there, how much players it is required to
start Tournament mode (T-mode), etc.
<p>
Here is settings window from pickled.psychosis.net:
<p>
<img src="images\serversettings.gif">
<p>
Here is a list of options with brief explanations:
<ul>
<li>Binary verification - whether the client binary should support some kind of verification</li>
<li>Tournament mode - how much players per side are required to start T-mode</li>
<li>Ships allowed - what types of ships are allowed to play on this server</li>
<li>Tractor/Pressor beams - whether tractor/pressor beams are allowed on the server</li>
<li>Kill required for plasma - how much kills should you have in order to get plasma after refit</li>
<li>Rank required for SB - what minimum rank should you have to be able to refit to Starbase</li>
<li>Planets required for SB - what minimum number of planets your team owns is required to be able to get Starbase</li>
<li>Hidden mode - when server will hide your enemies in the fog of war</li>
<li>Multiple Entry Planets - whether ships can be respawned no only around their home planet</li>
<li>Chaos mode - whether chaos mode is enabled or not</li>
<li>Hunter Killer - whether server will send Hunter Killer bot every half hour to clean galaxy</li>
<li>Message to GOD log - whether messages to GOD are saved</li>
<li>SB Transwarp - whether players can transwarp to Starbase ship</li>
<li>Surrender Counter - how much planets on loosin team are required to start surrender counter</li>
</ul>
</body>
</html>
--- NEW FILE: defaultmap.html ---
<html>
<head>
<style>@import url(main.css);</style>
<link disabled href="main.css" rel="stylesheet" type="text/css">
<title>Default Bindings</title>
</head>
<body>
<h1>Default Bindings</h1>
<p>
Here you will find a list of default keys and buttons bindings
<p>
<h2>Keyboard Bindings</h2>
<p>
<h3>Ship Controls:</h3>
<pre>
	<b>0</b> - set speed to 0
	<b>1</b> - set speed to 1
	<b>2</b> - set speed to 2
	<b>3</b> - set speed to 3
	<b>4</b> - set speed to 4
	<b>5</b> - set speed to 5
	<b>6</b> - set speed to 6
	<b>7</b> - set speed to 7
	<b>8</b> - set speed to 8
	<b>9</b> - set speed to 9
	<b>)</b> - set speed to 10
	<b>!</b> - set speed to 11
	<b>@</b> - set speed to 12
	<b>%</b> - set speed to maximum
	<b>#</b> - set speed to 1/2 maximum
	<b>&lt;</b> - decrease speed by 1
	<b>&gt;</b> - increase speed by 1
	<b>k</b> - set course
	<b>p</b> - fire phaser
	<b>t</b> - fire photon torpedo
	<b>f</b> - fire plasma torpedo
	<b>d</b> - detonate enemy torpedoes
	<b>D</b> - detonate your own torpedoes
	<b>S</b> - toggle ships status graph
	<b>]</b> - put shields up
	<b>[</b> - put shields down
	<b>{</b> - cloak
	<b>}</b> - uncloak
	<b>c</b> - toggle cloaking device
	<b>u</b> - toggle shields
	<b>s</b> - toggle shields
	<b>b</b> - bomb planet
	<b>z</b> - beam up armies
	<b>x</b> - beam down armies
	<b>T</b> - toggle tractor beam
	<b>y</b> - toggle pressor beam
	<b>_</b> - turn on tractor beam
	<b>^</b> - turn on pressor beam
	<b>$</b> - turn off tractor/pressor beam
	<b>R</b> - enter repair mode
	<b>o</b> - orbit planet or dock to starbase
	<b>e</b> - starbase docking permission toggle
	<b>r</b> - refit (change ship type)
	<b>l</b> - lock on player/planet
	<b>;</b> - lock on planet/starbase
	<b>*</b> - transwarp to starbase / send practice robot
</pre>
<p>
<h3>Other Controls:</h3>
<pre>
	<b>X</b> - enter macro mode
	<b>X?</b> - show macros window
	<b>L</b> - rotate playerlist to show everyone, players only, observers only
	<b>P</b> - show planets list
	<b>i</b> - get information on player/planet
	<b>I</b> - get extended information on player/planet
	<b>Q</b> - quit
	<b>q</b> - fast quit
	<b>?</b> - switch message windows from split to single setup
	<b>h</b> - help window toggle
	<b>H</b> - toggle hockey lines on tactical (local). Only for hockey servers
	<b>G</b> - toggle hockey lines on galaxy (map). Only for hockey servers
	<b>w</b> - show war declaration window
	<b>N</b> - toggle planet names on tactical
	<b>U</b> - show rankings window
	<b>m</b> - message window zoom
	<b>/</b> - toggle sorted player list
	<b>:</b> - toggle messages recording to log file
	<b>+</b> - toggle UDP options window
	<b>~</b> - toggle sound control window
	<b>'</b> - toggle ping statistics window
	<b>`</b> - toggle packets window
	<b>=</b> - send request to update all galaxy data
	<b>-</b> - send request to update weapons, planets and kills data
	<b>|</b> - send request to update everything except player statistics
	<b>M</b> - show shell tools window
	<b>&</b> - reread configration file
	<b>"</b> - save current configuration to netrekrc.sav
	<b>\</b> - reset dashboard timer to 00:00:00
	<b>v</b> - decrease sound volume by one notch
	<b>V</b> - increase sound volume by one notch
	<b>(space)</b> - hide all windows except tactical/map/messages/playerlist/dashboard
</pre>
<p>
<h2>Mouse Bindings</h2>
<p>
All mouse clicks are translated to keyboard actions. If one of Ctrl, Shift, Ctrl+Shift keys
pressed along with mouse click it will also generate keyboard action.
<p>
Next table will list all possible mouse buttons and the keyboard actions they generate:
<table border=1 cellspacing=0 cellpadding=3>
<tr>
<td><b>Mouse Button</b></td>
<td><b>Keyboard Action</td>
</tr>
<tr>
<td>Left</td>
<td>t</td>
</tr>
<tr>
<td>Shift+Left</td>
<td>%</td>
</tr>
<tr>
<td>Ctrl+Left</td>
<td>s</td>
</tr>
<tr>
<td>Ctrl+Shift+Left</td>
<td>T</td>
</tr>
<tr>
<td>Middle</td>
<td>p</td>
</tr>
<tr>
<td>Shift+Middle</td>
<td>D</td>
</tr>
<tr>
<td>Ctrl+Middle</td>
<td>c</td>
</tr>
<tr>
<td>Ctrl+Shift+Middle</td>
<td>y</td>
</tr>
<tr>
<td>Right</td>
<td>k</td>
</tr>
<tr>
<td>Shift+Right</td>
<td>#</td>
</tr>
<tr>
<td>Ctrl+Right</td>
<td>i</td>
</tr>
<tr>
<td>Ctrl+Shift+Right</td>
<td>;</td>
</tr>
<tr>
<td>Fourth</td>
<td>f</td>
</tr>
<tr>
<td>Shift+Fourth</td>
<td>0</td>
</tr>
<tr>
<td>Ctrl+Fourth</td>
<td>z</td>
</tr>
<tr>
<td>Ctrl+Shift+Fourth</td>
<td>l</td>
</tr>
<tr>
<td>Fifth</td>
<td>b</td>
</tr>
<tr>
<td>Shift+Fifth</td>
<td>d</td>
</tr>
<tr>
<td>Ctrl+Fifth</td>
<td>x</td>
</tr>
<tr>
<td>Ctrl+Shift+Fifth</td>
<td>*</td>
</tr>
</table>
<p>
<b>Fourth</b> and <b>Fifth</b> are so called <b>X Buttons</b> that Microsoft added to their
IntelliPoint mouses. You can use IntelliPoint drivers to map them to keys, but instead
of doing that you can just use regular <b>buttonmap</b> in NetrekXP Mod
</body>
</html>
--- NEW FILE: commandline.html ---
<html>
<head>
<style>@import url(main.css);</style>
<link disabled href="main.css" rel="stylesheet" type="text/css">
<title>Command Line Options</title>
</head>
<body>
<h1>Command Line Options</h1>
<p>
Most of times you will not use command line to start client.
However it is handy to remember -h and -p options, so you will be able
to connect to server even when something is wrong with metaserver (which happens
from time to time). Or for instance the server you want to connect to
doesn't report itself to metaserver (so it won't appear in the metaserver window).
<p>
It is good to remember that default ports for most of servers are 2592 for players
and 2593 for observers. So if you want to observe game on continuum.us.netrek.org
you will use "netrek -h continuum.us.netrek.org -p 2593".
<p>
Here is the list of command options for NetrekXP Mod:<br>
<br>
<pre>
  -h &lt;server&gt;               : specify server name to connect to
  -p &lt;port&gt;                 : specify port number to connect to
  -r &lt;configuration file&gt;   : specify configuration file to read
  -s &lt;socket port&gt;          : specify socket port
  -u                        : show usage information
  -A &lt;password&gt;             : specify character password
  -C &lt;name&gt;                 : specify character name
  -U &lt;udp port&gt;             : specify UDP port
  -o                        : use old style binary verification
  -R                        : use RSA binary verification
  -P                        : log server packets
  -c                        : check players on server and return list
  -f &lt;file name&gt;            : record game to file (can be viewed later with -F)
  -F &lt;file name&gt;            : view recorded game
  -l &lt;file name&gt;            : record all messages to log file
  -m                        : connect to metaserver (default)
  -k                        : display known servers
  -n                        : show console window
  -v                        : display client version info
</pre>
<br>

</body>
</html>
--- NEW FILE: configsyntax.html ---
<html>
<head>
<style>@import url(main.css);</style>
<link disabled href="main.css" rel="stylesheet" type="text/css">
<title>Configuration File Syntax</title>
</head>
<body>
<h1>Configuration File Syntax</h1>
<p>
Configuration file is regular text file that can contain comments, empty lines and
configuration definitions.
<p>
<h2>Comments</h2>
<p>
Every line that has hashmark (<b>#</b>) as its first character is comment line and
will be ignored.
<p>
<h2>Configuration Options</h2>
<p>
The general syntax for any of configuration options is:
<p>
<code><b>keyword: &lt;value&gt;</b></code>
<p>
All configuration option keywords are <b>case incensitive</b>
<p>
Most of option keywords can have three additional suffixes to enable fine tuning
of options:
<p>
<ul>
<li>
<code><b>keyword.observer: &lt;value&gt;</b></code> - this suffix will enable
option only in case you are logged in to server as observer
<p>
Example:
<br>
<code>buttonmap.observer: 1l2I3i</code> - will set different buttonmap when you
observe game
</li>
<p>
<li><code><b>keyword.&lt;servernick&gt;: &lt;value&gt;</b></code> - this suffix will
set option only if you are connected to server &lt;servernick&gt;
<p>
Note that in order to define &lt;servernick&gt; you should define
<b><code>server.&lt;servernick&gt;: &lt;server host name&gt;</code></b>
<p>
Example:
<br>
<code>server.continuum: continuum.us.netrek.org</code> - this option sets
servernick for continuum.us.netrek.org to be continuum
<br>
<code>keymap.continuum: a2d%</code> - this option defines custom keymap for
server with 'continuum' as its servernick
</li>
<p>
<li><code><b>keyword.&lt;servertype&gt;: &lt;value&gt;</b></code> - this suffix will
set option only if you are connected to server with &lt;servertype&gt; type.
<p>
Note: the client will automatically set &lt;servertype&gt; only if you connect from <a href="metaserver.html">Metaserver Window</a>
<p>
If you want to define &lt;servertype&gt; for specific server that is not there or
you connect to server from command line you can use <b><code>servertype.&lt;servernick&gt;: &lt;type of server&gt;</code></b> where
&lt;type of server&gt; can be one of following:
	<ul>
	<li><code>paradise</code></li>
	<li><code>bronco</code></li>
	<li><code>chaos</code></li>
	<li><code>inl</code></li>
	<li><code>sturgeon</code></li>
	<li><code>hockey</code></li>
	<li><code>dogfight</code></li>
	</ul>
<p>
Example:
<br>
<code>server.continuum: continuum.us.netrek.org</code> - this will set servernick
for continuum.us.netrek.org to be continuum
<br>
<code>serverType.continuum: bronco</code> - this will set servertype for continuum
to be bronco
<br>
<code>keymap.bronco: a2d%</code> - this will set keymap for any bronco server
</li>
</ul>
<p>
The precedence for the keywords is as follows:
<ul>
<li><code><b>keyword.observer: &lt;value&gt;</b></code></li> - best match
<li><code><b>keyword.&ltservernick&gt;: &lt;value&gt;</b></code></li>
<li><code><b>keyword.&ltservertype&gt;: &lt;value&gt;</b></code></li>
<li><code><b>keyword: &lt;value&gt;</b></code></li> - worst match
</ul>
<p>
There are three types of values that can appear in the configuration:
<p>
<ul>
<li>Boolean</li>
	<ul>
	<li><b>on</b>, <b>true</b>, <b>1</b> - to enable option</li>
	<li><b>off</b>, <b>false</b>, <b>0</b> - to disable option</li>
	</ul>
<li>Number</li>
	<ul>
	<li><b>integer</b></li>
	</ul>
<li>String</li>
	<ul>
	<li><b>string of characters</b></li>
	</ul>
</ul>
<p>
Examples:
<p>
<ul>
<li><code>keepPeace: on</code> - will enable keepPeace option</li>
<li><code>planetBitmap: 2</code> - will assign value of 2 to planetBitmap option</li>
<li><code>buttonmap: 1t2p3k</code> - will assign string '1t2p3k' to buttonmap option</li>
</ul>
</body>
</html>
--- NEW FILE: motdwindow.html ---
<html>
<head>
<title>Message Of The Day</title>
<style>@import url(main.css);</style>
<link disabled href="main.css" rel="stylesheet" type="text/css">
</head>
<body>
<h1>Message Of The Day</h1>
<p>
Top left part of the Team Selection window is called Message Of The Day
or MOTD. This window contains whatever information server administrator (GOD)
decided to display.
<p>
<img src="images\motdwindow.gif">
<p>
You can scroll text in the window using <b>'f', 'b', 'F', 'B'</b> keys to scroll
one line forward, one line backward, one page forward, one page backward.
<p>
You can also press <b>'R'</b> to send statistics reset request to server.
</body>
</html>
--- NEW FILE: remapping.html ---
<html>
<head>
<style>@import url(main.css);</style>
<link disabled href="main.css" rel="stylesheet" type="text/css">
<title>Changing Defaults</title>
</head>
<body>
<h1>Changing Defaults</h1>
<p>
In order to change default buttons and keys bindings you should be familiar
with <a href="configfile.html">Configuration File</a> and be able to edit
it.
<p>
It is possible to change keyboard mappings in game by going to help window ('h' in
default keymap) and remapping keys by pointing on desired action and pushing key that
you want this action to be bound to. The main problem with that is that these remappings
are not saved anywhere (unless you save them using "Save options" action) and will be
lost after you close the program.
<p>
There are three configuration commands that deal with keyboard and mouse buttons
rebinding (remapping):
<ul>
<li><b>keymap</b> - allows to change keyboard default bindings</li>
<li><b>buttonmap</b> - allows to change mouse default bindings</li>
<li><b>ckeymap</b> - allows to change Ctrl+Key keyboard bindings</li>
</ul>
<p>
<h2>Syntax</h2>
<p>
Same syntax is applied for all of the configuration commands above:
<p>
<code>command: [&lt;key to bind&gt;&lt;action to perform&gt;]+</code>
<p>
Examples:
<p>
<ul>
<li><code>keymap: a2d%</code> - will bind warp 2 speed to key 'a' and maxwarp to key 'b'.</li>
<li><code>buttonmap: 1i3l</code> - will bind info action to mouse button 1 (left button) and
lock action to mouse button 3 (right button).</li>
<li><code>ckeymap: ^cc^vl</code> - will bind cloak action to Ctrl-c and lock action to Ctrl-v</li>
</ul>
<p>
<code><b>buttonmap</b></code> is the tricky one because you should know what button gets what name.
<br>
So here is a table that will list all possible buttons that can be bound there:
<table border=1 cellspacing=0 cellpadding=3>
<tr>
<td><b>Mouse Button</b></td>
<td><b>ButtonMap Representation</b></td>
</tr>
</tr>
<tr>
<td>Left</td>
<td>1</td>
</tr>
<tr>
<td>Middle</td>
<td>2</td>
</tr>
<tr>
<td>Right</td>
<td>3</td>
</tr>
<tr>
<td>Fourth</td>
<td>4</td>
</tr>
<tr>
<td>Fifth</td>
<td>5</td>
</tr>
<tr>
<td>Wheel Up</td>
<td>6</td>
</tr>
<tr>
<td>Wheel Down</td>
<td>7</td>
</tr>
<tr>
<td>Shift+Left</td>
<td>8</td>
</tr>
<tr>
<td>Shift+Middle</td>
<td>9</td>
</tr>
<tr>
<td>Shift+Right</td>
<td>a</td>
</tr>
<tr>
<td>Shift+Fourth</td>
<td>b</td>
</tr>
<tr>
<td>Shift+Fifth</td>
<td>c</td>
</tr>
<tr>
<td>Ctrl+Left</td>
<td>d</td>
</tr>
<tr>
<td>Ctrl+Middle</td>
<td>e</td>
</tr>
<tr>
<td>Ctrl+Right</td>
<td>f</td>
</tr>
<tr>
<td>Ctrl+Fourth</td>
<td>g</td>
</tr>
<tr>
<td>Ctrl+Fifth</td>
<td>h</td>
</tr>
<tr>
<td>Ctrl+Shift+Left</td>
<td>i</td>
</tr>
<tr>
<td>Ctrl+Shift+Middle</td>
<td>j</td>
</tr>
<tr>
<td>Ctrl+Shift+Right</td>
<td>k</td>
</tr>
<tr>
<td>Ctrl+Shift+Fourth</td>
<td>l</td>
</tr>
<tr>
<td>Ctrl+Shift+Fifth</td>
<td>m</td>
</tr>
</table>
<p>
For example <code><b>'buttonmap: 1p4dhi'</b></code> - will create following mapping:
<p>
<ul>
<li><b>Left Mouse Button</b> will map to <b>phaser</b></li>
<li><b>Fourth Mouse Button</b> will map to <b>detonate enemy torps</b></li>
<li><b>Ctrl+Fifth Mouse Button</b> will map to <b>info</b></li>
</ul>
<p>
Almost all players at some point will remap (rebind) default keyboard (and probably mouse) actions
to keys that satisfy their requirements. Feel free to play with key bindings and try to get most
out of it. Just remember that once you got used to some specific layout it will be difficult to
switch to something else.
</body>
</html>