#1 Please make a reglist command, it is something very basic. We should not use scripts for this. Some other basic things, in my opinion: adding a chatroom for a specific class or above, leaving a message to an offline user...

#2 Display in !hubinfo how many users are on each listening port. Very useful when you have more DNS's pointing to your hub.

#3 If a user can not join a hub because his nick is already taken, please redirect that user... especially very usefull when you merge 2 or more big hubs.

#4 I think verlihub is the only hubsoft where you need to use !restart after changing something like hub security or opchat name. Is so difficult to send a $Quit|$Hello|$OpList to all connected and pending users ? Or to open some more listening ports while the hub is running ?...

#5 Please introduce a very nice concept: "private chatrooms". A chatroom that each user (op or not) has and where he can invite and uninvite anyone he likes. So that I can use my own chatroom to talk with only 3 or 4 users... and nobody else will see what we talk there because it is MY OWN private chatroom.

#6 Add something like !deepban where the hub appears offline to the banned user who tries to join. Also, if a user is banned, why he has to see the "logo" message and how many users are on the hub, what is the hub uptime etc ? Deprive him of such informations... since he is banned...

#7 Now almost all clients (DC, Strong, Apex) when they connect to another client to get their filelist, they send a "reference" to the hub that initiated the connection. Like this: $MyNick Lotus|$Lock EXTENDEDPROTOCOLABCABCABCABCABCABC Pk=DCPLUSPLUS0.760Ref=abc.no-ip.org. The hub abc.no-ip.org is the hub that sent the $CTM to my client. Now, if many users try to connect TO A HUB sending $MyNick instead of $Key then it is very likely a CTM Flood/DDoS and it is a good ideea to display the hub reference in opchat...

#8 Make a !hinfo of something where the user can see what is the search interval for him, if he can chat/download/search, etc, useful information that are usually hidden for regular users and affects him.

#9 Penalties (like gag, ban etc) should be redesigned. There are 3 types: gag (can not send main/pm messages), block (can not search/download) and ban (can not join the hub). Since you can ban a user for a time, after an ip/nick/prefix etc, you should also be able to gag or block him in the same way...
One simple idea is to make a "centralized" command, like:

!pen(alize) flag1 flag2 target time reason

flag1 is: 1 = gag, 2 = block, 4 = ban, 8 = deepban (see #6)

flag2 is saying what target is (a nick, an ip, a share, a description, an email, a tag...)