Okies... so I sat here mulling over the Auto update part with an integrated !seen command
This version is pretty much reworked in alot of ways.

• 1st I ditched the redundant(same code for 2 different channels) manual Member handling routine I had had incorporated from Rooster_RAID.php
• 2nd I blended in Wanuarmi lastseen.php, which I had to modify that a bit to get it to work using the Member table.
• 3rd (which took a little more thinking over than I thought it would) I had to update the way the Cron job stored member info. In the original manner it completely Deleted the contents of the Member table before updating it. This was a bad thing since I wanted to store the "lastseen" timestamp there. Solution? Don't dump the contents of the table using DELETE, create a conditional routine that checks to see if there is a timestamp recorded (not the Default 0), grab that time stamp and set it to a Variable to be re-inserted with other updated info from FC server. Then instead of using an INSERT INTO we use REPLACE INTO. Why you ask? Well to quote the MySQL Docs -- "REPLACE works exactly like INSERT, except that if an old record in the table has the same value as a new record for a PRIMARY KEY or a UNIQUE index, the old record is deleted before the new record is inserted." In other words I can grab values from the Table I don't want to loose before they get re-inserted.
• I dumped the columns for the Picture and Level Range since nothing in Bebot seemed to be using them.
• ++ Last addition, this one is now aware of messages in Org. Msg. channel. Bot will auto add/remove Org members as it witnesses those events.

Here's the code, I have it running on my bot currently and it works. Take a read through it and if you've played with the Rooster enough you'll notice the changes. Oh and I also changed the formating a bit on the !seen output from Wanuarmi's

21 May 2006 Edit: I'm happy and I am done with this module. The member update Cron job does what it's supposed to do now and doesn't disturb guests on the bots Buddy list. It still contains all the previous notes above. I did this update mostly to fix issues with Guest auto inviting. BTW, the Auto inviting fixes go beyond the scope of this file. There were also fixes to AutoInv.php and Relay_GUILD.php. You can find those FILES HERE
There are also some fixed functions in Bot.php that needed to be done. They are is_member() and inc_buddy(), I placed those functions in a text file here rather than post my entire customized Bot.php. If your using a stock Bot.php replacing these functions shouldn't mess up anything else.

11 Jan 07 Edit: Updated links to files in this post. See link in my Sig for all other files posted by me around these forums.

Hi Xenixa,

Works great here, no problems at all so far =)

p.s. did you ever post your working auto-invite guests code, did a quick scout on forum and couldn't find.

Cheers,

-jj-

Just put this on my bot. One thing I noted is that my members table had the fields ai_rank_id and ai_rank instead of ailevel and aititle, so I had to go through and change all the references.

Hrrm ok, so sow does the Roster Updates relate to auto invites you may be wondering?
Well else were I have posted fixes to Bot.php, and AutoInv.php that address actual Auto Inviting of people on the Guest list. Well since bots rely on knowing when people logon by them being in the bots Buddy list, Rooster_GUILD.php would prevent this.

So, I looked at this 2 ways and the best solution I could think of was to just do a simple comparison against the Guest Table. Or if you want to try it yourself, Find in Rooster_GUILD.php I have above:// Remove buddys not on list...
foreach ($buds as $id => $value)
{
$this -> bot -> aoc -> buddy_remove($id);
$this -> bot -> log("BUDDY", "DEL", $this -> bot -> aoc -> get_uname($id));
}Replace with:// Remove buddys not on list...
foreach ($buds as $id => $value)
{
//Auto Invite Fix: Test to see if buddy exsists on Guestlist first. Don't remove if they are.
$gbuds = $this -> bot -> db -> select("SELECT id FROM guests WHERE id = $id");
if (empty($gbuds[0][0]))
{
$this -> bot -> aoc -> buddy_remove($id);
$this -> bot -> log("BUDDY", "DEL", $this -> bot -> aoc -> get_uname($id));
}
}The updated AutoInv.php can be found on my ftp server here ftp://xen.afraid.org/bebot_files/
And changes to Bot.php can be found here: http://bebot.link/index.php/topic,255.0.html

You may have to remove then re-add people from the guest list so they can start getting Auto Invited on logon.
Also after restarting the bot don't forget to do a !autoinv on

I saw that happen before the changes I made. Usually doing an !is will knock them off Online list if they logged out.

Edit: I looked this again Ainen, It's an issue with the Online.php ... It seems to base the Members online by read it's own buddylist with AND like condition on the is_member function.

Hi Xenixa,

Still using the code above plus the various fixes - autoinvite works perfectly :-)

However, one problem I found is that if someone leaves org, the member does not get deleted at next roster check (you can delete manually with the !member command though).

Just wondered if this was a side-effect of not removing the guests from buddy list or could it be fixed?

Either way, just to let you know this problem exists (and is fixable manually).

Cheers,

-jj-

Ya, I've noticed this one also.

Problem is in order to keep the lastseen column from getting nuked I changed it so it wouldn't delete the whole list of Org members. What I failed to realize was that members could get stuck on that table if no one wasn't actively keeping track of there Org's roster and deleting them from the bot.

I been working on another method actually as time permits that should fix this.

There are two different approaches to this issue that i can see.

The easy way is to grab the messages from Org. Msg. which we should be doing (and will be doing) and use it to delete members, and simply leave it up to the administrators of the bot to delete any members missed by the automated system.

The second way, which isn't quite as easy, is still grabbing the messages by automated removal, but also actually validating the list somehow, I'm just not sure what way would be best.
My original thoughts went towards md5'ing the org XML, however that would pick up on a lot of changes not related to org additions and leavings. Another avenue would be using the member count, but even that is prone to problems as it can occur that a member leaves and a member is added in a single day, in which case the member count would stay the same but the org rooster would remain unchanged.

Bot's nowdays barring server issues tend to stay online almost constantly though so it could be argued that a more sophisticated approach than the first is a total waste anyways.

You could use a combination of the the method used now and the ["Org. Msg."].  Just add the functionality of (.+) (joined|left) the org./i into the system, and max out the cron time.  I realize it's double redundancy, but it will not only provide real-time updates to the roster, but also provide the reliability of a periodic revamp of the roster as well.

Just starting my delve into Bebot, so I apologize if this method has been trashed before or there are prior reasons for not using it.

- Tsuyoi