So I'm only bringing this up in case it is also a problem with 0.5.x ... if its been addressed then no worries.

I had a bot (well, someone else created it) running 0.4.1 that was not an org bot. We added many people to it as members manually so that they could use it as a raid bot. However ever since FC's XML roster problems started up we have had the bot regularly purge its entire member list.

The culprit seems to have been the area in Roster.php that deletes a member (search for the if ($id) line that has this text: 'as the character appears to have been deleted.').

I'm not sure if the person who created the bot messed up something or not. I wouldn't think Roster would need to run in a non-org bot. I checked the config file and it was not set up as an org bot. So it may not be a bug so much as the bot just thinking it needed to run Roster when it didn't. Or maybe Roster needs to run even when not an org bot?

Anyway, with all the times that Roster is not working on our orgbots (we have well over 1K users and the server often times out before it responds), it seems Roster might need some robustification. Not sure if it has had an overhaul for 0.5.x or not.