Feed

This is just a log or a feed if you like. ;-)
You can see all changes made in the GUI here, such as port, topic changes. kicks and so forth.

Settings

Hub Control

Redirects

Redirects
Just put the address you want the users should be redirected to. If you want multiple addresses, separate with a pipe " | "
( ex: on.hub.full1:411 | on.hub.full2:411 | on.hub.full3:411 )
But you can type what ever you want in the box.
( ex. on reg only: sorry this is a reg only hub go to  www.abc.com )
If you don't want them to be redirected to another hub that is.

Notifications

Protocol notifications (before kick)

Notify invalid key (if kicking) - Notification on sending invalid key, which is sent by the client when logging into the hub.
Notify invalid MyINFO - Notification on sending an invalid MyINFO. (contains share size, description etc)
Notify invalid private message - Notification on sending a fake or malformed private message.
Notify invalid mainchat message - Notification on sending a invalid mainchat message.
Notify invalid search result - Notification on sending an invalid search.
Notify invalid passive connection attempt - Notification on sending a incorrect nickname when    connecting in passive mode to another user.
Notify incorrect characters in nick - Notification on forbidden character in nickname.

Spam notifications
Notify on MyINFO spam - Notification on sending too many MyINFO´s in to short time.
Notify on search spam - Notification on sending too many searches in to short time.
Notify on mainchat spam - Notification on sending too many mainchat messages in to short time.
Notify on private message spam - Notification on sending to many private messages in to short time.
Notify on nicklist spam - Notification on requesting the nicklist too many times in too short time .
Notify on junk data spam - Notification on data spam.

Other Notifications
Suppress client kick message in mainchat - Stops the kick messages to be posted in mainchat.
Notify operators on kick in mainchat - This will send a notification if a user is kicked to all OP´s.
Notify operators on ban in mainchat - This will send a notification if a user is banned to all OP´s.

When you choose something here, it will be sent to the feed, the chat-room you have chosen.
You change where the feed is to be sent in Miscellaneous

Feed
Use the feed command if supported - If you want to use the feed command or not.
The feed sends info on Errors in the hub, Kicks, changes in the GUI etc.
Save feed to disk - Saves the feed to a text-file.
Feed name when sent to a chat-room - Put here whatever you want the feed name should be .

Miscellaneous
Notify incorrect pass after x times - Report if a users sends wrong password in X times

To the top

Text Commands

Text commands
Enable - Enable/disable the text command. As it says an On/Off function.

Minimum - The minimum required level to access the text command. ( 0 = Disable )
If you set yourself to level 5 then you set the min level here to 3, then the users with level 2 wont be able to get the usercommands even if they write the correct command.
On level 0 everyone can access it.

Maximum - The maximum required level to access the text command. ( 9 = Disable )
If you have level 7 and you have set max level to 7, then wont the other profiles with level 8 get these commands. If you set it to 9 everyone can access is.

Edit level - The required level to edit the text commands.( 10=Only editable via the GUI )
If you set this to example 5, everyone with a level 5 and higher will have the right to edit the text command in the hub via the hub commands. (!settextcommand <name> <content>) If you set it to 10 then only the one that have the hub soft will be able to change the commands using the GUI interface.

Schedule - Timed interval in which to send this text command.
Highlight scheduledInformation in Text commands.
Set Broadcast to :everyone, message type :force to MC Parameters : No Autorun : None and set the timer to what ever you want. in my case i have set it to 240.
Then type this in the content box.
- <>===========H=U=B==I=N=F=O===========
Total Users: <users>
Current Share: <share>
Current Topic: <hubtopic>
Current Time: <time>
Current Date: <date>
Hub Uptime: <uptime>
Address: <hubaddress>
> - <>=====================================
Then hit the save button, and you are all done with the timed message. Get it here.
But don´t forget to press "enter" one time before you paste it in, or else it will look ugly in mainchat.

Broadcast to
The one writing - Sends the text command to the one writing.
Only the user which has writing the command will receive it.

Operators - Send the text command to the operators only.
Only the operators will get the commands, even if a user knows howe to type it.

Everyone - Send the text command to everyone.
Everyone in the hub will receive this command, an example of such a command is
* me <parm1>| which is shown further down. (+me <text>)

Feed - Send the text command to the feed only. It will only be sent to the feed, which would be one of the chat-rooms, if you have chosen a room to receive the feed.

Parameters
number of parameters you want to use in the text command.
example of an parameter is written further down.

Command visibility
Decides who should see the commands written in mainchat in the hub.
Nobody - None will see the command
The one writing - Only the one writing will be abel to see the command .
Operators - Only operators will be abel to see who is writing the command.
Operators and self - Operators and the users which is writing the command will be abel to see it .
Everyone - Everyone will be abel to see the command that is written in mainchat.

To the top

Message type
How to send the contexts of the text command. ( Regular, Force to PM, Force to mainchat, raw command & Randomized)
Regular: If it´s sent in mainchat it will be received in MC, If it´s sent in PM to the bot you will receive it from the bot in a PM.
Force to PM: It will be received in a PM even if it´s written in mainchatt.
Force to MC: It will be received in mainchatt even if it´s written in a PM.
Raw command: You use this when you want to send the $usercommands for an example.
Randomized: Allows you to randomize a trigger. Just separate the words with a pipe. "|"
(ex. Hello|Hi!|Hello World )

Autorun
Automatically runs the text command. ( On Connect or On login )
On Connect: The user will get the command as soon they have joined the hub.
On login: The user will get the command after he/she has sent his/hers password

Name
Name of the text command, it is also used to trigger the command. ( ex. +name )

Content
The content of the text command goes in here.

To the top

Right click in the content box to insert advanced data
Advanced data you can insert are:
Userinfo - <nick>, <ip>, <dns>
General info - <botname>, <hubname>, <hubaddress>, <hubdescription>, <hubtopic>
Stats - <time>, <date>, <users>, <share>, <uptime>
Customized Broadcast - You need to highlight the text to do this if you right click that is. <[self]> </[self]>, <[ops]> </[ops]>, <[all]></[all]>, <[feed]></[feed]>

<[self]> </[self]>: Will send the content to the one writing the command.
Look in the report command and you will know what i mean.
<[ops]> </[ops]>: The ops will receive what ever has been written between the flags.
<[all]></[all]>: Every one in the hub will se what is written between the flags.
<[feed]></[feed]>: It will be sent to the feed, what ever has been written between the flags

Text command examples

Me command
* nick <parm1> | ( set Broadcast to: everyone, Message type: to raw, Parameters to: 1 ) don't forget to end with a pipe " | ".

Report
In the content box - Report from <nick>: <parm1><[self]>Report sent</[self]>
Broadcast to: Feed, Message type: Regular, Parameters: 1, Autorun: None
The <[self]><[/self]> command will give the user a PM with " Report sent "

Todi have made a usercommand generator here, It´s an easy way to make some commands. http://todi.kicks-ass.net/YnHub/generator.php

Security

General security
Kick user if key is invalid - Testing that correct key is generated. Eliminates the crappiest clients.
Check sender IP on Search and connectToMe - Make sure users can´t supply an incorrect IP, prevents exploiting of the DC protocol. Highly recommended.
Perform DNS lookup - Checking so the user has a correct DNS address if chosen in accounts - IP Pattern
Check data before lock - According to the DC protocol the client shouldn´t send data before lock. so this is an effective way of not processing incorrect connections.

Maintenance & Timeouts
Handshake timouts - The maximum amount connecting user may negotiate. This option is crucial to help rid the server from invalid connections attempts, stalls and attacks. Strongly recommended
Drop non responding - Dropping non responding socket will help ensure that the hub den´t collect ghosts.
Temporary ban on kick - The amount of time you want the user to be tempbaned from the hub after a kick. I believe 10min is good enough. The old 5 min goes to fast.

Share trace
Enable share trace - Enables the share trace feature.
Notify on share update - Notification when the user has updated his/hers share
and is allowed into the hub again.
This feature is very good to use if you run a hub that only allows certain files.
(Ex: !kick <nick> !remove abc.bin from you share please) the" ! " is the trigger and the hub wont let the user into the hub until he/she has updated the share.
The best way is to use DCDM´s ADL search for this.
An example of a a RAW command you can use in DCDM.

$To: %[nick] From: %[mynick] $<%[mynick]> You are being kicked because: Please Remove -   %[cheatingdescription]|<%[mynick]> is kicking %[nick] because: - %[cheatingdescription]|<%[mynick]> !kick %[nick] ! REMOVE - %[cheatingdescription]|

Autoprune - Automatically clears out old share traces after "X" amount of time.


Auto bans
Ban on kick no - Automatically kicks the user after "X " kicks and timebanes the user "X" hours.
Ban on incorrect pass no - Automatically kicks the user after "X" incorrect passwords
and timebanes the user "X" hours

Spam control
New MyINFOs - The amount of MyINFOs that is allowed to be sent to the hub in "X" seconds.
Searching - The amount of allowed searches in the hub in "X" seconds.
Mainchat - The amount of allowed mainchat messages in the hub in "X" seconds.
Private messages - The amount of allowed private messages in "X" seconds.
Nicklist - Amount of nicklist requested.
Junk data - Spam warning on unrecognised protocol messages or protocol messages sent out of scoop.
Junk data directkick - kick on unrecognised protocol messages or protocol messages sent out of scoop.
Max spam warnings - Max spam warning that is sent before kick ( 0 = Off )

(A grayed check will render spam control enabled but without issuing spam warnings Just filters.) ( Click twice to get grayed box)

Restrictions

Length restrictions
Nick min length - Minimum chars a nick can contain.
Nick max length - Maximum amount of characters a nick can contain.
Search max length - Maximum amount of characters a search can contain.
MyINFO max length - Maximum amount of characters a MyINFO can contain.
Mainchat length - Maximum length of a mainchat message.
Private message max length - Maximum length of a private message.

Passive search restrictions
Max search replies - Maximum amount of search replies that will be received in passive mode.
Here you can save some bandwidth if you set it low, and in the same time force your users to
change to active mode. Just make sure they know about it if you set it low.
Some user may not have a clue how to change into active mode.
Max length any file type - Minimum length of a search when file type is unspecified.
Min length specific file type - Maximum length of a search when a file type is specified
( Audio, Video etc.)

MyINFO distribution
Pool MyINFO changes for - This will delay any changes of a MyINFO (waiting on further changes).
(if the box is grayed the operators will receive the MyINFO instantly.)( Click twice to get grayed box)

Disable description - When enabled the hub dosn´t distribute the description part of the MyINFO.
( If grayed the operators will still see all description. ) ( Click twice to get grayed box)

Disable description tag - When enabled the hub dosn´t distribute the description tag of the MyINFO.
( If grayed the operators will still see all description tags. ) ( Click twice to get grayed box)

Disable email - When enabled the hub dosn´t distribute the email part of the MyINFO.
( If grayed the operators will still see all emails. ) ( Click twice to get grayed box)

Disable connection speed information - When enabled the hub dosn´t distribute the connection speed in the MyINFO.
( If grayed the operators will still see all connection speeds. ) ( Click twice to get grayed box)

Allowed nick characters
Here you select what chars you will let your users to have in their nicks.
so just mark the box on which characters you will allow in the hub.

Banlist

Bans
Here you can add or edit you bans. the char * list all bans made in the hub,
or you can search by nick, IP, DNS etc.

To use the showban in the hub just type.
!shownickbans (snb) <search> [offset] - Search among nick bans
!showipbans (sib) <search> [offset] - Search among IP bans
!showdnsbans (sdb) <search> [offset] - Search among DNS bans
!showclientbans (scb) <search> [offset] - Search among client bans
!showtemp (st) [offset] - Show temporary bans

To show the 200 latest bans made in the hub just type" !showipbans * " the * char is the trigger to list.
To use the offset just type like this "!showipbans * 51 " then it will list the all IP bans from 51 to 251

Miscellaneous

Hub command visibility
Force reply to PM - The hubs response to hub commands will always be in PM.
Show command written to self
Integrated command visibility - Decides who should see the commands written in mainchat in the hub - Makes the hub bot show the command written.

Integrated command visibility
Force reply to PM - The hubs response to integrated commands will always be in PM.

Nobody - None will see the command
The one writing - Only the one writing will be abel to see the command.
Operators - Only operators will be abel to see who is writing the command.
Operators and self - Operators and the users which is writing the command will be abel to see it.
Everyone - Everyone will be abel to see the command that is written in mainchat.

General searching
Max hits on hub integrated commands searches - Such as search on Bans, nicks and so on

Miscellaneous
Autosend own userIP on login - Send a userIP containing the users IP when connecting
( if supported )

Chatrooms

Name - The name you want the chat-room to have.
Welcome message - Here you are abel to set a welcome message as soon as the user enters the chat-room.
Here you can add and edit you chat-rooms in the hub.
Join style - Public ( Invites self), Private, Forced (auto join only)
Public = everyone in the hub can join the chat-room by typing +join in a message to the room.
Private = In this room you need to be invited. If you don´t have such a profile that you autojoin when you connect. The OP-chat is one example.
Forced = Every user that you have chosen on profile will be in this room,
if anyone types in it, it will popup a window and you don´t have to type +join to chat.
The OP-chat is one example of this.

Show chat-room as operator - The chat room will be shown as an operator. It will have a key infront.
Show feed messages - If you want the feed messages to be sent to this chat-room. The feed messages is chosen on Notification (show me)

J, AJ, A Profile
J: Profiles who may join the chat-room. - need to type +join to enter the chat-room.
AJ: Profiles that auto joins the chat-room. - it will work as the old OP-chat, it popup's whenever someone writes.
A: Profiles that may admin the chat-room. - May kick users out of the chat-room
Just type +help (+h) in the chat-room for available commands.

Hublists

Enable hublist registration - register your hub on the hublists.

Manage hublist server
Use this public registration server - Chooses if you want to use this hublist registration or not.
Name - Name of the hublist.
Description - The pinger description if any.
Host (DNS/IP) - The pingers IP or DNS.
Port - The port, the pinger uses.
Allow pinger to connect to other users - Some pingers uses this to verify that it is real users in the hub.

Recognition
Use a nick/nick pattern for the hublist pinger - Identify the pinger by it´s nick/nick pattern.
Use a IP/IP pattern for hublist pinger - Identify the pinger by it´s IP address or IP pattern.
Use host DNS to update pinger IP - Update the the pingers IP address through hublist host DNS.

Search Scanner

Enable Trigger on - Enable the private message scanner to trigger on this word/part of word.
Restrict match to the beginning of a word - Only trigger on words that begin with the
trigger ( ex. If triggers is "me", then the word "memory" will trigger, but "time" or
"summer" will not trigger)
Restrict match to the end of a word - Only trigger on words that end with the trigger.
(Ex. If trigger is "him", then the word whim will trigger, but "himself" or "whimp"
will not trigger.)
Action - Choose what action should be carried out on the word/user/message.
Level - When a user has equal or higher level. Then will the user not be affected by the action. ( 10 = Not overridable )
Reason - The reason for the action, that is sent to the user. Empty reason is allowed.

User Stats

Type
Disables userstats - Don´t store user data at all.
Store locally - Store user data in memory. ( will be cleared when the hub is restarted )
Note: in order to get the !ui hub command to work you need to enable userstats here.
If you don´t have MySQL, it will be enough to just enable it locally.
Use MySQL - Uses the MySQL database.
Prune - Automatically removes old users stats after "X" days.
Clear userstats - Clear all saved user data.

Users

Note: These settings only affects unaccounted users

Connection restrictions
May connect using passive mode - Allowed to connect using passive mode.
Require an account or registered ( Reg only ) - Only users with an account or who are self registered can connect.
Enable register ( Allowed users to register their nicks ) - Allowed users to register and unregistered their own nicks.  ( command is (+) or (!) regme <password> , (+) or (!) unregme
Enable ISP/IP check - Enable ISP/IP check on connecting user(s)
Allow IP´s not found in ISP list - Allow users with IP addresses that are not in the ISP/IP list to enter the hub.
Require prefix - User must use this prefix to enter the hub. (ex. [NORM] or [ USER] )
Min sharesize - Enable the minimum share requirements.
Min slots - Enable the minimum slot requirements.
Max slots - Enable the maximum slot limit.
Max sharesize - Enable the maximum sharesize limit.
Max hubs - Enables the maximum hubs limit.
Slot ratio - Enable the slot ratio requirements. ( slot ratio = slots / hubs )
Allow"tag-less" clients to bypass hub/slot restrictions - Clients without a tag can bypass hub/slot restrictions.( tag ex. <++ V:0.401,M:A,H:0/2/0,S:2> )

Protocol access
Search in active mode - Allow users to search while in active mode.
Search in passive mode - Allow users to search while in passive mode.
Send Mainchat messages - Allow users to send mainchat messages.
Send private messages - Allow users to send private messages.
Connect in active mode - Allow users to connect to each other in active mode.
Connect in passive mode - Allow users to connect to each other in passive mode.

General  User control  ISP  Miscellaneous  Overrides  Advanced  On Join

Profiles

To Profiles   To the top
Allowed to use (on/at) if they have less profile level.
Allowed to use (on/at) if they have the same or less profile level.
Allowed to use (on/at), regardless of profile level.
General
Profile settings
May use hub commands - Enables the user to access the hub commands. ( write !help for help )
Is operator - whether the user should be treated as an operator. Get a key infront of their name
May see hidden users - Allowed to see hidden users.
May hide self - Allowed to hide, you will not be shown in the nicklist.
Can enter even if hub is full - Enables the user to bypass the userlimit check.
Force hide share - Will change the users share in nicklist to 0 bytes and prohibit searches connection attempts to the user.
May hide share - Lets the user to hide/unhide his share and prohibit searches connection attempts to the user.
!hideshare <on/off> - Toggle hide share
(when hidden showing zero bytes plus no search/connect to you)
Note: This is not a perfect system, for an example. If a user has a Queue on you and you want to get his/hers list then your client says it´s OK and the other users client will send a OK, from here it´s not an hub issue. The hub has nothing to do with the client anymore they will communicate by them self.
So even if you have the "hide" on the other client will start downloading from you.

Connection restrictions
Set min share - Allow access to set min share. Allows to set min share via hub commands.
!setminshare <share> - Sets hub min share (sufix: KiB, MiB, GiB, TiB, PiB)
Set max share - Allow access to set max share. Allows to set max share via hub commands.
!setmaxshare <share> - Sets hub max share (ex. 50 GiB, 0 = disabled)
Set max hubs - Allow access to set max hubs. Allows to set max hubs via hub commands.
!setmaxhubs <hubs> - Set max hubs (0 = disabled)
Set min slots - Allow access to set min slots. Allows to set min slots via hub commands.
!setminslots <slots> - Set min slots (0 = disabled)
Set max slots - Allow access to set max slots. Allows to max slots via hub commands.
!setmaxslots <slots> - Set max slots (0 = disabled)
Set slotratio - Allow access to set slotratio. Allows to set slotratio via hub commands.
!setslotratio <ratio> - Set slotratio (min slots / hub, 0 = disabled)

Hub control
Save settings - Allowed to save settings, via hub commands.
!savesettings - Saves all YnHub settings to disk
Change userlimit - Allowed to change the userlimit, via hub commands.
!userlimit <count> - Set max amount of users allowed in the hub
Set topic - Allowed to change/delete topic, via hub commands.
!topic [topic] - Sets a hubtopic (no topic deletes current topic)
Redirect all - Allowed to redirect all affecting users,via hub commands.
!redirectall <address> [reason] - Redirects everyone on the hub!
Set workpace - Allowed to change workpace on the hub, via hub commands.
!workpace <pace> - Set the current workpace
Lock hub - Allowed to lock the hub disabling new connections.
!lock <on/off> - Sets lock on hub. When activated (on) hub appears offline
Lock mainchat - Allowed to disable mainchat.
!mainchat <on/off> - Disable the ability to post in main chat (override by operators and specially allowed users)

Information
Hub info - Allowed to fetch hub information.
!hubinfo (hi) - Hub information and statistics
Userinfo - Allowed to fetch user-info,can get detailed information of a user.
!userinfo (ui) [search] [offset] - Information on one or more users
Look here if you cant get the userstats to work
IP info - Allowed to fetch IP information.
!ipinfo (ii) [search] [offset] - Information on one or more ips
Nick info - Allowed to fetch nick information from an IP/IP range.
!nickinfo (ni) [search] [offset] - Nick information from an IP/IP range
Traffic info - Allowed to access traffic information on a user.
!trafficinfo (ti) <user> - Display users protocol message counts
Traffic stats - Allowed to request traffic stats.
!trafficstats (ts) [type] - Display traffic statistics (Types: Search, SR, Connect, NickList, MyINFO, MC, PM, Data, BW)

To Profiles   To the top
Allowed to use (on/at) if they have less profile level.
Allowed to use (on/at) if they have the same or less profile level.
Allowed to use (on/at), regardless of profile level.

Users
Accounts
Add account- Allowed to add profiles.
!addreg (ar) <nick> <pass> <profile> [ippattern] - Add an account
Remove account - Allowed to remove accounts.
!delreg (dr) <nick> - Delete an account (note: does not kick user if online)
List account - Allowed to list accounts.
!showreg (sr) <profile> <search> [offset] - Shows accounts,
use "all" as profile to list regardless of profile
Set profile - Allowed to change the profile on a account.
!setprofile <nick> <profile> - Sets the profile of an account
Set required IP/ISP range - Allowed to set IPS/IP range on account.
!setaccountip (sai) <nick> [ip] - Sets one or more IP/IP range(s) for the account, use ; as delimiter
!showaccountip (shai) <user> - Shows the required IP/IP range(s) for the account
Set comment - Allowed to set comments on account(s).
!setcomment <nick> <comment> - Sets a comment to the account
Set greeting - Allowed to set greeting on a account.
!setgreeting <account> <greeting>
Set expire-date - Allowed to set an expire-date on account(s).
!setexpiredate <nick> <expire-date> - Sets an expire date on an account
(Ex. "2005-01-17", "0" for permanent)
Set owner - Allowed to set owner on account(s).
!setowner <nick> <owner> - Sets an owner on an account (if no owner is supplied you become owner)
Set password - Allowed to set password on account(s).
changereg (cr) <oldnick> <newnick> [newpass]
Show password - Allowed to show password.
!showpass <user> - Shows the current password on <account>
!usershowpass <user> - Shows the current password of <nick>
Show profiles - Allowed to show profiles.
!showprofiles (sp) - Display all profiles available

User control
Block users - Allowed to block user(s).
!block <user> - Block user (user will become unable to search and download)
!unblock <user> - Unblocks user
Redirect user(s) - Allowed to redirect User(s).
!redirect <user> <address> [reason] - Redirects user to address
Drop user(s) - Allowed to drop user(s.)
!drop <user> - Drops a user
Kick user(s) - Allowed to kick user(s).
!kick <user> [reason] - Kicks a user and adds to tempban
Ban nick - Allowed to ban nick.
!bannick <user> [reason] - Bans a nick or pattern (Ex. *demo*, may be left/right/both truncated)
!shownickbans (snb) <search> [offset] - Search among nick bans
!clearnickbans (cnb) - Clears all nick bans (all possible)
!unban <user/ip/dns> - Unban's a user banned by Nick/IP/DNS
Ban IP/ISP range - Allow access to IP/IP range bans.
You are abel to ban multiple IP´s (ex. 127.1.*;127.2.*;127.3.*)
!banip <ip> [reason] - Bans a IP or IP range (Ex. 127.0.*)
!ban <user> [reason] - Bans a user by IP (User kicked)
!showipbans (sib) <search> [offset] - Search among IP bans
!clearipbans (cib) - Clears all IP bans (all possible)
!unban <user/ip/dns> - Unban's a user banned by Nick/IP/DNS
Ban DNS - Allow access DNS bans.
!bandns <dns> [reason] - Bans a DNS or DNS pattern (Ex. *.anydns.com, use ? as any char)
!showdnsbans (sdb) <search> [offset] - Search among DNS bans
!cleardnsbans (cdb) - Clears all DNS bans
!unban <user/ip/dns> - Unbans a user banned by Nick/IP/DNS
Ban Client - Allow access to client bans.
!banclient <client> [reason] - Bans a client or client pattern (Ex. DC++0.1*)
!showclientbans (scb) <search> [offset] - Search among client bans
!clearclientbans (ccb) - Clears all client bans
!unbanclient <client> - Unbans a client or client pattern
Tempban - Allow access to tempbans.
!showtemp (st) [offset] - Show temporary bans
!cleartemp (ct) [limit] - Clears <limit> temporary bans Ex. limit = 1: clears last tempban
Mutes user(s) - Allowed to mute user(s).
!mute <user> - Mutes user (Unable to post in mainchat, use * to mute all)
!unmute <user> - Unmutes user (able to post in mainchat again, use * to unmute all)
Lunarize user(s) - Allowed to lunarize user(s).
!lunarize <user> - Lunarizes user (makes user talk funny, use * to lunarize all)
!unlunarize <user> - Unlunarizes user (use * to unlunarize all)
Kennylize user(s) - Allowed to kennylize users(s).
!kennylize <user> - Kennylizes user (Posts in mainchat will be affected, use * to kennylize all)
!unkennylize <user> - Unkennylizes user (use * to unkennylize all)

To Profiles   To the top
Allowed to use (on/at) if they have less profile level.
Allowed to use (on/at) if they have the same or less profile level.
Allowed to use (on/at), regardless of profile level.

ISP
ISP´s
Add ISP - Allow access to add ISP.
!addisp <isp> [prefix] - Adds <isp> to ISP-list
Remove ISP - Allow access to remove ISP
!delisp - Removes from ISP-list
List ISP´s - Allow access to list ISP.
!showisp [isp] - Shows all isps or specified ISP (for more detailed information)
!searchisp (si) <search> [offset] - Searches among IP's showing matching ISPs
!matchisp (mi) <ip> - Looks for an ISP matching the <ip>
Set min share - Allow access to set min share for ISP.
!ispminshare <isp> <share> - Set min share for ISP (sufix: KiB, MiB, GiB, TiB, PiB)
Set max share - Allow access to set max share for ISP.
!ispmaxshare <isp> <share> - Set max share for ISP (ex. 50 GiB, 0 = disabled)
Set max hubs - Allow access to set max hubs for ISP.
!ispmaxhubs - Set max hubs for ISP (0 = disabled)
Set min slots - Allow access to set min slots for ISP.
!ispminslots - Set min slots for ISP (0 = disabled)
Set max slots - Allow access to set max slots for ISP.
!ispmaxslots - Set max slots for ISP (0 = disabled)
Set slot ratio - Allow access set slot ratio for ISP.
!ispslotratio - Set slotratio for iSP (min slots / hub, 0 = disabled)

IP on ISP´s
Add IP to ISP - Allow access to add IP to ISP.
!addip (ai) <ip> <isp> - Adds <ip> to <isp> approved
Remove IP from ISP - Allow access to remove IP from ISP.
!delip (di) <ip> <isp> - Removes <ip> from approved
Show IP´s on ISP - Allow access to show IP´s on ISP.
!ispiplist <isp> [offset] - Shows all approved IP/IP ranges for <isp>

To Profiles   To the top
Allowed to use (on/at) if they have less profile level.
Allowed to use (on/at) if they have the same or less profile level.
Allowed to use (on/at), regardless of profile level.

Miscellaneous
Redirects
!setredirect <type> [addr] - Sets a redirect, omit type and addr parameter to get available types
!showredirects - Shows current redirects
!setredirect all [addr] - Changes all redirects to the same address
Hub full - Can change redirect on hub full.
!setredirect full [addr]
Incorrect ISP/IP - Can change redirect on incorrect ISP/IP.
!setredirect isp [addr]
Low share - Can change redirect on to small share.
!setredirect lowshare [addr]
High share - Can change redirect on to large share.
!setredirect highshare [addr]
Reg only - Can change redirect if the hub is reg only.
!setredirect regonly [addr]
Passive - Can change redirect if using passive mode.
!setredirect passive [addr]
No tag - Can change redirect if missing a tag.
!setredirect notag [addr]
High hubs - Can change redirect if to many hubs.
!setredirect hubs [addr]
Low slots - Can change redirect if not enough slots.
!setredirect lowslots [addr]
High slots - Can change redirect on to many slots.
!setredirect highslots [addr]
Low slot ratio - Can change redirect on to slow slot ratio.
!setredirect slotratio [addr]
Banned - Can change redirect if banned.
!setredirect banned [addr]

Miscellaneous
Admin chatrooms - Allowed to admin chatrooms.
!addchatroom <name> - Adds a public chatroom
!delchatroom <name> - Removes a public chatroom
Admin textfiles - Allowed to change the text commands.
!textcommand <name> <on/off> - Enable/disable a text command
!settextcommand <name> <content> - Changes the content of a text command
!showtextcommand <name> - Shows the content of a text command
Admin registered - Allowed to registered users in the hub.
!useraddreg (uar) <nick> <pass> - Add a nick to registered
!userdelreg (udr) <nick> - Delete a nick from registered
!usershowreg (usr) <search> [offset] - Show registered
Use say command - Allowed allowed to use say command.
  !say <nick> <message> - Says <message> in mainchat as if <nick> said it
Use MC command - Allowed to access Mainchat commands.
!mc <message> - Sends <message> in mainchat from me
Use warn command - Allowed to use the warn command.
!warn <user> [reason] - Sends a warning to <user>
Use inform - Allowed access to inform.
!inform <user> <message> - Sends <message> as a private message to <user> from me
Use PM command - Allowed access to use the PM command.
!pm <message> - Sends a PM from me to everyone
Use PM profile command - Allowed access to use the PM profile.
!pmprofile <profile> <message> - Sends a PM to a specific profile.
Use OPM command - Allowed access to use the OPM command.
!opm <message> - Sends a PM from me to all operators

To Profiles   To the top
Allowed to use (on/at) if they have less profile level.
Allowed to use (on/at) if they have the same or less profile level.
Allowed to use (on/at), regardless of profile level.

Overrides
Privileges (Overrides)
Flood check - Allowed to override the flood check.
PM length limit check - Allowed to override the PM length limit.
Mainchat length limit check - Allowed to override the MC length limit.
IP check when connecting - Allowed to override the IP check when connecting.
Nick check in PM/MC - Allowed to override nick check in mainchat/PM
Bypass ISP/IP - Allowed to override ISp/IP check.
Override default/ISP tag restrictions - Allowed to override default ISP restrictions.
Allow"tag-less" clients to bypass hub/slot restrictions - Clients without a tag can bypass hub/slot
restrictions.( tag ex. <++ V:0.001,M;A,H:1/0/0,S:3> )
May connect using passive mode - Allowed to connect using passive mode.
Nickban - Allowed to override nickban.
IP/ISP range ban - Allowed to override IP/IP range.
DNS - Allowed to override DNS ban.
Client ban - Allowed to override client ban.
Tempban - Allowed to override the tempban.

To Profiles   To the top
Allowed to use (on/at) if they have less profile level.
Allowed to use (on/at) if they have the same or less profile level.
Allowed to use (on/at), regardless of profile level.

Advanced
Protocol access
Search in active mode - Allowed to search in active mode.
Search in passive mode - Allowed to search in passive mode.
Send mainchat messages - Allowed to send messages to mainchat.
Send private messages - Allowed to send private messages.
Connect in active mode - Allowed to connect to other users in active mode.
Connect in passive mode - Allowed to connect to other users in passive mode.

Feature access
May access MCTo - Enables the MCTo support. ( used by bots to by send a mainchat message to a single user )
Autosend User IP (UserIP2) -

Master overrides
Cannot be kicked - Cannot be kicked.
Cannot be dropped - Cannot be dropped.
Cannot be redirected - cannot be redirected.

Feed
Receive feed - Receive nameless feed. Feed sent via text command. Eg +report
Receive action feed - sends feed if (redirects, registration, bans etc.)
Receive kick feed - Sends feed if someone gets kicked.
Receive event feed - Sends feed when you change the listening ports.
Receive GUI feed - sends feed if changes are made in the GUI.
Receive error feed - Sends hub errors. If the hub get an error, the error will be sent to the chat.

To Profiles   To the top

On Join
Enable joining announcement ( announced to all in hub ) - Join announcement will be sent to everyone in the hub when a user of this profile level connects.
Available substitutes are:
<nick> -
<profile> -
<users> -
<dns> -
<ip> -
( ex. our bellowed<nick> has entered this hub, and his profile are <profile> )
( eg 2. <nick> enters the hub and just want to say that it is <users> users in the hub. )
(eg 3. <nick> has entered the hub and his/hers IP is:<ip> )

Accounts

Manage account
Nick - Enter a nick here.
Password - Enter a password here.
Profile - Choose profile on the user.
Owner - Choose owner.
IP Pattern - Only a user with matching IP/IP pattern will be allowed to use this account.
Expire date - Set a date when this account will expire.
Comment - Comment about the user.
Greeting - Message that will be sent to the user after connect.( only the connecting user will se this )

 Registered

Enable register ( Allow users to register their nicks ) - Allow users to register and unregister their own nicks.   ( command is (+) or (!) regme <password> , (+) or (!) unregme.
Search - You can search on registered users here. If you type * it will list all registered users.
Add/Edit - You can add or edit a name here.

ISP/IP

Enable ISP/IP check - Enable the ISP/IP check for connecting users.
Manage IP/IP patterns - Here you can add or delete a IP/IP range .A IP range is written like this. 195.54.107.*
Which allows the range between 195.54.107.0 to 195.54.107.255 to enter the hub.

Manage ISP
Name - Name of the ISP ( Internet Service Provider )
Description - You can write whatever you want here.
Prefix - One or more prefixes the user with this ISP should use. ( ex. [BBB];[LAN];[10Mbit] )
Allow"tag-less" clients to bypass hub/slot restrictions - Clients without a tag can bypass hub/slot
restrictions.( tag ex. <++ V:0.001,M;A,H:1/0/0,S:3> )
May connect using passive mode - Allowed to connect using passive mode.