I am not realeasing my newest version of the Modified Generalbot Until I make some more additions to it. I have added a list of what I have completed so far. I am still workin on adding some new awesome features like a add-in script for backup of hub settings, Because I hate losing my new weekend bans when the pc crashes on my remote connection. I have also found a different way of constructing the way the script works to be more efficient with the 64k space we have to write them in. and all this In addition to learning this damn LUA scripting for that Ptokax Hubsoftware. But ptokax still needs Improving. It may be a while before I finish this one :( But.... Good Things come to those who wait!! :) GeneralBot.L8.503.241.script 5.19.03 UNRELEASED - Still makin it better !GeneralBotSettings.421.503.script 5.19.03 UNRELEASED Just when u think I cant screw it up any worse I really did it this time!! I removed all the settings from the script, and make it read them from the registry WTF? the registry? How do they get there? Here is your answer: I made another script that does that, this is my way of makin a way for all my to talk to each other. Other New Features added: Added new level of security - Hub owner (for powerop and depowerop commands) Enable so any OP can grant VIP status -powerop Add an OP to the Powerop list -depowerop -botinfo display all of the bot settings in PM -reset Update both scripts (if setting changes, like -powerop) -read synchronize both scripts (just reads the settings from the registry) -repass Yup, I dig that one (CaSeSeNsItIvE) L8.503.241 4.27.03 UNRELEASED I have really fucked it up this time.... I have split it into 2 scripts, one that saves the settings to the registry, and it is just like the main genbot, but with the settings removed (and put in registry) I fixed allthe bugs with the -maxusers and -hubmax commands, so now they work proberly I added the -repass command, so ops can change their password (cAsE SeNsItIvE ToO) I added the -powerop and workin on -depowerop, to modify the powerops array I enabled it so all OPs can Register VIP users L8.421.241.4+++ 4.15.03 I fixed the bug with the -minslots command!! it works properly now!! I put back the -flood and -fuckup commands I fixed how it reports the -status to look more friendly (with status first so it lines up) l8.421.241.4+ 4.12.03 I modded the -slots command to send in a pm, and show the slots first, so it looks more organized I disable the -flood and -fuckup command in just this version, this is because I had too many ops flooding when they should not be -attack is the new command for flooding, l8.421.241.4 slots command available for users (fixed, does not show IP anymore for users) l8.421.241.3+ -smack command mimics command from UTB Script -hubmax set hub Max Users -minshare set minimum share for users. -vipshare set minimum share for VIP users. -mass sends a message to all connected users -mmop sends a message to all connected ops -fuckup = -flood -smack = -kill = -kickban -setredir = -changeredirect -maxusers = -setmaxusers -logon or -logoff Turns OPchat on/off -status check status of Ops Logged into OPchat Added special bad user array Added special fake share array Made it announce to main chat when you add a new OP or VIP a user Fixed so BCDC++ users can use the right click UserIP command Added a user description for the Bots in the User list Fixed follow function to show how many attempts Successful, Failed, Searches, It also reports this info to the failed user Increased security for what regular ops and powerops can do Change the variable sCmdPrefix to sCd to conserve script size Deleted all extra spaces to conserve script size l8.421.241.2 -findslots command for users -smack command for ops -changeredirect -maxusers -hubmax -minshare -vipshare -mass -mmop