How to Access TigerMUCK
TigerMUCK is accessable by telnet or a dedicated 'muck client' program to tigermuck.tigerden.com 8888,
If you have a client program which can connect using SSL (Secure Socket Layer) protocol, you can connect using encrypted communication to port tigermuck.tigerden.com 8889.
You can also connect using the site IP address/port which is currently 126.96.36.199 8888 or 8889. NOTE: Use of the host name rather than IP number is recommended especially if you are embedding the site into a script, since the number may change, but the name won't.
The 8888 or 8889 is the port number and is essential to reach TigerMUCK. You *should* get 'Welcome to' followed by TigerMUCK's ASCII art logo (the one you saw on the first TigerMUCK info page) and instructional text.
If you get something like:
You will not get a 'login' prompt following the sign-on banner screen. Once the screen has displayed, you need only enter the single line:
Although 'raw telnet' will work, use of a 'client' program is highly recommended. TinyFugue is the best known of the clients for unix systems, and works very well. Tinyfugue is available from tinyfugue.sourceforge.com . Some knowledge of UNIX will be needed to install TinyFugue on your system. Information on other clients for unix as well as other operating systems can be found at http://www.mudconnect.com/mudfaq/mudfaq-p2.html in the MUD FAQ.
If you don't have a client, you may be able to set your terminal program to a 'chat mode' where incoming and outgoing text is displayed in seperate windows on your screen. Otherwise, text you send will echo and appear mixed with any incoming text that arrives while you are typing. Although what you send will be interpreted properly, the resulting garbage on your screen makes it difficult to see and correct what you type.
Lines sent to you are not always formatted to fit 80 column screens, so you will have to turn word-wrap on on your terminal if lines run off the right side of the screen.
If the sign-on logo looks like garbage on your screen, your terminal program is not properly interpreting the 'newline' character sent by our unix server. You can still connect, and things should be ok after that.