Well another month between updates, man i am a crazy nut. Anyways, here we go people. Please READ THIS WHOLE POST! The information at the bottom is VERY IMPORTANT as it will help optimise GuarDDog.
GuarD-Doctor1. Replaced the prompt (when error occurs) from a prompt input to a dialog. Prior to this update, the prompt will cause mIRC to stop all it's opperations. This meant that you did not receieve any data till you accepted. This has now been fixed by use of a dialog.
2. When uinstalling an addon, GuarD-Doctor will close all related dialogs to the addon that you are uninstalling. This should prevent some "cannot remove" errors that were occuring.
3. Due to some people liking to delete folders which are used for GuarDDog, i have to implement an auto recreating system so that folders stay in place.
DogCollar Connection
1. Fixed the Away/Return problem. In Version 1.3.8, the away/return would not be told to mIRC. This has now been fixed.
Choke Chain Protection
1. Added another if-error-trap to stop some of the /hmake errors that were occuring on updating.
2. Added seperate controls for the joint protections. Joint protection is where an event occurs of the same nature but form multiple users. This is useful to stopping those annoying mass ctcp flooders and that.
3. When clicking "Apply to current room", it added a colon to the front of it, this has now been fixed.
4. Some people were getting disconnected easily by CTCP checks, this has now been solved.
5. Seperated the joint flood protections from the individual flood protections to allow for you to configurate them as you wish.
6. In the event of a flood, sometimes GuarDDog would kick the person removing the flood. This has now been fixed.
7. Put in a filter so that if the user that joins is owner in the room in a flood, they shouldn't get kicked.
AOP System
1. Split the database from the main controls. This enables you to have more control over the entries in the AOP System.
2. Modified the AOP Control system so that it opperates faster when switching between level's commands.
3. Moved the level commands to their own tabs.
4. Added in options which are AOP Level based, meaning you can have some options for the AOP level, and others not.
5. Added "Custom Commands". This allows you to input your own code into the system, and have it work with the current AOP system in GD5.
6. Fixed <prefix>ddeny to display properly.
7. Fixed a few typos here and there.
8. With "level based options" i made a few new commands such as "Auto add hosted to Local Hosted" which will allow GD5 to self maintain the databases for the chatrooms.
9. This was requested by a user a while back, only implemented now, "Protect user". This will protect people on the AOP system if they are removed by another user on the same level.
10. Now, when a user comes in and already has the status that the AOP System has been told that the user should have, it will not change their status (meaning that if they are local owner, and they came in with a gold hammer already, it will not deowner and reowner them).
11. Modified "Auto unban" so that it now adds a voice entry for 5 minutes to allow the user to rejoin, even if room is on invite only or room limit is full or key is required.
BibleBot
1. Fixed the remote concordance to work as it should. Some how some of the variables ended up in the wrong spot (blames mIRC
).
2. Done modifications to current focus verse which should mean that the focus verse will not triggure if there is no focus verse in play (or you do not have any bibles installed).
NickList
1. Modified the dialog slightly to appear more "fitting" in the list.
*** VERY IMPORTANT NOTES ***
For starters, please everyone, open up Choke Chain Protection and view your "Flood and Mass Protect" options. You will notice, there are a few new introductions. In the previous update, this was a hidden thing, well not hidden, but linked off the same settings. I have seperated them so that you can customize them. Please note the words "Inividual" and "Joint" on some of these protections now. Individual means that just 1 user is trigguring the event. Joint means that multiple users are trigguring the event. For example, if you have issues with having multiple accounts massing time requesting your chat room, this would be protected through "CTCP Flooding (Joint)". MAKE SURE YOU CONFIGURE ALL THE JOINT SETTINGS. The inidvidual settings remain the same as what was previously in place. There are 3 joint settings in total, so make sure you adjust them ALL!
Now moving to the new AOP System. You will notice that there are now two options for AOP system, AOP Database and AOP Control. AOP database is the database for your AOP system. In the previous version, this was on the front of the main dialog. Please be aware, it's broken into 3 sections, Global View (meaning view all Global Entires), Local View (meaning view all entries for the individual rooms) and *NEW* room view. Room view allows you to see the current room, and all the users in it, as well as their AOP level and AOP tags. For AOP Control, the inbuilt commands have been placed on their own. This is to allow you to see the list better. I have also placed level based options in. This means that there is custom options for specific levels. BE AWARE, SOME OF THESE OPTIONS COULD MEAN THAT YOUR ROOM CAN BE SUSPECTABLE TO TAKE OVERS!!! Only apply the "Auto add to local owner/local host" to those level which you can TRUST!!!
Yes it's here the ability to put in all your own little commands into GD5's AOP System! It does have a few rules in it, but overall, ALL your codes that you would use in a normal script will work in the Custom Commands section of the AOP Control. Be sure to test it with basic commands before pushing it with big stuff. I will need feedback on this over the next few hours before i'm gone so that i can correct any errors that occur to users as i only implemented it, not tested it properly.
That is all people, i hope that these new implementations will be enough to keep GuarDDog going. AND YES I BELIEVE I FIXED THE CTCP FLOOD OUT PROBLEM that people were having (like (Michael)) so it should be safe and stable to update to.
Please try these new things and get back to me within the next few hours (6 hours and counting down) as it will be the last of the updates unless it is CRITICAL that i need to update, like MSN botching up everything again.
my global ban list is not working now after this update. i have seen peeps i know are on the ban list come in, i click on there nick and go to the aop settings ans i see options to change there leval, so i know they are in there. i check in the database and see there gatekeeper. i have gone into settings too and i have "enable global ban list" checked still the peep comes in, no kick no ban. another owner of the room also has a GD5 in there and he has the peeps on his global ban also, his GD5 dose not kick them either. he also got the latest updates. any ideas?? anyone else having this problem?
.