I've encountered a problem using the help queue recently. If the bot is already sending data to a user, and then it loads the same data into the queue to be sent to another person, it will send it to the second person in the wrong order.
Basically, it cuts the output at the point between what had already been sent to the first person and what it had left to send to that person, although both users still receive the complete information.
Here's an example. It should be clear where the data *should* have begun and *should* have finished..
[03:16] <Dazzle^> sb userlist
[03:16] <@ClubCX> It's like an expanded version of handlelist
[03:16] <Raven1089> sb userlist
[03:16] <@ClubCX> sb userlist
[03:16] -SiliconBot- Channel Access: ChanOwner
[03:16] -SiliconBot- Known Hosts: *!jewel@*.uk.com
[03:16] -SiliconBot- First Added: 29 Jan 2002 (20:48) Last Seen: 01 Jan 1970 (00:00)
[03:16] -SiliconBot- End of userlist
[03:16] -SiliconBot- #training Userlist
[03:16] -SiliconBot- [1] Handle: ClubCX Global Flags: fhjmnoptxAL
I seem to recall hearing that duplicate messages to the same target were being prevented, but since this is to different targets it should be unaffected. I've only encountered this problem since upgrading to 1.6.8. Has anybody else seen anything like this?
- Tom
http://www.botservice.net
This is the new home of the egghelp.org community forum.
All data has been migrated (including user logins/passwords) to a new phpBB version.
For more information, see this announcement post. Click the X in the top right-corner of this box to dismiss this message.
All data has been migrated (including user logins/passwords) to a new phpBB version.
For more information, see this announcement post. Click the X in the top right-corner of this box to dismiss this message.
queue problem
without testing this myself, here is my theory.
my guess is that the bot is taking advantage of stacked messages, ie PRIVMSG nick1,nick2,nick3,nick4,nickN :message
Thus, lets say you have 5 lines to send to the ppl, which are A, B, C, D and E. This is what could be happening
<nick1> !trigger
<bot> PRIVMSG nick1 :A
<bot> PRIVMSG nick1 :B
<nick2> !trigger
<bot> PRIVMSG nick1,nick2 :C
<bot> PRIVMSG nick1,nick2
<bot> PRIVMSG nick1,nick2 :E
<bot> PRIVMSG nick2 :A
<bot> PRIVMSG nick2 :B
you should enable console mode +v to see if this is really what is happening.
my guess is that the bot is taking advantage of stacked messages, ie PRIVMSG nick1,nick2,nick3,nick4,nickN :message
Thus, lets say you have 5 lines to send to the ppl, which are A, B, C, D and E. This is what could be happening
<nick1> !trigger
<bot> PRIVMSG nick1 :A
<bot> PRIVMSG nick1 :B
<nick2> !trigger
<bot> PRIVMSG nick1,nick2 :C
<bot> PRIVMSG nick1,nick2
<bot> PRIVMSG nick1,nick2 :E
<bot> PRIVMSG nick2 :A
<bot> PRIVMSG nick2 :B
you should enable console mode +v to see if this is really what is happening.
The 'stacked messages' suggestion seems to be the most feasible explanation. If that's the case, perhaps somebody could explain why it is present.
I believe that having messages sent in this way is inappropriate for NOTICE, and probably just as much so for PRIVMSG. I didn't find anything in the newest version of the conf file that mentioned it, so I'll assume it's a compulsory feature. Is it really neccessary?
- Tom
I believe that having messages sent in this way is inappropriate for NOTICE, and probably just as much so for PRIVMSG. I didn't find anything in the newest version of the conf file that mentioned it, so I'll assume it's a compulsory feature. Is it really neccessary?
- Tom