Forums Feature Suggestions 'backlog' from server to client on:join

You have just started colapsing your script down, Now it only deals with one channel, and that can be flooded off, the bot well not respond quick enough with the 25 lines if a single/multiple requests made, you may have the /WRITE Delete line mirc bug after 65000 or so delete writes, you not capturing actions to the channel, and people should have to see others going !backlog either. And of course the fact that there has to be a client script to make it work correctly.

Now im not expecting you to correct all that, im just trying to point out that, it would never be just a "simple mirc script"

Another aproach might be to simply write a client/server script, where say your running it, your in a channel called #backlogs (all the time), you enter the channel you want to be in lets say #BLAH, you right click and select the added menu option for #BLAH called "backlog", in #backlogs your client says "!backlog #BLAH", any one in there whos in #BLAH, can/does now PM your client with a message such as "~~~ BACKLOG HERE ~~~" this is never seen by you as the script processes it, first person to PM it is sent a reply "~~~ BACKLOG REQUEST ~~~", and his script PM's or better yet DCC's you the backlog. Protections can be arranged to ignore bulk requests and or requests after someone is already in the channel for some time or not in the channel at all of a !backlog <channel> request.

This would leave the channels transparent to backloging script. And mean that no one is relyiong on any one bot for there backlog, as long as one other user of the script was in the channel, you can still get a backlog.