incith wrote:I'm not sure what version you're using,Hello,
Using incith weather v2.8p
Thanks for reply and the tip.I'm guessing I just made this change recently in my local copy.
Basically, do a search for putserv and replace them with putquick and this should make the output instant.
What does SVN mean?The SVN version has this already (and !time) -- http://svn.incith.com/index/incith/trunk/#path_trunk_
Sure, eggdrop queues. You see, most people get the mistaken impression that using putserv instead of puthelp or putquick instead of putserv that your actually going to see the output faster. This isn't entirely true (as usually at then 4th or 5th line it will slow down), to really get instantaneous output requires building a new procedure, perhaps the putnow function can be used (but will definitely get your eggdrop excess flooded every now and then). Eggdrop will natively queue your messages regardless of which command you use to put*.willyw wrote:Yes, it did make a difference. But only for the first 5 lines of output.
They came up very quickly. Much nicer.
But the remaining lines came up same as before - Line-by-line with a little pause between each.
Any ideas as to what is causing this?
Thanks for the reply.speechles wrote:Sure, eggdrop queues. You see, most people get the mistaken impression that using putserv instead of puthelp or putquick instead of putserv that your actually going to see the output faster. This isn't entirely true (as usually at then 4th or 5th line it will slow down), to really get instantaneous output requires building a new procedure, perhaps the putnow function can be used (but will definitely get your eggdrop excess flooded every now and then). Eggdrop will natively queue your messages regardless of which command you use to put*.willyw wrote:Yes, it did make a difference. But only for the first 5 lines of output.
They came up very quickly. Much nicer.
But the remaining lines came up same as before - Line-by-line with a little pause between each.
Any ideas as to what is causing this?
I don't think I understand you.(but will definitely get your eggdrop excess flooded every now and then).
willyw wrote:But, can you elaborate on this, please:I don't think I understand you.(but will definitely get your eggdrop excess flooded every now and then).
It can't be that eggdrop will censure itself for "flooding". So you must mean something to do with the IRCD?
Is that it?
Somewhere along the lines of this. This depends on the amount of lines displayed and the number of users triggering it at once. Combined this might cause the ircd to terminate your connection rather than handle it by throttling your messages as some servers do. This may/or may not happen to you. I've just mentioned it so your fully aware of it.*** Quits: YourBot (~ident@your.bots.mask.com) (Quits: Excess Flood)
Reading between the lines... let me see if I've got this right, when I say:speechles wrote: ...
But without it, your going to need to adjust your ignore times and flood settings to be able to keep your bot from getting killed all the time.
This is interesting, because we tried something almost like this already today - after reading the comments above, about flooding etc.incith wrote:you can test this on your own client for example.. try spamming 10 - 12 lines in a row really fast (uparrow + enter), and perhaps watch the output on another IRC client. You may get disconnected from the server, or, your output will start getting queued. I don't think it's really something that can be avoided.
I'm a little confused then...incith wrote:... not sure why it happened on /msg.
I wasn't really watching him that time.. but we'll do it again and see.Basically for the test I mean, have your friend send the 12 or whatnot !weathers, and just watch him, he should start lagging to you in the same way the bot does, after his first 5 or so !weathers sent to the channel, they should start getting queued a bit by his client, theoretically.