Archive > AO official modules
Updated Points.php
jjones666:
The two showing in top25 are in guild, the one which doesn't show isn't in guild.
-jj-
Khalem:
Ok.
This is happening because blondengy probably never intended the points module to be used outside of a stand alone raid bot.
Basically whats happening is that your out of guild buddy is getting his points stored in the raid points table. However, the raid table only contains the character id. This characterid is then referenced with the members table to get the name of the character. On a guild bot, non guilded users wont be in the members table, which is also why he wont show in top25 :\
Im not sure if there is really a good way to handle this case short of adding the name to the raid points table. The problem with that again is that you'd be storing a lot of uneccecary data as 99% of the people with raid points, will either be members of the guild if its a guild bot, or everyone in the case of a raid bot.
Then again im dead tired atm, anyone else have thoughts on this one?
jjones666:
Easy to fix :-)
http://bebot.fieses.net/viewtopic.php?t=135
Using Xenixa's updated ROOSTER_GUILD script above, so manually added member to bot's roster with !member command.
Works fine now :-)
Cheers for the support Khalem!
-jj-
Khalem:
Actually, that wont fix it too well though :(
The problem lies with how the rest of the Guild rooster is handeled.
Every 12 hours the bot basically deletes the guild rooster and updates it from the funcom XML (not a solution im too happy with), so in under 12 hours, when the cronjob to update the guild rooster runs again, he will be removed :\
I'll need to think about this one a bit more, definately not something i want to do in my current tired state.
Xenixa:
I myself thought that over in the past. The best solution for my org was to just make a 2nd Org Raid bot seperate of the Organization bot since we leave the Relay on at all times for guests.
Running a raid with raid chatter in the Org bots Private channel only servered to annoy Org members and guests not involved in the raid.
You can still use the same database for a Raid bot and a Guild bot so thats not really an issue.
Oh and the !member command in my Rooster_GUILD.php is only a temporary thing. When our recruiting Dept adds a new member they toss them on the Member roster so their on the bot buddy list until FC gets around to making it's updates. My own personal copy of Rooster_GUILD has the cron job set to 18 hrs BTW for the rare occation that someone may be added in that period just after FC update's the XML db's. Just keeps them from being removed from the bots buddy list to soon really.
Edit: I guess I should mention I added a 18hr Cron job to the Bot.php also. :)
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version