Topic: AutoMember

[Temar]

AutoMember.php

AutoMember

This Module will Automatically add Users who Join the Private Group to Member List
After you Get this and restart your bot you need to turn it on
/tell botname !set
and click AutoMember
also You can Use the Faction and Minlevel setting from flexible security if you want
Don't turn Restrict on if you are not using Flexible Security as it will Prob Add nobody

Your can Now Set it to Remove member when they leave Guest Channel
You can Have Temp Member on if you want it to ONLY delete temp member and will not delete your normal members

AutoMemberClean

Part of the Module will Clean your Member List For you
The setting for who to remove are Level and Faction
there is a safe list to add people you don't want to be deleted
i didn't see a point with having the lower than level so its only higher than XX level
default set to 220 so thats 221+ so no 1 (except maybe a GM)

also Does a Check for faction (Default is None)
you set faction in setting and you chose the faction you WANT to be deleted
example i have a clan bot set to Not Clan, and that will remove Neutral and Omni

How to Use
cleansafe add <name> " add to Safe list "
cleansafe del <name> " Delete from safe list "
cleansafe rem <name> " Delete from safe list "
cleannow " Make it do a Clean now, although it should do every 24hr and on bot boot "

Any more changed Etc Please reply to topic

oh and dont forget to turn on and set my module with !set AutoMember and !set AutoMemberClean

Change Log

• 15/07/07 [1.5] - Changed AutoMemberClean so it Only Checks Level of Members and not those already Deleted
• 15/07/07 [1.6] - Add Option to Send Extra Msg to People That get Removed by AutoMemberClean
• 16/07/07 [1.7] - Some bugs Fixed inc a delay because of Spamming blocking tells
• 17/07/07 [1.8] - Few more Minor Bug Fixes
• 27/09/07 [1.9] - Sorted Format of Code out with slight improvements
• 27/09/07 [1.10] - Added Faction Checking
• 27/09/07 [1.11] - Fixed Manual Clean not Working when Cron is OFF
• 27/09/07 [1.12] - Added Count+Blob with All info
• 23/01/08 [1.13] - Added Buddy List Limit (sets some as inactive)
• 01/02/08 [1.14] - Now Using 0.5.0 Version (Requires 0.5.0Support.php if your Lower)
• 23/05/08 [2.0] - Updated to 0.5
• 28/05/08 [2.1] - Moved Safe list to Own Table and Added expire time (Default 48hours)
• 28/05/08 [2.2] - Changed AutoBan to only ban if not invited, other wise output warning
• 11/08/08 [2.3] - Fixed Issues with user not getting added/removed to safelist cache when added/removed
• 11/08/08 [2.4] - Fixed AutoBan Prevention if Invited
• 14/08/08 [2.5] - Added Timeout for !invite ban prevention
• 09/03/10 [2.6] - Not idea but prob fixes i did awhile ago

[Temar]

Well my Raid bot was getting to 1k (983)
so i added some code to this module
it now removes some users from buddy list only
they are still members
it choses the members with oldest last_seen

they are readded iver by bot simple because of space (requires 20+ space before this is triggered)
or if they join the privgroup they will be readded also

they also get notified of the status change with bot (altho chances are most will never be read, inactive accounts)

[clashbot]

Error message Fatal error: call to undefined method AOChat::buddy_rem() in automember.php on line 338

[Temar]

oops thats code for 0.5.0 ill fix when i get in from work in about 2 hours and 30mins

[clashbot]

lol...ok...how stable is 5 now?

[Temar]

its good i always use it
There is a post i have done under unofficial module 0.5.0 to easily down load it

[Temar]

ok Now i Have Posted the 0.5.0
If you are still running 0.4.3 get the Module i just posted and it should work, along with other 0.5.0 modules 

[clashbot]

I hate being the harbinger of bad news, but got another error on the same line, "call to a member function buddy_remove() on a non-object in automember.php on line 338"

[clashbot]

nvm again, saw the support module...having a blonde night

[Alreadythere]

lol...ok...how stable is 5 now?

0.5 is pretty stable at the moment.

[Temar]

Today there was an Omni on my Clan bot
This user had Changed Sides and would of been removed on next memberclean
but till then he can have access?

so i added a Check when members join Pgroup
if not on the safelist
and meets the req to Ban (see !set automember and setting autoban)
He will be Kicked and Banned from Bot

The only Problem i can see at the moment would be if u Invite an Omni
you can add them to safelist but i wana try find a better solution to determin if they were invited or not

[DocJones]

Today there was an Omni on my Clan bot
This user had Changed Sides and would of been removed on next memberclean
but till then he can have access?

so i added a Check when members join Pgroup
if not on the safelist
and meets the req to Ban (see !set automember and setting autoban)
He will be Kicked and Banned from Bot

The only Problem i can see at the moment would be if u Invite an Omni
you can add them to safelist but i wana try find a better solution to determin if they were invited or not

I have set up a TL5+ froob raid force and added the mixlevel (150) and ai_level (0) restriction to the pgjoin/clean function. However, i have the problem that a lower levelled toon can join, get's added and will be deleted only when a !cleannow / reboot occurs.
What do i have to do to enforce the TL5+/Froob requirements upon joining?

thanks
/d

[Temar]

you need to set join to guest. Then use flexible security to give the users you want on bot guest access.

[clashbot]

is this working with the 5.1 branch?

[Temar]

prob not, its 3month old since updated, ill to is tomorrow, going bed now