Zebedee's Inetd Services


A good protocol definition and implementation are available (from Nostradamus@Zebedee), however I didn't find a good list of available services and commands. So I created this list myself, based on the implementation.

Note that the fields "NAME" and "UDP_PORT" should be present in every message. Very common are the fields "ID" (used whenever an reply is expected) and "SND" (the sender: he should receive the reply). These fields will not be mentioned in the list below.

"channel"
The channel-request is used for sending a message on any channel. The "CMD" field is optional and may be omitted for normal messages. Note that you should not send an history or list request to _all_ known muds!

"CHANNEL"
The channel on which a message is send (the standard channels are "intermud", "intercode", "interadm", "d-chat", "d-code" and "d-adm"; on the d-channels German is spoken)

"DATA"
The message to be send (not used with history/list request)

"CMD" (optional)

""
for normal intermud messages,

"emote"
if the message is an emote,

"history"
for an history request: the last 20 lines of this channel will be shown.

"list"
to list all remote users listening to this channel

"EMOTE" (optional)

1
The message is a normal emote.

2
The message is a gemote.

"finger"
Retreive information about a player or creator on a remote mud.

"DATA"
The player of whom information is requested

"locate"
Check whether a certain player is logged on at a remote mud. This request is usually send to all known muds at the same time.

"user"
Name of the person who requests the information.

"vbs"
The verbose option has only two pre-defined values:

1
Even report when the result was negative

2
Don't do timeouts, but keep waiting

"fnd"
The found option is only used in the reply and it's value is either 1 (success) or 0 (failure). The absence of a found parameter indicates failure as well.

"DATA"
The player to find.

"man"
Retreive a manual page from a remote mud. Many muds don't support this feature...

"DATA"
The name of the requested manual page

"mail"
An extension to the standard protocol, by Alvin@Sushi. This is used to send mails from one mud to another.

"udpm_status"
This field should only be used in the reply and indicates how mail is handled. Currently there are four pre-defined values for the status field:

0
time out

1
delivered ok

2
unknown player

3
in spool (will be delivered later)

"udpm_writer"
Name of the person who wrote this mail

"udpm_spool_name"
Should be returned as sent, this value is used to remove the mail from the spool directory after it has been delivered (or refused)

"udpm_subject"
Subject of the mail message

"DATA"
The body of the mail (the actual message)

"ping"
A ping request has only the standard fields, the reply is usually a short string like " is alive."

"query"
Get standard information about another mud. This is the only command of which the reply may not include a load of rubbish, but should only hold the requested information, so that it can be parsed by the server.

"DATA"
The following queries are pretty much standard:

"commands"
List all commands that are supported by the inetd

"email"
The email-address of the mud administrator(s)

"hosts"
A listing of all hosts in a special format [t.b.d.]

"inetd"
The version number of the inetd used

"list"
The list of all items which can be queried

"info"
A short human-readable string with practically "query" information

"mud_port"
The portnumber that players connect to on login

"time"
The local time for this mud

"users"
A list of the people that are active in this mud

"version"
The version of the mud-driver (and library)

"www"
The URL of the mud's web page (e.g. http://mud.stack.nl/)

"reply"
This request method is used for _all_ replies.

"DATA"
A human-readable string, containing the reply to a given query

"RCPNT"
The same name as in the "SND" field or the query; Usually this is the name of the player who initiated the query

"QUERY"
This field is only used in a response to a "query" request and should be equal to the "DATA" field of that request

"VBS"
This field is only used in a response to a "locate" request and should be equal to the "VBS" field of that request

"FND"
This field is only used in a response to a "locate" request and should be 1 if the player was located and 0 otherwise

"tell"
Say something to a player on another mud.

"RCPNT"
Name of the player to whom you are talking

"DATA"
Whatever you wish to say to this person

"who"
List the people that are active on a remote mud. The anwer usually contains some active information about the players, like titles, levels or age.

"DATA"
Not supported by many muds. Introduced August 1997.
Additional switch(es) (space separated) that change the appearence of the resulting list. The switches normally resemble the switches used inside of that mud for the 'who' command. Typical values include:
"short" "s" "-short" "-s" "kurz"
Return a concise listing.
"alpha" "a" "alphabetisch" "-alpha" "-a"
Sort the players alphabetically.

Return to the OuterSpace index
Last modified Thu Oct 7 22:28:16 2004, by Dyorion