DCH++ is a high-performance hub for the Direct Connect network. The main features are (in comparison with Neo-Modus hub):
* More difficult to use
This is not a good hub to start your hub career with as it has no friendly user interface.
* Low CPU and memory usage
Being written in C++ and carefully profiled, performance is kept at a maximum for the feature set present. To
further enhance the performance, there is no user interface. The application is meant to run as a service, but
can also be run from the console.
* Low bandwidth usage
Using various optimizations, DCH++ uses a lot less bandwidth than NMDCHub. As an example, the full list of nicks
is not sent to the user until he's been fully validated and checked, neither is the notification that a user
has arrived.
* Convenient for the users
Doesn't sent a lot of worthless information to the users such as kick messages and join/part messages for users
that are kicked during the login phase (for instance, because they don't share enough).
* More hack proof
Because it's actually being developed, any hacks that come to the authors knowledge are fixed.
* No scripts
Instead of scripts, DCH++ uses compiled C++ plugins to maximize performance (scripts are dreadfully slow and
memory-consuming). This has the disadvantage that there's no simple way for non-programmers to add features.
There is of course the possibility of writing a script plugin, that would enable scripting for DCH++,
and if you feel like helping out, this is a good place to try. Packed and developed together with DCH++ is
for example a LUA plugin that runs LUA scripts (
www.lua.org).
* Different userlevels
Each user that is allowed into the hub is assigned a level that is used to determine things such as min share
and if the user is an op. This can also be to create superusers that can not be kicked, or VIP accounts that
don't need to share. The number of levels is unlimited, as opposed to the normal 2-4 level systems hubs employ.
* Configurable
There are a lot of tasty details in the settings file for the competent hub owner to change.
* Multiple hub-lists
You can make the hub register to an arbitrary number of hub lists.
* No "Hub is full" message for op's and vips
Each userlevel can be set to ignore the max users limit.
* Basic flood protection
Flood protection is present for any costly operation (search, chat, myinfo update).
* Ban time shown to user
When a user is (temp)banned, a "time left" message is sent to him to spare the owner of stupid questions.
* Nick and description length checks
Avoid long nicks and descriptions to decrease bandwidth usage and get rid of idiots.
* Internationalization
You can load different language files to be used when communicating with the users.
... 
. . and hope cross my fingures the one i allready wrote will work with it