1. Installation of the JQuake Server
------------------------------------------------------------------------------

The JQuake Server is a Java application that handles
a number of JQuake clients. This will allow a simple
deatchmatch.

The JQuake Server must be run on the http server on
which the JQuake applet is stored. It can either be
started with a java application viewer, like "jview",
or on NT-machines, as a service.

The JQuakeServer.zip should be unzipped recursively
in a subdirectory, e.g. "JQuakeServer".

1.1 Starting it as an application
---------------------------------

When running it with "jview", enter the subdirectory
JQuakeServer and start it with:

jview JQuakeServer [ option1="value1" [ option2="value2" [ ... ] ] ]

where the options are:

port:                ServerPort. Default: 27100
moveRate:            Frequency at which actors are moved. Default: 60.
                      High is good, but if it takes too much CPU-time, it
                      can be lowered.
minMovesPerSend:     Minimum number of moves per send - i.e. max packet
                      transmission frequency will be moveRate / movesPerSend.
                      The clients will automatically request about as much
                      much as they can handle, so this value will only affect
                      clients with very fast computers and good connections.
                      Default: 1
map:                 The map that will be played. Default: binaries/dm4.bin
maxClients:          Maximum number of clients that can connect. Default: 6.
                      The fraglist in the chat-applet will not look nice if
                      you enter a higher value than 6. We'll see if we can 
                      autoresize the chat-applet after maxClients.
welcomePhrase:       The phrase that greets a newly connected player.
                      Default: null
msgLevel:            A higher value prints more messages. Default: 0
					 -1: No messages
                      0: Only prints "initializing" and "initialized"
                      1: Prints connection requests and stuff
                      2: Prints even more.
                      3: Prints a lot.
                      More than 1 is not recommended except for testing purposes.
                      More than 0 is not recommended for services on NTs.

example:
jview JQuakeServer port="27100" welcomePhrase="Welcome to Our Server"

Make sure that the server is run using a JIT-compiler. Sometimes you need
to pass an option to "jview", like "-jit".

1.2 Starting it as a NT service
-------------------------------

Starting it as a NT service is a bit more complicated.
We'll add the description soon.


2. Setting up the JQuake Applet.
------------------------------------------------------------------------------

Hopefully you have received or snatched a HTML page with the JQuake Applet.
Parameters are given with the same syntax as the server when running 
as a standalone application. When running as an applet it's just applet 
parameters.
One applet parameter that is always required is the "CABBASE", which should 
be "JQuakeNChat.cab". Other parameters are:

mipmapLevel:        1 if all textures should be resampled with a lower
                     resolution, to save memory. Default: 1
zoom:               1 if scene should be rendered at 160*100 and stretched
                     to 320x200. A bit obsolete, since you can chose with
                     '+' and '-'. Default: 0
sleep:              The client will sleep( sleep ) between each frame, if
                     sleep > 0. Default: 0. The framerate will, of course,
                     drop if you sleep, so it's not recommended.
map:                Map to be played. Default: "binaries/dm4.bin". Must be
                     same as map-parameter the server was started with.
deathmatch:         1 if you're running a server that the client should
                     connect to. Default: 0
serverAddress:      IP-address of the server. Default: getCodeBase - i.e.
                     The address of the server on which the applet is stored,
                     so normally this parameter is not needed, since the server
                     must be run there. Mainly used for debugging purposes or
                     when running it as a standalone application.
serverPort:         Port on which the server is listening. Default: 27100.
                     Must be same as the port-parameter the server was started
                     with.
maxClients:         Maximum number of clients that can connect to the server.
                     Important: must be same as on server! Default: 6
failsafe:           1 turns off networking and displays images with a slightly
                     more "reliable" technique. Default: 0. Not needed for any
                     browser, as far as I know.
gif:                1 makes JQuake load GIF-images instead of JPG-images.
                     GIFs are larger and are not included in the .CAB-file,
                     so it will take much longer to load, but some VMs can't
                     load JPGs.

3. Additional info.
------------------------------------------------------------------------------

We need information about the server you set up so that we can include a 
reference to your JQuake applet from our pages. We will put an additional link 
to any page you request.

When you add the JQuake applet to any of your pages, add a link to the JQuake
homepage at "http://hem1.passagen.se/carebear/JQuake.htm" and an optional mail
link to "scitech@thermometric.se".

DO NOT redistribute the JQuakeServer and JQuakeClient classes. In this way we
hope not to take undue advantage of ID Software's kindness to use their 
copyrighted material.

You can instead mail us at "scitech@thermometric.se" and ask for copies of 
JQuakeServer and JQuakeClient.