If you want to recompile this package on your own server, you MUST have access
to a full JDK, and a web server. There are 3 main directories for the game:
1. The place where your html file is stored for displaying the client applet
2. The place where the classfiles are stored
3. The place where the gamefiles and dictionaries are stored.

On UNIX my suggestions are:
1. $HOME/public_html/
2. $HOME/public_html/java/
3. $HOME/bogglefiles

On Windows or Dos my suggestions are:
1. C:\WWW	(providing your webserver serves from this directory)
2. C:\WWW\JAVA
3. C:\WWW\bogglefiles	(WIN)
3. C:\WWW\BFILES	(DOS)

You need to change the settings.java to reflect which dictionaries you have made
available (I supply English.dict (courtesy of linux, therefore under GNU general 
public licence) and German.dict (courtesy of nic.funet.fi:/pub/unix/security/dictionaries))
Also in settings.java are the hostname of your webserver, and the directory (3.)
: THIS IS ESSENTIAL unless all your clients will be running application clients
instead of applets (java boggle.c)

To compile the java files you need to run through the compile about three times to
resolve the dependencies (they loop) use a compile script like the following:

on UNIX:
<bogglecompile>
#!/bin/bash
rundir=$HOME/public_html/java/
export CLASSPATH=$CLASSPATH:$rundir
javac -d $rundir $*
rmic -d $rundir boggle.server.boggleServer boggle.server.gameServer boggle.server.messageServer
<EOF>

on WIN/DOS:
<bogglecompile.bat> / <bcompile.bat>
SET BOGGLECLASSDIR=C:\WWW\JAVA
@rem CHANGE the above if you have the server (http) dishing out your java from somewhere else
javac -classpath %CLASSPATH%;%BOGGLECLASSDIR% -d %BOGGLECLASSDIR% *.java
rmic -classpath %CLASSPATH%;%BOGGLECLASSDIR% -d %BOGGLECLASSDIR% boggle.server.boggleServer boggle.server.gameServer boggle.server.messageServer
<EOF>

So to compile, go to the directory where all the java files are and do:
bogglecompile *.java
(do it three times to resolve dependencies)
Providing the third compile works, you now need to start the server programs
on the web server. log in to the machine running the web server and do:
rmiregistry & (UNIX)
start rmiregistry (WIN)
now you must perform the following command (NB your classpath must include
the directory (2,) )
java -Djava.rmi.server.codebase=http://yourservername/java boggle.s
(replace yourservername with the DNS name of your web server e.g. www.domain.com)
providing all this works (!) you need to generate the game files:

move the dictionary files available to the directory (3.) and then run:
java boggle.server.multiGen
THIS CAN TAKE HOURS. if you want to shorcut this, e-mail me because I have some
prebuilt ones.
(p.s. you can ignore dictionary panics if they are type 2 with no other errors)

IF YOU JUST WANT TO PERUSE THE CODE
this tree may be helpful to understand the code

This is the package tree for boggle

-+- package boggle
 |
 +-+- package boggle.client
 | |
 | +-+- package boggle.client.games
 | | |
 | | \- bogglePanel
 | |
 | +- gamePanel
 | |
 | +- langDialog
 | |
 | +- mainClient
 | |
 | +- messaging
 | |
 | +- passwordDialog
 | |
 | \- playerViewer
 |
 +-+- package boggle.server
 | |
 | +-+- package boggle.server.games
 | | |
 | | +- babbleGameGen
 | | |
 | | \- boggleGameGen
 | |
 | +- boggleServer
 | |
 | +- boggleServerInterface
 | |
 | +- dictionary
 | |
 | +- dictionaryException
 | |
 | +- fileNotGeneratedException
 | |
 | +- GameGen
 | |
 | +- gameServer
 | |
 | +- gameServerInterface
 | |
 | +- messageServer
 | |
 | +- messageServerInterface
 | |
 | +- multiGen
 | |
 | +- player
 | |
 | \- playerPool
 |
 +- c
 |
 +- codec
 |
 +- s
 |
 +- settings
 |
 +- timer
 |
 \- timerCaller