Mccp (Technical Help)

The Two Towers supports the Mud Client Compression Protocol (MCCP).

Specifically, MCCP is used to compress the output text stream sent by a MUD to a MUD client using zlib, in order to reduce bandwidth usage, resulting in a faster connection.

The following clients are known to work with MCCP:

• Kmuddy, a KDE3 based mud client for Linux, versions >= 0.5 [MCCP1+2]
• mcl, Linux client, versions >= 0.42.05 [MCCP1] or >= 0.52.98 [MCCP1+2]
• MUSHclient, windows-based, versions >= 2.14 [MCCP1], or >= 3.05 [MCCP1+2]
• Papaya, GTK-based for Linux/Solaris/Windows, as of version 0.60 [MCCP1+2]
• RoAClient, as of version 4.4. [MCCP2]
• SimpleMU, as of version 4.0. [MCCP1+2]
• TinTin++, as of version 1.90. [MCCP2]
• KBTin, an extended clone of TinTin++, as of version 1.0.9 [MCCP1+2]
• zMUD, versions >= 6.03beta. [MCCP1+2]
• KildClient, a GTK mud client for Linux/Windows [MCCP1+2]
• Wintin.Net, a .NET mud client for Windows, as of version 1.07. [MCCP1+2]
• cMUD, all versions [MCCP1+2]
• TinyFugue, a Mac/Unix/Windows client, versions >= 5.0b5 [MCCP1+2]

For clients that do not support MCCP natively, like GMUD and raw telnet, you can still use the feature by downloading the mcclient:

Windows users:

1. Obtain the Windows binary from http://t2tmud.org/tools/mcclient.zip
2. Unzip into a directory (eg c:\program files\MCCP)
3. Double click mcclient.exe in that directory
4. Connect your mud client to host "localhost" ip "127.0.0.1" port "9999"

Linux users:

1. Download the MCCP source from http://t2tmud.org/tools/mcclient-0.4.zip
2. Uncompress the contents and compile
3. Run the client
4. Connect your mud client to host "localhost" ip "127.0.0.1" port "9999"

You can check your compression status by typing the "conninfo" command and seeing if you are being sent compressed bytes.