MOO Client Protocol 2.1 Support (and other plugins)
MOOsaico supports the following packages
dns-org-mud-moo-simpleedit dns-com-awns-status dns-com-vmoo-client dns-com-awns-serverinfo dns-com-vmoo-pages dns-com-awns-ping dns-com-vmoo-userlist dns-com-awns-displayurl dns-com-vmoo-mmedia * dns-com-awns-visual dns-com-zuggsoft-msp * dns-org-cubik-prompt * under testUse the
@mcpcommand to check the availability of these. The folder
*clientsin MOOsaico is the place of discussion for issues about MOO clients and MCP/2.1.
Check the rest of the page for some packages for your client of choice. The following clients support MCP/2.1 and some of the listed packages above: TinyFugue, tkMOO-light, tkMOO-SE, GnoeMoe, Trebuchet Tk, gMOO, VMOO, zMUD and KoeMoe, Atlantis, MudWalker, Savitar .
You can check their appearance with these screenshots.
TinyFugueWindows, Macintosh, Linux
No. The package is not here. It is better to get it from the original place: https://tinyfugue.sourceforge.net/
MCP pluginshttps://ben.com/MOO/tf-mcp.html. Unpack it in your
tf-lib. With these macros you will get MCP (MOO Client Protocol) support from tf so you can interact with some moo packages. One of the most important one is local editing (edit text in a separate window). Make sure your
-Ttiny.mooon your MOO worlds.
Local MCP/2.1 packages for TinyFugue:
- Implements some client info to be known within the MOO. Name, version and client window size are some of them. Nice for better tables and horizontal text.
- The package allows the server to send short, human readable, informational messages to cooperating clients. The client will display it on a status bar. This implementation uses the window title.
- The package allows the server to send URLs to the client. The client should then use a client-side webbrowser to display the contents of the URL. You have to edit it and write your browser name.
- Allows both client and server to test the latency of a user's
connection, a rough indication of net-lag. An indicator shows up
on the right side of the worlds name on the visual bar.
Of course you need
/visual on. This is just the client test for now.
If you need some help check this small HOW-TO.
The packages here have been signed by the wizards.
You can get the public key from any keyserver with the key id 0x24B51361, or directly from here:
The public key fingerprint should be:
pub 1024D/24B51361 2005-03-16 MOOsaico (https://no.moosaico.merg.ulh.as/) <firstname.lastname@example.org> Key fingerprint = DF47 12EF 7125 57B0 15BB C1C6 72C7 CD75 24B5 1361For more information about public key signatures, see https://www.gnupg.org/
You must get one of the following two if you type with accents:
- If a LambdaMOO server has a database that supports sending
binary chars to the player, this way everyone can type
accented characters and make them appear to the others.
Now you can send pages and messages in MOOsaico with your
Do not forget to set
If you really want to see the ~XX codes for debugging get this.
- Just type the accented characters you are used to, and automagically they are converted to a 7 bit codification. It is working with Euro € :)
tkMOO-lightWindows, Macintosh, Linux
Put these extentions in
- Type accented characters! This plugin let's you use your usual
international keyboard and fonts with MOOsaico.
You can turn it off under the
Do not forget to set
Contribution by pmsac.
- The tool you're waiting for! Keep on top of the wave! This autoupdater will
check automatically if there are new or updated plugins and will get them
for you. You've just have to restart your client. Are you a Windows
user ? The client binary for windows doesn't have HTTP support so you
need to also copy this
http.tclto your plugins directory.
- Show to the moo system what client you are using so it gets better
support. It also update your
@linelenif you resize your window.
If you want to use emacs as a client download this client.