🚀 go-pugleaf

In article <1992Nov12.173229.16605@infodev.cam.ac.uk>, scf11@cl.cam.ac.uk (S.C. Farrar) writes:
>xtrek
>i am a total novice at these types of things, and i will have to learn somewhere
>Please help me .....
>Simon.
>
I have the same problem will some please explain how to get going in this 
game

Please,Please,Please
--Andrew
------------------------------------------------------------------------------
               ___                 *
  ___....-----'---`-----....___    *   Andrew Grant
   ___`---..._______...---'___     *   Box M-1276
  (___)      _|_|_|_      (___)    *   Mount Allison University
    \\____.-'_.---._`-.____//      *   Sackville, N.B. Canada
     `~~~~`.__`---'__.'~~~~'       *   E0A 3C0
              ~~~~~                *

This was stolen from rec.games.netrek

Article: 5764 of rec.games.netrek
Xref: bham rec.games.netrek:5764 news.answers:3412
Path: bham!warwick!pipex!uunet!think.com!spool.mu.edu!agate!soda.berkeley.edu!tom
From: tom@soda.berkeley.edu (Tom Holub)
Newsgroups: rec.games.netrek,news.answers
Subject: rec.games.netrek FAQ List
Supersedes: <netrekFAQ_716953128@soda.berkeley.edu>
Followup-To: rec.games.netrek
Date: 23 Oct 1992 03:14:04 GMT
Organization: University of California, Berkeley
Lines: 337
Approved: news-answers-request@MIT.Edu
Expires: 4 Dec 1992 03:13:47 GMT
Message-ID: <netrekFAQ_719810027@soda.berkeley.edu>
Reply-To: tom@soda.Berkeley.EDU
NNTP-Posting-Host: soda.berkeley.edu
Originator: tom@soda.berkeley.edu

Archive-Name: netrek/faq
Last-Updated: 18 Sep 1992
Changes: None.


TABLE OF CONTENTS:

 1. What is Netrek?

 2. It sounds interesting; how do I get started?

 3. What's the difference between Xtrek and Netrek?

 4. I've seen a game called Nettrek for the Macintosh; is that the same
    thing as Netrek?

 5. Can I play Netrek on my Mac/IBM PC/Amiga?

 6. I would like to start a new server; what kind of hardware will I need?

 7. I'm trying to start a new server, and I'm having problems.  Where can I
    get help?

 8. I compiled the client source, but every time I try to connect to a server 
    it kicks me out or tells me to get a 'blessed' binary.  What gives?

 9. The game runs fine, but when the Netrek window comes up, I can't type
    anything into it.  How can I fix this?

10. OK, the game runs fine and I found a server and logged in, but there
    doesn't seem to be anyone else around.  How can I find a game with
    people in it?

11. OK, now I'm in a game with other people.  What do I do?

12. When I'm playing the game, people keep sending messages to me.  How can
    I talk back to them?

13. I would like to change what some of the keys do; for example, I'd
    like 't' instead of 'T' to activate my tractor beam.  Is there a way
    to change this?

14. How does the rating/promotion system work?

15. I keep dying.  How can I get better at the game?

16. What is 't-mode'?

17. What does DI stand for, anyway?

18. Some of the servers and binaries are called 'UDP'; what does that mean?

19. I keep reading about the INL; what is it?

20. Where can I get the most recent copy of this FAQ list?

21. My GPA has fallen 25% since I started playing Netrek last semester.
    How do you find time to do your homework and still make Admiral?
 

Subject: What is Netrek?

 Netrek is a 16-player graphical real-time battle simulation with a 
Star Trek theme.  The game is divided into two teams of 8 (or less), who
dogfight each other and attempt to conquer each other's planets.  There
are several different types of ships, from fast, fragile scouts up to
big, slow battleships; this allows a great deal of variance in play
styles.

 Netrek is set up as a client/server combination; if you want to play,
you'll need the client binary for your machine (most are X-based).


Subject: It sounds interesting; how do I get started?

 First, you need to get a client binary for your machine; read the 
Netrek FTP List (which is usually posted along with this FAQ
list) to find an FTP site.  The client should run on anything that
runs X Windows, although the slower your machine is, the harder it's
going to be to play.  Slow networks are even harder to play with.

If you don't know how to use FTP, ask your local guru about it.

If you don't have access to FTP, you can use the mail server at
decwrl.dec.com.  Mail ftpmail@decwrl.dec.com with 'help' in the body
(nothing else) and you'll get an automatic reply with instructions.

Once you have the binary, rename it to something logical like 'netrek'
and run it with 'netrek -h <hostname> -p <port>'.  Read the Netrek Server
List to find a server near you; the nearer, the better.

If you get a 'netrek: Permission denied' message, try 'chmod 755 netrek'.
After the game is over, try 'man chmod', it's too important to not 
know about.


Subject: What's the difference between Xtrek and Netrek?

 Xtrek is a precursor to Netrek.  It has many of the same elements,
but it doesn't work as well because it isn't set up as a client-server
combination.  

Unfortunately, Netrek is often called Xtrek.  This causes much confusion.
This newsgroup really is dedicated to Netrek, but feel free to talk about
Xtrek if you want; many people here play both.


Subject: I've seen a game called Nettrek for the Macintosh; is that the same
	 thing as Netrek?

 No.  Nettrek is in the same family as Netrek (it's unclear which was
created first), but it's not the same game.  It runs over Appletalk
and doesn't have a whole lot of complexity.  If you're interested in it, 
the original version can be found in most net archive sites that support
Mac games.  The most recent version is a commercial program called
"Nettrek 3.0 - The Real Version," and is published by Premiere Technology,
Inc.


Subject: Can I play Netrek on my Mac/IBM PC/Amiga?

 Probably not.  If you aren't connected directly to the net via
ethernet card or SLIP, you can't.  If you ARE connected via ethernet but
aren't running X windows, you have a chance--there are ports for 
the Mac and the Amiga in the works, but nothing has yet been released.
If you're running Unix and X windows, you should be able to compile
the source and it should work, emphasis on the 'should.'


Subject: I would like to start a new server; what kind of hardware will 
	 I need?

 The server should run on anything that has Sys V shared memory and a good 
amount of CPU power.  Good net connections are essential if you want
lots of players.

Read the Netrek FTP list to find out where you can get the server 
source.

Please get the permission of your sysadmins before setting up a server.
Netrek doesn't need any additional bad publicity.


Subject: I'm trying to start a new server, and I'm having problems.  Where can
	 I get help?

 Read the Netrek FTP list to find out where the server-secrets files are 
stored (currently at gs69.sp.cs.cmu.edu).

 There is also a server maintainer's mailing list, netrek@iastate.edu.
If you want to be put on the list, mail a short message to 
netrek-request@iastate.edu and include the amount of C experience
you have, how much you know about netrek code, and anything else
that might be interesting.


Subject: I compiled the client source, but every time I try to connect to
	 a server it kicks me out or tells me to get a 'blessed' binary.  
	 What gives?

 It's possible to modify the client source to do lots of tedious tasks
(like aiming, dodging, that sort of thing) for you.  Since this gives
you a big advantage over a mere human, netrek has a way of knowing whether
you have a client that was compiled by the netrek Gods or by you.  If
you compiled it, netrek will assume it's a cyborg, and will kick you out
if it's not cyborg hours.  Check the Netrek Server List for cyborg
hours of the servers; sometimes they're legal, sometimes they aren't.  

  If you're not interested in playing a modified binary, get one of the 
pre-compiled 'blessed' binaries available at any of the FTP sites.  If 
there isn't a blessed binary for your particular machine, get in touch 
with one of the netrek Gods (sfd@miro.Berkeley.EDU, scott@sting.Berkeley.EDU,
or mehlhaff@soda.Berkeley.EDU) and they'll try to help you out.

   If you *are* interested in playing a modified binary, get the source
from one of the FTP sites and start hacking, or download one of the
public cyborgs.  It's probably not a good idea for new players to
use cyborgs; cyborg players get called lots of nasty names, and
they tend not to learn how to play the game (since their client is
doing most of the work).


Subject: The game runs fine, but when the Netrek window comes up, I can't 
	 type anything into it.  How can I fix this?

This is a problem under a few window managers (OpenWindows and ovlwm, for
example); it's netrek's fault, but you can fix is by adding the line
"<window manager name>.FocusLenience: True" to your .Xdefaults file.
Log out and log back in and it should work.


Subject: OK, the game runs fine and I found a server and logged in, but there
	 doesn't seem to be anyone else around.  How can I find a game with
	 people in it?

Eric Mehlhaff has written a nifty little hack called METASERVER.
Do 'telnet bigdog.cs.berkeley.edu 2520' and it will dump out a list
of servers with the number of people currently on each one.
Andy McFadden, not to be outdone, has modified it and created
Metaserver II; telnet charon.amdahl.com 3520-3524 gives information
in a number of formats.


Subject: OK, now I'm in a game with other people.  What do I do?

The first thing you should do is bring up your message window (by
hitting '?') and your player list (by hitting 'L').  Pressing a number
key chooses your warp speed.  The left mouse button fires torpedos at
your cursor, the middle mouse button fires phasers at your cursor, and 
the right mouse button turns your ship towards your cursor.  Hitting
'h' will bring up a help window with a list of basic commands.


Subject: When I'm playing the game, people keep sending messages to me.  
	 How can I talk back to them?

On the bottom right-hand side of your main window you'll see two 
long boxes.  The top one is where messages like "Not enough fuel for
phaser" come up just before you die.  The bottom one is the one you
use to talk to people.  Move your cursor down there and type a character
to choose who to send the message to: 'A' for ALL, the capitalized 
team letter for the team (i.e., 'F' for Federation), or the player
number for a message to a single player (i.e., 'c' to send to Rc).
Type your message and hit enter when you're done.  Don't do this in
combat.


Subject: I would like to change what some of the keys do; for example, I'd
	 like 't' instead of 'T' to activate my tractor beam.  Is there 
	 a way to change this?

There are two ways: first, do a shift-O.  This brings up the options
window.  Near the bottom there is a box for 'New keymap entries'.  
Move your cursor to this box and type your new keymap entries.  The
format is <newchar><oldchar>, so 'tT' will remap tractor beam to 't'.

Netrek also recognizes a .xtrekrc file; a 'keymap:' line in there 
will allow you to map as many as you want.  Format is the same
as above.


Subject: How does the rating/promotion system work?

 Do a shift-I on yourself; you'll see four ratings there, one for planets,
one for bombing, one for offense, and one for defense.  The planet, 
bombing, and offense ratings are measured in DI/hour; for each planet
you take, army you bomb, and player you kill you get a certain amount
of DI (which varies depending on the server)--the average amount per
hour is your rating.  Your rating is equal to (your DI/your hours)/
(total DI/total hours); therefore, if you have a bombing rating of
2.0, you bomb twice as many armies as the average person on the server.
This is true for all ratings.  All ratings are updated only in t-mode.

 Now do a shift-U.  Listed there are the thresholds for each rank.  
Your overall rating is your planets+bombing+offense.  To make a rank,
you need to have the DI required for that rank, and your ratings need
to be above the rating required for that rank (i.e., to make Admiral,
you need 320 DI and your ratings need to be above 8.0).  You can also
make a ranking by having ratings good enough for a level and *twice*
the DI you would need for the next level (So you can make Admiral 
with ratings of 7.0 and 640 DI).  This equation is recursive once, so you
can also make it with 6.0 ratings and 1280 DI (which would take about 
200 hours!).  You can't make it with 5.0 ratings and 2560 DI; not
only would you flunk out first, the server wouldn't promote you anyway.

 On most servers, your defense also needs to be above .8 to advance
past Lt. Commander.  

Note that suggestions on how to improve the rating system occur
about twice a week in rec.games.netrek, and the general consensus
is that it isn't worth the hassle.


Subject: I keep dying.  How can I get better at the game?

 The best way is probably to talk with someone who knows how to play.
There is also an archive of hints and suggestions on how to play 
better; read the Netrek FTP List to find out where it is
located.


Subject: What is 't-mode'?

 T-mode is short for 'tournament mode.'  To keep some integrity in the
database, ratings are calculated only when there are a certain number
of people in the game (actually, when there are a certain number of
people on two separate teams.  On many servers, you need 4 players
on 2 different teams; 4 teams of 2 players won't do it).  When 
the game goes into t-mode, there will be a 't' flag in your list
of flags, and there will be a message like "Dan Quayle declares self
as Galactic Emperor and chaos breaks out!"  When the game drops out
of t-mode (because someone quit), the 't' flag will disappear and
there'll be a "Dan Quayle is locked up and order returns to the galaxy"
message.  

 It's generally considered rude to bomb or take planets out of t-mode.
Some servers punish people for trying.


Subject: What does DI stand for, anyway?

Destruction Inflicted.


Subject: Some of the servers and binaries are called 'UDP'; what does 
	 that mean?

UDP is a network protocol that is much more lenient than TCP (which is 
what netrek was originally based on).  If you don't have a local server, 
using a UDP client on a UDP server could reduce your lag considerably.  
Read the Netrek FTP List to find out where you can get a UDP client.
(Many thanks to Andy McFadden, Netrek Guru, for writing the UDP
protocol).


Subject: I keep reading about the INL; what is it?

The INL is the Intercollegiate Netrek League, a collection of teams from
different schools around the country who periodically beat up on each
other.  The league is full for the summer season, but will be open
in the fall.  Mail tom@soda.berkeley.edu if you have any questions about it.


Subject: Where can I get the most recent copy of this FAQ list?

 You can either look in the back messages of rec.games.netrek, or
ftp it from one of the archive sites; read the Netrek Server/FTP
list to find out where it is stored.  It's also in the Usenet archive
at pit-manager.mit.edu.  telnet charon.amdahl.com 3524 gives the server
information from the FAQ list.


Subject: My GPA has fallen 25% since I started playing Netrek last semester.
	 How do you find time to do your homework and still make Admiral?

Sorry, nobody's found an answer to this one yet.  Just remember that
(GPA+kill ratio) is constant.

This was stolen from rec.games.netrek

Article: 5765 of rec.games.netrek
Xref: bham rec.games.netrek:5765 news.answers:3413
Path: bham!warwick!pipex!uunet!think.com!spool.mu.edu!agate!soda.berkeley.edu!tom
From: tom@soda.berkeley.edu (Tom Holub)
Newsgroups: rec.games.netrek,news.answers
Subject: Netrek Server List
Supersedes: <netreklist_716953128@soda.berkeley.edu>
Followup-To: rec.games.netrek
Date: 23 Oct 1992 03:14:07 GMT
Organization: University of California, Berkeley
Lines: 468
Approved: news-answers-request@MIT.Edu
Expires: 4 Dec 1992 03:13:47 GMT
Message-ID: <netreklist_719810027@soda.berkeley.edu>
References: <netrekFAQ_719810027@soda.berkeley.edu>
Reply-To: tom@soda.berkeley.edu
NNTP-Posting-Host: soda.berkeley.edu
Originator: tom@soda.berkeley.edu

Last-Updated: 22 Oct 1992
Archive-Name: netrek/server-list
Changes: Various updates.


This is a list of all known public Netrek servers.  If you know of any 
others, or if any of my information is wrong, please mail
tom@soda.Berkeley.EDU.

Note: All servers are UDP unless noted otherwise.


Server name			INET address	Port	Notes

bigdog.cs.berkeley.edu 		128.32.240.123	2592	Last Cal server.

sickdog.cs.berkeley.edu		128.32.240.135	2592	Down for good.

bronco.ece.cmu.edu		128.2.210.65	2592	Most popular server.

rwd4.mach.cs.cmu.edu		128.2.209.169	2592	CMU.

hpserv.math.tamu.edu		128.194.7.8	2592	Down.

netrek.cis.ksu.edu		129.130.10.87	5855	KSU chaos.

hockey.ksu.edu 			129.130.6.10	2592	KSU hockey.

peanuts.informatik.uni-tuebingen.de 134.2.14.1	2592	Germany.

bayes.ibr.cs.tu-bs.de		134.169.34.33	5855	Germany.

iacrs2.unibe.ch			130.92.11.4	592	Switzerland.

uhura.fmi.uni-passau.de		132.231.51.224	21212	Germany.

legend.cma.fr			192.33.149.15	2592	France.

borkum.informatik.uni-rostock.de  139.30.5.27	2529	Apparently down.

iota42.mtek.chalmers.se		129.16.60.82	2592	Sweeden.

netrek.chemietechnik.uni-dortmund.de 129.217.174.20  592  Germany.

diamant.informatik.uni-oldenburg.de 134.106.21.2  2592	Germany.

deakin.anu.edu.au		150.203.15.26	592	Australia, no UDP.

ghost.dsi.unimi.it		149.132.1.2	2592	Italy.

netrek.cs.bham.ac.uk		147.188.202.1	2592	U.K.

melmac.risc.uni-linz.ac.at	140.78.140.60	2592	Austria.

fisher.psy.vu.nl		130.37.96.2	2592	Amsterdam.

calvin.usc.edu			128.125.62.143	2592	USC.

tbird.cc.iastate.edu		129.186.140.11	2592	Iowa State.

doorstop.design.iastate.edu	129.186.8.6	2592	Iowa State, INL.

panther.ecss.iastate.edu	129.186.141.248	2592	Borg-oriented.

ultrix.csc.usf.edu		131.247.31.1	2592	Florida, no UDP.

fife.ecn.purdue.edu		128.46.130.169	2592	Purdue.

sturgeon.cs.washington.edu	128.95.1.58	2592	Washington.

harvey.cs.umd.edu		128.8.128.178	2592	Maryland.

discovery.cl.msu.edu		35.8.1.220	2592	Michigan.

esrg.ucsb.edu			128.111.228.1	2592	UC Santa Barbara.

netrek.atd.ucar.edu		128.117.78.10	2592	Colorado.

flint.cs.brown.edu		128.148.37.33	2592	User's choice.

netrek.cs.mcgill.ca		132.206.51.3	2592	Canada, no UDP.

romulus.ulowell.edu		129.63.17.1	2592	REPLACES bigmax.

garnet.cdf.toronto.edu		128.100.31.36	5555	Canada.

kensho.biosci.arizona.edu	128.196.124.16	2592	Arizona chaos.

geo1s.mps.ohio-state.edu	128.146.130.2	2592	Ohio State.

b62150.student.cwru.edu		129.22.242.198	2592	Case Western.

newton.physics.ucla.edu		128.97.23.41	2592	Apparently down.

tramp.cc.utexas.edu		128.83.135.26	2592	Return of Foghorn!

netrek.icaen.uiowa.edu		128.255.21.58	2592	Now Sturgeon source.


Comments and server configurations:

NOTE: It is an excellent idea to read the MOTD when you first log
on to a server (use 'f' and 'b' to move forwards and backwards through
the news).


bigdog.cs.berkeley.edu
Server source: Scam.
UDP: Version 1.0.
Hours: 5PM to 8AM Pacific time Monday-Friday, all day on weekends.
T-mode: 4 on 4.
Cyborgs: Never allowed.  Blessed binaries required.
Theme nights: Monday and Tuesday, three-race war.
Ping time from ocf: 15-30.
Maintainer: jh@bigdog.cs.berkeley.edu.
Comments: Hosers are back.  Transwarp (warp 60) to your starbase by 
	  locking on to it and hitting '*'.  Now can 'nuke' planets;
	  read the MOTD to see how.  METASERVER resides here; telnet 
	  bigdog.cs.berkeley.edu 2520.

sickdog.cs.berkeley.edu: This server is down for good.

bronco.ece.cmu.edu:
Server source: Bronco sources (this is where they get their name).
UDP: version 1.0.
Hours: 5PM-9AM Eastern time Monday-Friday, all day on weekends.
T-mode: 5 on 5.
Ping time from ocf: 130-200.
Ping time from cmu: 5-8.
Ping time from utexas: 100-150.
Maintainer: george@ece.cmu.edu
Comments: The biggest East Coast server, t-mode nearly every night.
	  No profanity allowed.
	  Bronco is apparently back up, but I have no idea who's
	  maintaining it.

rwd4.mach.cs.cmu.edu
Server source: Bronco.
UDP: Version 1.0.
Hours: Open 24 hours.
T-mode: 4 on 4.
Cyborgs: Allowed 9AM-1PM Eastern time, Monday-Friday.
Ping time from ocf: 115-200.
Ping time from cmu: 5-7.
Ping time from utexas: 100-150.
Maintainer: rwd+@cs.cmu.edu.
Comments: Used to be the biggest borg server, now has mostly human hours.
          Usually has t-mode.  No profanity allowed.  During borg hours,
          torps are vector.  Galaxy is reset at 5pm each day.

hpserv.tamu.edu: This server is down.

netrek.cis.ksu.edu
Server source: Bronco source plus galaxy class ships.
UDP: Version 1.0.
Hours: 6PM to 7AM Central time.
T-mode: 4 on 4.
Cyborgs: Discouraged.
Ping time from ocf: 140-200.
Ping time from cmu: 100-150.
Ping time from utexas: 130-250.
Maintainter: jfy@cis.ksu.edu.
Comments: Chaos.  Independent players, wrap-around walls, 
	  Hunterkillers, lots of other stuff.

hockey.ksu.edu
Server source: Bronco source, hockey mode.
UDP: Version 1.0.
Hours: Open 24 hours.
Cyborgs: Allowed.
Maintainer: bav@hobbes.ksu.ksu.edu.
Comments: Hockey mode all the time, send 'help' to player j for details.

peanuts.informatik.uni-tuebingen.de
Server source: Bronco source.
UDP: Version 1.0.
Hours: 5PM-7AM Monday-Friday, all day on weekends.
Cyborgs: Allowed.
Ping time from ocf: 350-1500.
Ping time from utexas: 350-2500.
Maintainer: jw@peanuts.informatik.uni-tuebingen.de.

bayes.ibr.cs.tu-bs.edu
Server source: Bronco source.
UDP: Version 1.0.
Hours: Open 24 hours.
Cyborgs: Always allowed.
Ping time from ocf: 450-700.
Maintainer: schrei@ibr.cs.tu-bs.de.

iacrs2.unibe.ch
Server source: Bronco source.
UDP: Version 1.0.
Hours: Open 24 hours.
T-mode: 2 on 2.
Cyborgs: Allowed except on Monday and Wednesday.
Ping time from ocf: 300-600.
Maintainer: schuetz@iac.unibe.ch.
Comments: Plasmas for everyone, vector torps.

uhura.fmi.uni-passau.de
Server source: Scam source.
Hours: Open 24 hours.
Cyborgs: Always allowed.
Ping time from ocf: 500-5000.
Maintainer: games@kirk.fmi.uni-passau.de.

legend.cma.fr
Server source: Bronco source.
UDP: Version 1.0.
Hours: Open 24 hours.
Cyborgs: Never allowed.
Ping time from ocf: 300-700.
Maintainer: jmt@cma.cma.fr.
Comments: Players here have finally learned how to avoid trans-Atlantic oggs.

borkum.informatik.uni-rostock.de: This server is apparently down.

iota42.mtek.chalmers.se
Server source: Bronco source.
UDP: Version 1.0.
Hours: Open 24 hourss.
T-mode: 2 on 2.
Cyborgs: Never allowed, need local client.
Maintainer: lab@mtek.chalmers.se.
Comments: FTP local binary from duke.me.chalmers.se.

netrek.chemietechnik.uni-dortmund.de
Server source: Bronco source.
UDP: Version 1.0.
Hours: Closed 8 AM to noon Monday-Friday.
Maintainer: hw@plato.Chemietechnik.Uni-Dortmund.DE.
Comments: No Iggy.

diamant.informatik.uni-oldenburg.de
Server source: KSU Galaxy.
UDP: Version 1.0.
T-mode: 2 on 2.
Cyborgs: Discouraged.
Hours: All day for local players, closed during the day from elsewhere.
Maintainer: Klaus.Moeller@Informatik.Uni-Oldenburg.DE.
Comments: Robots use fuel.

deakin.anu.edu.au
Server source: Bronco source.
UDP: Version 1.0.
Hours: Open 24 hours, but take it easy during working hours.
Cyborgs: Discouraged.
Maintainer: James.Ashton@syseng.anu.edu.au
Comments: brand new and hardly used.

ghost.dsi.unimi.it
Server source: Bronco source.
UDP: version 1.0.
Hours: Open 4PM-10AM Monday-Friday, all day on weekends.
Cyborgs: Always allowed.
Ping time from ocf: 300-500.
Maintainer: carlo@ghost.dsi.unimi.it.

netrek.cs.bham.ac.uk
Server source: Bronco source.
UDP: Version 1.0.
Hours: 5PM to 8AM British Summer Time Monday-Friday, all day weekends.
T-mode: 4 on 4.
Cyborgs: Discouraged.
Maintainer: A.Willams@cs.bham.ac.uk.

melmac.risc.uni-linz.ac.at
Server source: Bronco source.
UDP: Version 1.0.
Hours: Open 24 hours.
T-mode: 2 on 2.
Cyborgs: Discouraged. 
Maintainer: ppregler@risc.uni-linz.ac.at.
Comments: There is an INL server running here, mail the maintainer to
	  use it.

fisher.psy.vu.nl
Server source: Brongo source.
UDP: Version 1.0.
Hours: Open 24 hours.
T-mode: 3 on 3.
Cyborgs: Discouraged.
Maintainer: rob@psy.vu.nl

calvin.usc.edu
Server source: Scam source.
UDP: Version 1.0.
Hours: Open 24 hours.
Cyborgs: Never allowed, blessed binary required.
Ping time from ocf: 100-150.
Maintainer: dank@usc.edu.
Comments: Uncloak time now standard.

tbird.cc.iastate.edu
Server source: Bronco source (hacked).
Hours: 5PM to 8AM Central time Monday-Friday, all day on weekends.
Ping time from ocf: 180-250.
Ping time from cmu: 80-200.
Maintainer: explorer@iastate.edu.

doorstop.design.iastate.edu
Server source: INL source.
UDP: Version 1.0.
Hours: Open 24 hours.
T-mode: 4 on 4.
Cyborgs: Allowed during the day, sometimes.
Maintaner: isae@iastate.edu.
Comments: This is now a public INL server, home port 2592, away 3592.

panther.ecss.iastate.edu
Server source: Bronco source.
UDP: Version 1.0.
Hours: 5PM to 8AM Central time Monday-Friday, all day on weekends.
Cyborgs: Always allowed.
Maintainer: borg-god@iastate.edu.

ultrix.csc.usf.edu
Server source: Scam source.
UDP: No.
Hours: Open 24 hours.
Cyborgs: Always allowed.
Maintainer: pyro@ultrix.csc.usf.edu.
Comments: Galaxy class ship is really an ATT, available to all.

fife.ecn.purdue.edu
Server source: Bronco source.
UDP: Version 1.0.
Hours: Open 24 hours.
Cyborgs: Allowed Friday 11PM to 8AM, Tuesday 8AM to 11PM.
Ping time from ocf: 120-150.
Maintainer: bdhall@ecn.purdue.edu.

sturgeon.cs.washington.edu
Server source: Sturgeon source (the original).
UDP: Version 1.0.
Hours: Open 24 hours.
Cyborgs: Always allowed.
Ping time from ocf: 50-80.
Maintainer: tsang@june.cs.washington.edu.
Comments: This is an experimental server that used to be on
	  scrod.cs.uwashington.edu; the modifications will still be called
	  "scrod hacks" to avoid confusion.  Cloakers appear when hit,
	  extended phaser range, and you can trade kills for upgraded
	  ship configurations.  Read the motd or you'll never figure
	  out what's going on.
	  This server used to be on port 3592, the server that was at port
	  2592 is now gone.  Telnet to port 2591 to see who's logged on.

harvey.cs.umd.edu
Server source: Bronco source.
UDP: Version 1.0.
Hours: 7PM-9AM Eastern Monday-Friday, all day on weekends.
Cyborgs: Never allowed, blessed binary required.
Ping time from ocf: 120-180.
Maintainer: jerryw@cs.umd.edu.
Comments: T-mode is probable Tuesday and Thursday between 6PM and 8PM.

discovery.cl.msu.edu
Server source: Bronco source.
UDP: Version 1.0.
Hours: Open 24 hours.
Cyborgs: Allowed on weekends.
Ping time from ocf: 140-250.
Maintainer: mdb@discovery.cl.msu.edu.
Comments: Has been getting t-mode in the afternoon and evening.
	  No profanity allowed.

esrg.ucsb.edu
Server source: Scam source.
UDP: Version 1.0.
Hours: Open 24 hours.
Cyborgs: Always allowed.
Ping time from ocf: 80-160.
Maintainer: terry@esrg.ucsb.edu.
Comments: SB's have mines.

netrek.atd.ucar.edu
Server source: Bronco source.
UDP: Version 1.0.
Hours: Open 4PM to 8AM Monday-Friday, all day on weekends.
Cyborgs: Allowed on Monday.
Ping time from ocf: 120-200.
Maintainer: netrek@stout.ucar.edu.
Comments: No HunterKiller during t-mode.

flint.cs.brown.edu
Server source: Bronco source.
UDP: Version 1.0.
Hours: Open 24 hours.
Cyborgs: Allowed by user choice (see below).
Ping time from ocf: 130-180.
Maintainer: esj@cs.brown.edu.
Comments: This server allows the user to vote on the game setup; the
	  voting process is explained in the MOTD.  It is designed for
	  pickup tournament-style games.

netrek.cs.mcgill.ca
Server source: Bronco source.
UDP: No.
Hours: Open 24 hours.
Cyborgs: Never allowed.
Maintainer: kent@cs.mcgill.ca

romulus.ulowell.edu
Server source: Bronco source.
UDP: Version 1.0.
Hours: Currently 24 hours during trial run.
Cyborgs: Allowed Tuesday, Thursday, Saturday, and Sunday.
Ping time from ocf: 110-150.
Maintainer: oneill@ulowell.edu.
Comments: This server used to be on bigmax.ulowell.edu

garnet.cdf.toronto.edu
Server source: Bronco source.
UDP: Version 1.0.
Hours: Midnight-10AM Eastern time.
Cyborgs: Allowed Tuesday.
Maintainer: amid@cdf.toronto.edu.
Comments: Tuesday is experimental day, torps usually vector.

kensho.biosci.arizona.edu
Server source: KSU Galaxy.
UDP: Version 1.0.
Hours: 7PM-7AM Pacific time Monday to Friday, all day weekends.
T-mode: 1 on 1.
Cyborgs: Allowed Mon, Wed, Thu, and Sun.
Maintainer: powell@cs.arizona.edu.
Comments: Ship stats modified, plasmas take more than one phaser to kill,
	  lots of other mods. 

geo1s.mps.ohio-state.edu
Server source: Bronco source.
UDP: Version 1.0.
Hours: 24 hours Monday-Saturday, down during the day on Sunday.
Cyborgs: Never allowed, blessed binary required.
Maintainer: ansari@geo1s.mps.ohio-state.edu.
Comments: Uses Bronco player database.  Bronco-style hockey Thu-Sat.
	  Standard Netrek other times.  Telnet to port 2591 to see who's
	  logged on.

b62150.student.cwru.edu
Server source: Bronco source.
UDP: Version 1.0.
Hours: Open 24 hours.
Cyborgs: Allowed Saturday and Sunday, and 5PM-10PM during the week.
Maintainer: mcn@b62103.student.cwru.edu.
Comments: Vector torps during borg hours.  Promotions are granted by
	  by superior officers only.

newton.physics.ucla.edu: This server is apparently down.

tramp.cc.utexas.edu
Server source: KSU galaxy.
UDP: Version 1.0.
Hours: Open 24 hours.
Cyborgs: Discouraged.
Maintainer: kluge@bolvan.ph.utexas.edu.
Comments: Foghorn is back!  Wrap-around walls, galaxy class ships,
	  ridiculous plasmas, etc, etc.

netrek.icaen.uiowa.edu
Server source: Sturgeon source.
UDP: Version 1.0.
Hours: 5PM-9AM Monday-Friday, all day on weekends.
Cyborgs: Allowed.
Maintainer: milutz@icaen.uiowa.edu.
Comments: Friday nights will be experimental.

Stolen from rec.games.netrek

Article: 5766 of rec.games.netrek
Xref: bham rec.games.netrek:5766 news.answers:3414
Path: bham!warwick!pipex!uunet!think.com!spool.mu.edu!agate!soda.berkeley.edu!tom
From: tom@soda.berkeley.edu (Tom Holub)
Newsgroups: rec.games.netrek,news.answers
Subject: Netrek FTP list.
Supersedes: <netrekFTP_716953128@soda.berkeley.edu>
Followup-To: rec.games.netrek
Date: 23 Oct 1992 03:14:09 GMT
Organization: University of California, Berkeley
Lines: 151
Approved: news-answers-request@MIT.Edu
Expires: 4 Dec 1992 03:13:47 GMT
Message-ID: <netrekFTP_719810027@soda.berkeley.edu>
References: <netrekFAQ_719810027@soda.berkeley.edu>
Reply-To: tom@soda.berkeley.edu
NNTP-Posting-Host: soda.berkeley.edu
Originator: tom@soda.berkeley.edu

Last-Updated: 22 Oct 1992
Archive-Name: netrek/ftp-list
Changes: Various.


This is a list of all known FTP servers where you can find Netrek client and
server code, or anything else.  Mail tom@soda.berkeley.edu with any
comments.

Name                    Address         Comments

scam.Berkeley.EDU       128.32.138.1    The original site.
ftp.cis.ksu.edu         129.130.10.80   Mirrors, INL server.
pittslug.sug.org        192.58.107.150  Bronco binaries.
gs69.sp.cs.cmu.edu      128.2.206.167   Learn to play here!
b62103.student.cwru.edu 129.22.242.151  NeXT stuff.
ftp.iastate.edu         129.186.140.11  Little bit of everything.
iacrs2.unibe.ch         130.92.11.4     Source for IBM rs6k/AIX.
sgi.com                 192.48.153.1    Silicon Graphics binary.
ocf.berkeley.edu        128.32.184.252  Apollo stuff.
cad.ics.uci.edu         128.195.1.42    UDP client.
ftp.coe.montana.edu     192.31.215.240  Mirrors.
ftp.informatik.uni-rostock.de 139.30.5.23  Galaxy client.
ftp.ulowell.edu		129.63.32.1	VMS client.
ftp.unh.edu		132.177.128.99	VAX Ultrix client.
duke.me.chalmers.se	129.16.50.80	ntpatch source.
grind.isca.uiowa.edu	128.255.19.233	Grandfather borg.
charon.amdahl.com	129.212.11.1	Andy McFadden's stuff.
ftp.chemietechnik.uni-dortmund.de 129.217.174.20  Mirrors gs69.sp.cs.cmu.edu.
tbird.cc.iastate.edu	129.186.140.11	Game recorder server mod.


Note: 'Andy McFadden's Toolbox' currently contains the following items:
xsg: a tool for server gods that allows them to change owners of planets,
     ship states, and lots more.
gw: a tool to allow people to play netrek through an Internet firewall.
trekhopd: Similar to gw, but netrek-specific and more secure.
pledit: a tool to manipulate player databases.
He also developed the UDP protocol for netrek.  Donations for his shrine
are being accepted even as we speak.

Comments:

scam.Berkeley.EDU: Directory is /src/games/xtrek.  In addition
to netrek source, this site also has source for Xtrek 6 (the X11
version) and Xtrek III (the X10 version).  Netrek source and
binaries are in /src/games/xtrek/netrek.  The binaries here are blessed.
There is a binary only for Decstation 3100s.  The source will work on
cyborg nights, and this is where to go to get the code you'll need for
building your own cyborg.  The source for the scam server is here.

ftp.cis.ksu.edu: Directory is /pub/Games/netrek.  There are KSU-style
and bronco-style binaries for sun 3's and 4's.  Send your whole mail
address instead of just your login as 'Password:'.  There is also
source for the KSU 'GalaxyTrek' server, which supports the Galaxy
class ships, and source for the Galaxy client.  The latest copy
of the FAQ and this server list should be there.  Andy McFadden's
Toolbox is here.  The bronco server distribution has recently been added.
There is a blessed UDP binary for Sun 3's, 4's and HP Apollo series 700 
workstations.  The UDP server and client code is here.  There is also a 
tar file containing a font to use as an italic font (for neutral planets 
and team members).  The official INL server code and the INL rulebook 
are here.  

pittslug.sug.org: Directory is /pub/netrek.  The binaries here will work
anywhere.  There are UDP and conventional blessed binaries for Decstation
3100s, Sun 3s and 4s, NeXT's, and MIPS's.  The source for the UDP client 
and the UDP server is also here.  Andy McFadden's Toolbox is here.
XnetrekM, a Motif front end for METASERVER (by Tedd Hadley) is here.

gs69.sp.cs.cmu.edu: Directory is /usr/jch/netrek, but the server should
be smart enough to drop you there when you log in.  Send your whole mail
address instead of just your login name or else the server will rudely
close connection on you.  The collected wisdom of CMU xtrek players lies
here, along with the latest version of this server list, a sample .xtrekrc,
hints on how to play the different ship types, and lots of other useful
information for players.  There is also help here for people trying
to set up a server, and a list of common problems and their solutions.
There is a patch for turning the standard client code into an information
borg.  The final bronco server code is here in the /code directory.
The final bronco score database is here.  There's a ton of stuff here, 
really; check out ChangeLog for recent changes.  This archive is available 
over AFS (cd /afs/cs.cmu.edu/user/jch/netrek) and WAIS (gourd.srv.cs.cmu.edu,
port 6000, name netrek-ftp).

b62103.student.cwru.edu: Directory is /pub/games/netrek.  The binary
here is for NeXT computers, and specifically for NeXT's running
MouseX or Co-Xist (NOT NeXTstep).  The binary is now blessed and UDP,
so it can be used on any server.  The source will work on NeXT's or
any other color machine that has fewer than 8 color panes.
A NeXT port of 'sunborg' is also here.  The source for Dtrek, a
new, larger version of xtrek, is here.

ftp.iastate.edu: Directory is /pub/netrek.  There are versions of
Scout Popcorn's solarisborg for decstation 3100's, NeXT's and Suns,
a version of the Pig borg for decstation 3100's, and patches to set
up a server like tbird.cc.iastate.edu.  Pretty much anything that is
at any other FTP site can be found here, somewhere.

iacrs2.unibe.ch: Directory is /pub/aix/netrek.  There is source here that
contains the modifications necessary to get netrek to run on IBM
rs6k/AIX (the standard code, the galaxy code, and the BEEF information
borg code).  xsg code is here, also, as is the source for ck_players.
The source for the Scam server and client are here, as well as
source for the Aix server and client.  There are also sample
.xtrekrc's and the latest server and FTP lists.

sgi.com: Directory is now /sgi/src/netrek.  There is a binary and source 
for SGI Irix 4.0 or later here.  If you're not running 4.0, this will 
not work.

ocf.berkeley.edu: Directory is /pub/netrek.  There are blessed UDP binaries 
here for Sun 3's and 4's and HP Apollos.

cad.ics.uci.edu: Directory is /pub/netrek.  There is a binary here for
the UDP client (version 1.0) for sun 3's, 4's, and MIPS's.

ftp.coe.montana.edu: Directory is /pub/mirrors.  There are mirrors here
of gs69, pittslug, and ftp.iastate.edu.

ftp.informatik.uni-rostock.de: Directory is /pub/games/xtrek.  The source
for the KSU galaxy server is here, along with some sample xtrekrc's.

ftp.ulowell.edu: Directory is /pub/netrek.  The source for a VMS
client and VMS server are here, as well as an unblessed VMS client
binary.

ftp.unh.edu: Directory is /pub/submissions.  A blessed binary for
VAX Ultrix 4.2 is here, and a blessed VMS client (using UCX for the
TCP/IP interface).

duke.me.chalmers.se: Directory is /pub/netrek.  ntpatch, a utility
that allows one to change variables in shared memeory, is here.

grind.isca.uiowa.edu: Directory is /unix/netrek.  Has most everything
from the other archive sites.  This is also the main distribution
point for the Grandfather borg, there are binaries for Decstations,
NeXT's, and Suns (Sun 4's, I think).

charon.amdahl.com: Directory is /pub/netrek.  This is not a full-time
FTP site, but this is where Andy McFadden puts the new releases of
his netrek-related utilities until they show up elsewhere.  Currently
there is trekhopd 1.3 and xsg 1.22.

ftp.chemietechnik.uni-dortmund.de: Directory is /pub/games/netrek or
simpy netrek.  This is a mirror of gs69, and has also xsg, the grit
server source, the source for the Hadley client and the scam server/
client source.

tbird.cc.iastate.edu: Directory is /usr/isae.  The source for a server 
mod to record games of netrek is here.