rang@cs.wisc.edu (Anton Rang) (04/24/91)
Archive-name: games/mud/mud-client-listing/1991-04-22 Archive: jaguar.cs.wisc.edu:/pub/mud-client.listing [128.105.1.202] Original-posting-by: rang@cs.wisc.edu (Anton Rang) Original-subject: Periodic Post of Client Information Reposted-by: emv@msen.com (Edward Vielmetti, MSEN) This is a post I'll be making periodically. It includes information about where to get clients for the various MUDs. Please let me know if you have additions, changes, corrections, or suggestions. The most up-to-date copy of this file is always available for anonymous FTP from jaguar.cs.wisc.edu (128.105.1.202) as ~ftp/pub/mud-client.listing. Please note that I have not used or tested all of these. Bugs should be reported to the authors (whose names should be in the documentation somewhere). Anton Changes since the last release: Updated TINT version. [ Version 15 of 4/14/91. ] What is a client? ----------------- A "client" is a program which can be used to connect to a running MUD. Most current MUD systems can be reached using the 'telnet' program (standard on BSD UNIX, and available on many System V and VMS machines). The clients listed here can be used as replacements for telnet; they typically provide extra functions such as macros or a screen mode. What do I need to use a client? ------------------------------- You need to have a computer account; if you only have telnet access through a terminal server, you can't use a client. You must have enough disk space in your account to store the client's code; under UNIX, this is usually at least 45K for a small client, and may be as large as 200K (or more!) for larger ones. (EMACS-based clients typically require much less space, but you must have GNU EMACS available to use them.) You must also have the appropriate operating system. Many clients require BSD UNIX. Others require System V with BSD networking extensions. A few require VMS with MultiNet software. Some require that you have GNU EMACS installed on a UNIX system with networking. All non-EMACS clients that I know of are written in C. If you haven't got a C compiler, you're out of luck. Also, if you don't know EMACS, be prepared to put a lot of time into learning it before you can effectively use an EMACS-based client. How can I get a client? ----------------------- You need to use 'anonymous FTP' to retrieve the clients below. (If there's sufficient interest, I can go into more detail in this post, but it's usually easier to find someone at your site who knows how. I'm feeling too lazy to go through details right now.) What clients are available? --------------------------- Here's a listing of clients that I know of as of 1/26/91. It is certain to be incomplete and quite possibly has some inaccuracies. Please let me know of additions, changes, etc. so that I can correct it in later posts. The "features" list is especially incomplete for clients which I've never used. (It's also not exactly clear, and I'd love suggestions for a new format.) EMACS clients usually offer, even when not explicitly listed, a screen mode and logging capabilities. Numbers in brackets refer to notes at the end. The location will be the name of a computer, and the directory in which the clients' files are stored. The IP address is given in parentheses for people without name service. If there is more than one location given, you should probably try to get it from the site nearest to you. (In particular, FTP overseas is slow and expensive!) UNIX clients appear first, VMS clients last. EMACS clients for UNIX appear after those written in C. +------------+-----------+----------+-----------------------------------------+ | Name | System | Version | Location, features, and notes. | +------------+-----------+----------+-----------------------------------------+ | TinyTalk | Unix | 1.1.7 | jaguar.cs.wisc.edu:~ftp/pub/tinytalk | | | | 2/5/91 | (128.105.1.202) | | | BSD or | | | | | S5 w/net | | TinyMUD; hiliting (whispers, pages, | | | | | users); gag; auto-login; simple macros; | | | | | logging; portals. [#1] | +------------+-----------+----------+-----------------------------------------+ | TinyFugue | Unix | 1.5.2b5 | belch.berkeley.edu:~ftp/pub/mud_clients | | | | 3/8/91 | (128.32.152.202) [also on jaguar] | | | BSD or | | | | | S5 w/net | | TinyMUD; LPMUD; screen; hilite (regexp);| | | | | gag (regexp); auto-login; macros; | | | | | logging; portals; triggers; file load. | +------------+-----------+----------+-----------------------------------------+ | tcltt | BSD Unix | 0.9 | ftp.white.toronto.edu (128.100.2.160) | | | | | /pub/muds/tcltt/tcltt0.9.shar | | | | | | | | | | TinyMUD; hiliting; gag; logging; | | | | | auto-login; partial file load; | | | | | triggers; programmable (can do macros) | +------------+-----------+----------+-----------------------------------------+ | LPTalk | Unix | 1.2.1 | jaguar.cs.wisc.edu:/pub/contrib/lptalk | | | | 11/16/90 | (128.105.1.202) | | | BSD or | | | | | S5 w/net | | LP-MUD; hiliting; gag; auto-login; | | | | | simple macros; logging. | +------------+-----------+----------+-----------------------------------------+ | PMF | Unix | 1.9 | nanny.lysator.liu.se [in Sweden] | | | BSD only? | 12/28/90 | (130.236.254.13) | | | | | jaguar.cs.wisc.edu:/pub/contrib/pmf | | | | | (128.105.1.202) | | | | | | | | | | LPmud; TinyMUD; editing (GNU); | | | | | auto-login; macros; triggers; gag; | | | | | sounds; logging; file load; X-windows. | | | | | | | | | | This software has not been extensively | | | | | tested on many platforms. | +------------+-----------+----------+-----------------------------------------+ | TinyMUD.el | UNIX | | belch.berkeley.edu:~ftp/pub/mud_clients | | | GNU EMACS | | (128.32.152.202) | | | | | | | | | | ( Superseded by MUD.el, below. ) | | | | | | | | | | TinyMUD; portals; screen; ???. | +------------+-----------+----------+-----------------------------------------+ | TinyTalk.el| UNIX | 0.4 | belch.berkeley.edu:~ftp/pub/mud_clients | | | GNU EMACS | 3/5/91 | (128.32.152.202) | | | | | | | | | | TinyMUD; auto-login; macros; logging; | | | | | logging; screen; programmable. | +------------+-----------+----------+-----------------------------------------+ | MUD.el | UNIX | 2/13/91 | belch.berkeley.edu:~ftp/pub/mud_clients | | | GNU EMACS | | (128.32.152.202) | | | | | | | | | | ( Designed to replace TinyMUD.el. ) | | | | | | | | | | TinyMUD; LPMud; auto-login; macros; MOO;| | | | | logging; portals; screen; programmable. | +------------+-----------+----------+-----------------------------------------+ | LPmud.el | Unix | | nanny.lysator.liu.se [in Sweden] | | | GNU EMACS | 12/17/90 | (130.236.254.13) | | | | | jaguar.cs.wisc.edu:/pub/contrib/lpmud-el| | | | | (128.105.1.202) | | | | | | | | | | LP-MUD; macros; triggers; file load; | | | | | logging; screen; programmable. | +------------+-----------+----------+-----------------------------------------+ | MyMud.el | UNIX | 1.5 | jaguar.cs.wisc.edu:/pub/contrib/mymud-el| | | GNU EMACS | 2/18/91 | (128.105.1.202) | | | | | | | | | | LP-MUD; DikuMud; screen; auto-login; | | | | | macros; triggers; programmable. [#2] | +------------+-----------+----------+-----------------------------------------+ | TINT | VMS | 2.1b | belch.berkeley.edu:~ftp/pub/mud_clients | | | MultiNet | 4/91 | (128.32.152.202) | | | VT-100 | | | | | | | TinyMUD; hiliting (whispers, pages, | | | | | users); gag; file load; simple macros; | | | | | screen. | +------------+-----------+----------+-----------------------------------------+ | FooTalk | VMS | | lancelot.avalon.cs.cmu.edu:~ftp/pub | | | MultiNet | | (128.2.242.79) | | | | | | | | BSD UNIX | | TinyMUD; screen; programmable. | +------------+-----------+----------+-----------------------------------------+ Partial explanation of features: TinyMUD -- Supports TinyMUD servers. LPMud -- Supports LP-MUD servers. MOO -- Support MOO servers. DikuMud -- Supports DikuMud servers. Auto-login -- Automatically logs into the game for you. Hiliting -- Allows boldface or other emphasis to be applied to some text. Often allowed on particular types of output (e.g. whispers), or particular users. "Regexp" means that UNIX-style regular expressions can be used to select text to hilite. Gag -- Allows some text to be suppressed. The choice of what to suppress is often similar to hiliting (users or regular expressions). Macros -- Allows new commands to be defined. How complex a macro can be varies greatly between clients; check the documentation for details. Logging -- Allows output from the MUD to be recorded in a file. Portals -- Supports special MUD features which can automatically reconnect you to another MUD server ("cyberports"). File load -- Allows a file to be sent to the MUD. This is useful for programmable MUDs, for instance. Screen -- Supports some sort of screen mode (beyond just scrolling your output off the top of the screen) on some terminals. The exact support varies. Triggers -- Supports events which happen when certain actions on the MUD occur (e.g. waving when a player enters the room). (This can nearly always be trivially done on programmable clients, even if it isn't built in.) Programmable -- Supports some sort of client-local programming. Read the documentation. Sounds -- Supports sound on a Sparcstation. (If there is a demand for sounds, let me know; there are some available in Sweden, and I could place them on jaguar.cs.wisc.edu for FTP if anyone wants.) Editing (GNU) -- Supports command line editing if the GNU readline package is used. (Included in the PMF version 1.9 tar file.) X-windows -- Very basic support for X-windows; allows separate input and output windows. -------------------- Notes: #1 - I am interested in supporting TinyTalk on as many platforms as possible. If you have ported it onto a new system, I'd appreciate patches (or special compilation directions). #2 - MyMud.el supports two interesting features with LP-MUD servers. Multiple commands may be entered on one line, and they will be sent to the server one at a time; this works even on servers without typeahead capabilities. There is an "autonavigator" capability. This client can be taught the names and location of various places; it can then move along the shortest path to any of these. Don't ask me for details; I didn't write it. Read the documentation. +---------------------------+------------------+-------------+----------------+ | Anton Rang (grad student) | rang@cs.wisc.edu | UW--Madison | "VMS Forever!" | +---------------------------+------------------+-------------+----------------+ -- comp.archives file verification jaguar.cs.wisc.edu -rw-r--r-- 1 2032 50 11808 Mar 5 12:46 /pub/mud-client.listing found mud-client-listing ok jaguar.cs.wisc.edu:/pub/mud-client.listing