COMMAND | PARAMETER | VERSION |
/ADMIN login | password pwd | 0.91 |
Become chat administrator. You have to to this, before you can use any
of the other admin commands. The password pwd is the password you specifed
in the melange.conf file.
|
/ADMIN help | none | 1.10 |
Displays a list showing all administrator commands available.
|
/ADMIN whois | none | 1.10 |
Like the standard /WHOIS command, but the /ADMIN WHOIS command lists all users
in the chat even those who are connecting (These are people which are already
connected to the chat-server but have to chose a unique nicknames via the /LOGIN
command before they could start to chat) (C-FLAG). This command also
displays some additional info about the user: If they are channel owner (O-FLAG),
if they are administrator (A-FLAG), to which group they belong, in which
channel they are and their IDLE-time.
|
/ADMIN list | none | 1.10 |
Like the /LIST command, but it shows ALL channels, including the channels
which belong to ANOTHER GROUP. (The default /LIST command only shows
public channels and the channels which belong to the same group the user
is in.)
|
/ADMIN join | ChannelID cid | 0.92 |
Join an existing channel, even if the channel you want to go to, is locked
or belongs to another group.
|
/ADMIN own | UserId uid | 0.92 |
Change the owner of the channel you are currently in.
If you type SYSTEM instead of the UserID,
the channel is owned by the chatserver itself (like the channels MAIN (0) and
ANONYM (1)), that means, this channel can not be deleted by normal chat users.
Simliar you change make a SYSTEM-channel a normal user-channel by setting the owner
to a UserID.
|
/ADMIN topic | Channelname name | 0.92 |
Change the name of the channel you are currently in, even if you
are not the channel's owner. It does also work with SYSTEM-Channels.
|
/ADMIN close | ChannelId cid | 1.10 |
Close the channel given via cid, even if you are not the owner or the
channel is locked or a system-channel.
|
/ADMIN syschannel | ChannelName cname | 1.10 |
You can use this command to create a new system-channel with the name given with
the cname parameter.
|
/ADMIN kick | UserID uid | 0.91 |
Kick the user with the UserID uid out of the chat. After a user has been
kicked out, he is not able to connect immediatly. By setting the KICKOUTTIME parameter
in the configuration file, you can change the time, he has to wait before
he is allowed to come in again.
|
/ADMIN kickouttime | BannTime t | 0.94 |
Using this command, you can change the default value of the KICKOUTTIME parameter
in the configuration file, whithout the need of restarting
the server. This paramter sets the time, a user is not allowed to connect to the
server after he has been kicked out by the administrator. t is the time in seconds.
|
/ADMIN idletime | IdleTime t | 1.10 |
Using this command, you can change the default value of the IDLETIME parameter
in the configuration file, whithout the need of restarting
the server. This paramter sets the time after a user is kicked out of the chat if he doesn't
say a word for IdleTime seconds. If the time is set to 0 users will
not be kicked out even if they don't say a word for days. NOTE: Users are not kicked exactly at
the time you set via IdleTime but when the first new user after IdleTime is over
connects to the chat. (This is to speed up the server). The admin user will NEVER be kicked out
of the chat-system.
|
/ADMIN loglevel | Loglevel level | 0.99a |
Use this command to change the current loglevel without restarting the server.
It is the same as the Loglevel parameter in the configuration file.
Currently loglevel 0 to 4 are supported (0 ... no logfile output, 4 ... debugging mode)
|
/ADMIN sysmsg | Sysmsg on/off | 1.01 |
Use this command to enable/disable the "system messages" feature while the server is
running. On enables this messages, off disables the messages. This feature is used
and needed by the "real-time" clients. If you use such clients, make sure you enable
this parameter. It is the same as the Sysmsg parameter in the configuration file.
|
/ADMIN unique | UniqueNicks yes/no | 1.10 |
Use this command to enable/disable unqiue nicknames. If this parameter is enabled,
users who connect to the server have to choose a nickname which is not in use already,
before they can connect to the chat-channels via the /LOGIN command.
It is the same as the UNIQUE parameter in the configuration file.
|
/ADMIN changenicks | ChangeNicks yes/no | 1.10 |
Use this command to allow/disallow users to change their nicknames once they are
connected. If you don't want to allow your guest to change their names set this parameter
to no. It is the same as the CHANGENICKS parameter in the configuration file.
|
/ADMIN guestlogin | GuestLogin yes/no | 1.10 |
If the UNIQUE nickname paramter is enabled every users has to have a unique
nickname. If the UNIQUE paramter is enabled you can use this parameter to enabled
a guest-login. If users don't know a unique nickname they can use the nickname guest.
There can be more the one user with this nickname !
It is the same as the GUESTLOGIN parameter in the configuration file.
|
/ADMIN group | [Group groupnum] | 1.10 |
If this command is called without the OPTIONAL groupnum parameter
it lists all groups available and the associated passwords. If the command is
used with the groupnum parameter it lists all users of this group
who are connected in the moment, no matter in which channel.
|
/GRPADMIN | param1, param2 | 1.10 |
Used to administrate the groups. (NOTE: The command is called /GRPADMIN - not
/ADMIN grpadmin although you need to be administrator to use this command !)
There are three ways for using this command:
It is the same as the GROUP parameter in the configuration file.
|
/ADMIN stat | none | 0.99a |
Displays the status and the current parameter settings of the server. It shows the loglevel,
the name of the logfile, the port it is running on, the host table etc.
Depending on the default security profile you selected in the melange configuration file,
the host table stores the currently banned hosts, or the currently "trusted" hosts (these are
the hosts, which are allowed to connect). If the default security profile is allow (this is also the default setting), it is also displayed if
the hosts are permanently banned, or if they are banned after a user has been kicked out.
In the first case, the string (permanently banned) is displayed in addition.
Replaces the /ADMIN security command used in previous version.
|
/ADMIN deny (same as allow,add) | Hostmask mask | 0.94 |
If the default security profile is allow, everybody is allowed to connect to the server.
You can bann hosts, by defining a DENY mask in the configuration file.
With this command, you can also add hosts to the host table while the server is running,
without the need of restarting it. You do this by specifying a hostmask, which has the same
form as in the configfile. If you don't know what it looks like, take a look here.
|
/ADMIN allow (same as deny,add) | Hostmask mask | 0.94 |
If the default security profile is deny, you can add additional "trusted" hosts to
the host table, without restarting the server. Trusted hosts are the hosts which are allowed to connect to Melange.
You specify the hosts using the same hostmask as used in the configuration file. If
you don't know what it looks like, take a look here.
|
/ADMIN add (same as allow, deny) | Hostmask mask | 0.99a |
This command is the same as /ADMIN allow and /ADMIN deny. All these commands add
a hostmask to the host table. The reason for the existence of allow, deny and add
is to use the same command names used in the configfile and to make it easier to
remember the right syntax. Internal all of them are handled equal.
|
/ADMIN remove | Hostmask mask | 0.94 |
Using this command, you can remove a hostmask from the host table of currently banned or trusted hosts,
without restarting the server.
|
/ADMIN shutdown | Password pwd | 0.99a |
Shuts down the chat server in a controlled way, eg. all client connections are closed
before shutdown. To avoid unwanted shutdowns you have to give the administrator
password as a parameter, eg. /ADMIN shutdown mypassword
|