3 replies to this topic

[kev]

A much updated version of our verlihub-0.9.8x is currently in testing stage. We hope to have this ready for roll out very soon.
New features include:
advanced flood protection
stability updates
numerous bug fixes
register user share manipulation (hiding)
penalty list commands
registered account viewing
class command controls
and many more aswell as some minor bug fixes and updates to some plugins.

If there is any special feature requests you would like to see added then now is the time to tell us about it.

[Megaron]

Thnx for making this and congrats for the forum

There are some things i would like to see in verli though i don't know if they are possible.
1st A reguser cleaner for the hub would be nice. To autoclean users that have never loged in after reging or long time to visit.
2nd I would like to have different max hub & slot rules for class 2 users.
3rd Can you fix a beta hub so we can see the changes made so far?

[spinmagiic]

A much updated version of our verlihub-0.9.8x is currently in testing stage. We hope to have this ready for roll out very soon.

If there is anyone on planet earth that can do it, its my hero, kev. congrats on the forum and cant wait to see the new stuff.............

[kev]

Thnx for making this and congrats for the forum

There are some things i would like to see in verli though i don't know if they are possible.
1st A reguser cleaner for the hub would be nice. To autoclean users that have never loged in after reging or long time to visit.
2nd I would like to have different max hub & slot rules for class 2 users.
3rd Can you fix a beta hub so we can see the changes made so far?

Your first point I think I can come to a comprimise. There is the addition of a function which allows you to view regged accounts by class. Now I did intend to keep the returned info to to just nick and class in the first instance. I will look into expanding on this to include some other info that would be useful for administration purposes.

For you second point there is already a function that allows you to specify the min class of user whos tag will be checked. Although this doesnt allow you to specify seperate requirments per class its still one setting for all. I do like your idea but I dont think its something we have time to implement as we really want to get this hubsoft finished asap.

And point 3, I sure can ill update this post in the next couple of days with details.
Thanks