04/08/98 - Team NWO - UO Proxy V1.1

Introduction:
This nifty little program acts as a layer between your client
and OSI's server(s).  It decodes and decompresses the packets that are
sent back and forth, and logs them to specified files.  A note that
the first few packets should not be distributed to others.  The first
packets of both the login server and game server contain confidential
account information.  Distribution of these packets in either encrypted
or decrypted form will most likely result in a lot of problems that
you don't want to deal with.  You have been warned.

WARNING:
Use of this program may be considered a violation of OSI's
end user agreement.  In no way does NWO encourage anyone to use this,
nor will NWO be held responsible for any consequences of the use of this
program.  USE AT YOUR OWN RISK

Use:
The Login Server Proxy Port is the port which your client will
connect to.  The Game Server Proxy Port doesn't really matter, the client
is relayed to this port once it chooses a game server.
The "Route logins to:" fields probably shouldn't be changed, you'll notice
these are copied straight from the login.cfg of the client.
"Log Login Info to:" and "Log Game Info to:" are files (with full pathnames)
to which the login and game packets should be logged to respectively.
"My IP:" should always be 127.0.0.1

You'll need to change your login.cfg in the uo directory.
Make a backup copy (you'll regret it if you don't).  Change all four
lines that do not begin with a semi-colon to read:
LoginServer=127.0.0.1,9000
LoginServer=127.0.0.1,9000
LoginServer=127.0.0.1,9000
LoginServer=127.0.0.1,9000
If you used a different port than 9000 for the Login Server Proxy
Port, use that number at the end of each line instead of 9000.
Click initialize on the UOProxy program, and minimize if you want to.
(The UOProxy dialog displays no new information during logging).
Run your client, login, and you're logging packets.

Note that while this version supports multiple connections, setting "My IP"
to 127.0.0.1 effectively prevents remote connecting clients from getting
past the server selection menu.
In addition, all logging is currently writen to the same files.  Thus
two clients connected at once would still log to the same file, and the
dumped packets would be relatively indistinguishable.  For this reason, it is
suggested that you connect only one client to a UOProxy instance at a time.

-Rhad
Team NWO

Please read packets.txt if you would like to help team NWO get a working
product into release state faster!