#HELPS

0 I3~
Syntax: i3 <option>

Note: You must meet the mud's minimum level requirement before accessing I3.
You will be notified when you have reached the approptiate level.

General Usage:
------------------------------------------------

List channels available                : i3chanlist [all] [filter]
To tune into a channel                 : i3listen <localchannel>
To see who is listening on another mud : i3chanwho <channel> <mud>
List muds connected to I3              : i3mudlist [filter]
Information on antoher mud             : i3mudinfo <mud>
Ignore someone who annoys you          : i3ignore <string>
Make yourself invisible to I3          : i3invis

i3chanlist: Lists the channels the mud has available to listen to.
  Specifying 'all' will list the channels for the entire network.

i3listen  : Tunes you in to the specified channel. You must meet or
  exceed whatever the minimum level is for that channel to do so,
  and your mud must have the channel configured locally.

i3chanwho : Shows you who is listening to the specified channel on the
  specified mud. Invisble players will not be shown.

i3mudlist : Lists the muds which are connected to the network.
  Specifying a filter will narrow the list down to only those muds
  whose information matches. IE: &Wi3 mudlist afk&D will list all
  muds who have &Wafk&D as part of their listing.

i3mudinfo : Lists the information provided by the specified mud.

i3ignore  : Allows you to selectively ignore all contact with person@mud.
  This will block tells, beeps, locates, fingers, emotes, and whos. It will also
  block channel output from them, but will NOT block them from seeing YOU on
  a channel.

i3invis   : Makes you invisible to I3. Performs similar to the ignore option
  except it prevents EVERYONE on the network from finding you. You will still
  be able to use channels, and you will NOT be invisible to others if you
  do so.

See these general commands: I3TELL, I3FINGER, I3EMOTE, I3LOCATE, I3WHO, I3IGNORE

See these administrative commands: I3UCACHE, I3USER, I3BLOCK,
I3SETUP, I3CHANEDIT, I3CHANLAYOUT, I3ADDCHAN, I3REMOVECHAN, I3CHANADMIN,
I3CONNECT, I3DISCONNECT, I3PACKETDEBUG, I3CONFIG
~

103 I3UCACHE~
Syntax: i3ucache

Displays the current content of the mud's ucache data. This is a very spammy list
since multiple muds support this information and send packets out regularly.
Ucache data is used for gender targetting of socials.

See also: I3, INTERMUD3
~

103 I3USER~
Syntax: i3user@mud

Sends out a specific request for the target user's ucache data and updates the
data tables accordingly.

See also: I3, INTERMUD3
~

103 I3PERMS~
Syntax: i3perms <user>

Displays the permission level for the target user on the mud.

See also: I3, INTERMUD3
~

113 I3PERMSET~
Syntax: i3permset <user> <permission>

This command sets the permission level for a particular user on your mud.
The following permissions are available:

Notset - Default value. Causes subsequent logins to reset perms based on level.
None   - No access.
Mort   - Allows access to channels and commands for non-staff players.
Imm    - Allows access to additional channels and commands for regular staff.
Admin  - Allows access to additional channels and commands for administrative staff.
Imp    - Allows access to additional channels and commands for implementors.

These permission values are also used when setting channels up for access.

See also: I3, INTERMUD3
~

113 I3SETCHAN~
Syntax: i3setchan <i3channelname> <localname> [permission]

This creates a local copy of an existing I3 channel for the mud to subscribe to.
You must use the I3 name of the channel so that your mud will know which one you
want. This is obtained from the 'i3chanlist all' command. You must then supply
a local channel name to use with it. Then you can optionally set a permission level
at which players can start using the channel. Channels with no permission level
supplied will default to "Mort".

An example:

i3setchan diku_chat dchat mort

Available permissions are: None, Mort, Imm, Admin, and Imp. See I3PERMSET for more
information on what permissions do.

See also: I3, INTERMUD3
~

113 I3EDITCHAN~
Syntax: i3editchan <localname> localname <new localname>
Syntax: i3editchan <localname> level <permission>

This allows you to change the local name of a channel, or to change the permission
level at which players can begin using it.

Available permissions are: None, Mort, Imm, Admin, and Imp. See I3PERMSET for more
information on what permissions do.

See also: I3, INTERMUD3
~

113 I3CHANLAYOUT~
Syntax: i3chanlayout <localchannel> <layout> <format...>
Layout can be one of these: layout_e layout_m

Format can be any way you want it to look, provided you have the proper number of %s tags in it.

layout_e designs require 2 %s tags, one for the channel localname, and one for the message itself.

layout_m designs require 4 %s tags. One for the channel localname, one for the username, one for
the mudname, and one for the message itself.

Formats with incorrect amounts of tags will be rejected.

See also: I3, INTERMUD3
~

113 I3ADDCHAN~
Syntax: i3addchan <channelname> <localname> <type>

The channelname should be what shows up on the router's list and is displayed
on the 'i3chanlist all' command.

Localname should be the local name you want it listed as on the mud.

Type can be one of the following:

0: selectively banned
1: selectively admitted
2: filtered - valid for selectively admitted ONLY

Selectively banned channels are public channels, open to all.
Selectively admitted channels are private channels, by invite only.

Filtering is not yet implemented in this client code, but is used to scrub
the content of a private channel by its host before it is sent out to those who are
subscribed. As noted, this CANNOT be done on a public channel ( yet ).

New channels default to "Mort" permission.

See I3PERMSET for more information on what permissions do.

See also: I3, INTERMUD3
~

113 I3REMOVECHAN~
Syntax: i3removechan <channel>

Channelname should be the name seen on 'i3chanlist all'

Removed the indicated channel from the router, and deletes the local copy from the
mud as well. This does NOT send a broadcast to subscribed muds to delete their local
copies, so they will need to do that themselves upon noticing the channel is gone.

See also: I3, INTERMUD3
~

113 I3ADMINCHAN~
Syntax: i3adminchan <localchannel> <add|remove> <mudname>

This command is used to administer the list of muds authorized to use a channel.

When used with a public channel, "add" bans them from using it, and "remove" unbans them.
When used with a private channel, "add" allows them to use it, and "remove" disallows them.

This is all handled on a per mud basis.

See also: I3, INTERMUD3
~

103 I3CONNECT I3DISCONNECT~
Syntax: i3connect
Syntax: i3disconnect

Pretty self explainitory. Each option does exactly what it implies.

See also: I3, INTERMUD3
~

113 I3DEBUG~
Syntax: i3debug

When this option is on, all packets entering and leaving the mud are logged so
that they can be inspected later. This is really only of any value in the
deployment of new packet types that have not been tested, or in the addition of
new features that have yet to be implemented. It is not to be used lightly, for
it spams and is a gross invasion of privacy for anyone on the mud who may be
using tells. Responsible admins should either inform their users ahead of time or
use this option on a development port.

See also: I3, INTERMUD3
~

113 I3CONFIG~
Syntax: i3config <options>

The interface to changing your configuration while in the mud.
Most options listed by typing in the command cannot be changed if you are currently
connected to I3 and they will inform you of this.

'i3config show' will list the details of what you can currently change with this
command. If something is not listed, then the only means to change it is to edit it
in shell. The output of the command should be fairly self explainitory.

See also: I3, INTERMUD3
~

113 I3BLOCK~
Syntax: i3block <target>
Syntax: i3block IP:Port

This is the mud-wide version of an I3IGNORE command. Best used in elevated cases
where indivudual users have been unable to effectively block traffic from another
user or mud who is harassing them, or harassing multiple users on your mud.
This is a somewhat drastic measure and all traffic from the individual user or
mud will be dropped silently. It is usually best to have documented cases of
individual abuse before proceeding to this level. If blocking at this level fails
to stop the problem, you may wish to proceed to the administrator of the channel
if the problem is channel related, or directly to the router administration for
the router you are connected to if it's something else. Be prepared to provide
any necessary documentation of incidents if the administrator you contact should
request them.

See also: I3, INTERMUD3
~

0 I3IGNORE~
Syntax: i3ignore <target>
Syntax: i3ignore IP:Port

The I3IGNORE command blocks incoming traffic directed at a specific user on the mud.
It also prevents them from being displayed on such lists as who, and channel who.
This is your first line of defense against an annoying pest.
You can specify ignores either specifically or with wildcards, like so:

i3ignore pest@mud
i3ignore *@mud
i3ignore pest@*
i3ignore IP:Port

The IP type of ignore can only be specified as an IP and port, taken from the mud's
current mudinfo data. This will block anyone current and future who logs into that
mud IP and port from ever sending you traffic.

Before going to the mud's administration with a complain, you should attempt to make
an ignore work for you. If the particular person is still causing problems or is
making a nuisance of themselves to several people, advise your mud administration
that they may need to pursue an I3BLOCK against the person or mud in question.
Be prepared to show proper documentation of any incidents to support your case.

See also: I3, INTERMUD3
~

0 I3BEEP~
Syntax: i3beep <person@mud>
Syntax: i3beep [on]/[off]

i3beep sends a quick message to a person on another mud.
If the target mud supports the beep tone, then the person
on that mud will hear the standard beep tone used by whatever
client software they are using. Works in the same manner as
the local beep command.

Using on or off as an argument will enable or disable your ability
to send and receive i3beeps.

See also: I3, INTERMUD3
~

0 I3EMOTE~
Syntax: i3emote <person@mud> <message>

Sends a private emote to a person on another mud.

See also: I3, INTERMUD3
~

0 I3FINGER~
Syntax: i3finger <person@mud>
Syntax: i3finger privacy

Request for information regarding a player on another mud.
Operates in a similar manner to the local 'finger' command.
Will only reveal information the target mud feels is appropriate.

Using the privacy argument will disable your information from being
sent to a requesting user on another mud. You will not be told anyone
has tried.

See also: I3, INTERMUD3
~

0 I3LOCATE~
Syntax: i3locate <name>

Asks all the muds on the Intermud-3 network if a person
known by the name is there. Be patient when using this command,
there are a lot of muds on the network to search through, so
a response may take some time to come back.

See also: I3, INTERMUD3
~

0 I3TELL I3REPLY~
Syntax: i3tell <person@mud> <message>
Syntax: i3tell [on]/[off]
Syntax: i3reply <message>

i3tell sends a private message to a person on another mud.
To send a tell to someone on a mud with a multi-word name, you need to
enlcose person@mud in quotes, like so: i3tell 'person@mud with long name'
Otherwise this command operates in much the same way as the local tell command.

To reply to the last i3tell you received, simply type 'i3reply'
followed by your message and it will be sent back to the last
person on I3 who sent a tell to you. Works in the same manner
as the local reply command.

Using the on or off arguments will enable or disable your ability to send
and receive i3tells.

See also: I3, INTERMUD3
~

0 I3WHO~
Syntax: i3who <mud>

Requests an overview of players on a different mud.
Operates similarly to the local who command.

See also: I3, INTERMUD3
~

0 INTERMUD3~
Intermud-3 is a protocol which allows you to chat with people on
other muds who are also connected to Intermud-3. It is primarily
populated by LP based muds at this time, but the hope is to get
more Diku based muds to join over time. While some may say that
Diku based muds would be better served on the IMC Network, it
is far easier for a mud to obtain a connection to the Intermud-3
network, and the commands to use it are generally simpler.
In either case, should a mud desire it, Intermud-3 will coexist
peacefully with an IMC enabled mud.

See also: I3
~

0 $~


#$