The following info is available:
# # The RPI Netrek Help File...some basic tips # written by Thomas C. Ring # March 7, 1994 # This is intended as an introduction to netrek at RPI. The netrek package home directory is /dept/acm/packages/netrek/2.3/. It will be referred to as $PHOME throughout this document. 1) Some answers to frequently asked questions are in $PHOME/common/doc/. In that directory, the following files are useful: help: this file rgn.faq: the rec.games.netrek FAQ (Frequently Asked Questions) para.faq: paradise server FAQ Defaultrc: the default resource file 2) Simply type "netrek" to see a list of which servers are in use. Then type the name of the server after netrek in order to join in. Example: netrek calvin will connect you to the server at calvin.usc.edu 3) Remember the 'h' key will list the commands. 4) You can customize the starting features by creating a file called .xtrekrc in your home directory. Several sample .xtrekrc files are found in the $PHOME/common/doc directory. cp $PHOME/common/doc/xtrekrc1 ~/.xtrekrc or cp $PHOME/common/doc/xtrekrc2 ~/.xtrekrc will do the trick. 5) Netrek is a team game, and communication is a very important part of teamwork, so make sure you have the message window open. (The ? toggles it.) 6) Try practicing on an empty server first, to get the basics. Then, when you feel comfortable, join in on a battle and get some experience. If you have any questions, your teammates will usually be very helpful. 7) And remember...if you have any problems with the package, send e-mail to the administrator.
netrek - netrek 2.3p9 paradise client
netrek netrek -h servername [ -p connect port ] [ -r defaultfile ] netrek server-pattern [ -r defaultfile ]
"netrek" is actually a shell script interface to the real netrek-paradise program file. It is provided for ease of use of the user. This man page covers only use of the shell script, not how to play netrek in general. For information on general netrek playing, please see the files in /dept/acm/packages/netrek/2.3/common/doc/.
Without any options, netrek will display the list of servers that it currently supports, by running the meta program, a utility which contacts the netrek metaserver to obtain current statistics regarding gameplay. You can type meta help for more information about the meta program. If the first argument to netrek does not begin with a minus sign, it is assumed to be a server pattern, and the script will attempt to match the provided pattern to an actual server hostname (and port number) in the server file. example% netrek bronco Calling bronco.ece.cmu.edu on port 2592. If there is a server that you want to play on but is not listed, you can use the -h parameter, and an optional port number. example% netrek -h mist.cs.orst.edu Calling mist.cs.orst.edu port 2592 If you have a resource file someplace other than $HOME/.xtrekrc, then you can specify it with -r defaultfile. This will work with any of the above option modes, except when retrieving a server listing. If the -r option is not provided, the program will look for a file called .xtrekrc in your home directory. If that file does not exist, a default resource file will be used. example% netrek bronco -r $HOME/public/xtrekrc Calling bronco.ece.cmu.edu on port 2592
/dept/acm/packages/netrek/2.3/common/bin/netrek The shell script /dept/acm/packages/netrek/2.3/common/doc/servers Modified list of servers from rec.games.netrek ~/.xtrekrc Individual client customization file
Shawn A. Collenburg, email@example.com Kenny Zalewski, firstname.lastname@example.org