Forums Bug Reports idle time & away message

I've searched and haven't found anything related to what is happening here.

Recently I have noticed that on occassion while being marked as away, my own away message shows up in my status window.

example: Time4aHoliday is away: bbiab ...

Also while I have been away for quite some time, after the above happens my idle time gets reset back to 0 (zero) seconds.

I am using mIRC 6.12 and when the above instances have happened, haven't been using an anti-idle script.

Has any one else had this happen or know why it's happening?

Not sure if this is a mIRC bug or an ircd bug on DALnet or something else perhaps?

are you sure you aren't running an anti idle script or a lag/ping script?

use /debug -p @debug to see exactly what you're sending to the server.

nope, no anti-idle script running nor a lag/ping script.

I wrote my own script so I know exactly was is running and what isn't

Keep a debug window open and see if the server is sending you the text, if it is contact the IRCd writers.

Well I had a @debug window open to see what was going on, only problem is when I went to save it after it happened again, it only saved the last few lines in the @debug window. I closed the @debug window to open the log so lost what was onscreen.

A pity the @debug window doesn't have a 'save buffer' button.

From what glimpse I saw was happening, it may be some sort of flood protection, even though I wasn't flooded or was flooding.

So now I have a @debug window logging everything til it happens again .. who knows if and when that will happen, could be hours before it does lol .. then I'll paste here what shows up.

to save the @debug window isnt that hard

/filter -wf @debug filename.txt *

Ok I finally got it logged! Although this instance happened after a netsplit rejoined, it didn't happen in prior times.

[11:12] -> mesra.kl.my.dal.net PRIVMSG moet :FLOODCHECK
[11:12] <- :mesra.kl.my.dal.net 301 moet moet :testing something ..
[11:12] <- :moet!zebra@218-101-96-20.dialup.clear.net.nz PRIVMSG moet :FLOODCHECK

I do, however, an on join /whois of most nicks to check for bad channels and real name fields of regular spam bots. Maybe this is what is causing this to happen? Is there any way to lessen the flooding?

I wonder if it was possible to put in a /whois server .. something similiar along the lines of the ctcp finger server, so it helps minimize the flooding and be able to select which channel(s) to use it on.

The floodcheck script you are running is sending a message to yourself. When you send a message to anyone who is away the server tells you they are away, that is why the message is showing.

ok thanks Collective ... but ... I'm not running a self-checking flood script. Only flood script I have is for channel/action/notice text flooding.

Well this clearly shows that you are messaging yourself the text "FLOODCHECK".

[11:12] <- :moet!zebra@218-101-96-20.dialup.clear.net.nz PRIVMSG moet :FLOODCHECK

From moet
To moet

Well then I am totally stumped as to why it's happening then. I have checked every single script running here and NONE mention 'floodcheck' in them.

The only script I'm not really sure about is one I got off the board here about detecting people who try that DCC exploit. I added that after a person from a known flooding group on DALnet tried the DCC exploit on me.

Well, this could be the server forcing the event. I've seen this "FLOODCHECK" thing before, although it's rare in the network I hang on, so I don't remember the behaviour.

If you have a look at the lines from the debug window you can clearly see the line sent to the server then the server sending the 301 reply then the message that was sent and who sent it.

line sent to server and with who it was for
[11:12] -> mesra.kl.my.dal.net PRIVMSG moet :FLOODCHECK
301 reply
[11:12] <- :mesra.kl.my.dal.net 301 moet moet :testing something ..
message returning
[11:12] <- :moet!zebra@218-101-96-20.dialup.clear.net.nz PRIVMSG moet :FLOODCHECK

Thats somthing in mirc.. i had the same problem, the only way i could solve it was to disable mirc's own flood protrection, try that and see if it helps..

Indeed, very interesting. Upon a quick examination of mirc.exe, the phrase "FLOODCHECK" appears twice in the file. So without a doubt, it's a built-in function of mIRC. I really didn't know mIRC was smart enough to check for throttling.

On a side note, try sending yourself this same message...
//msg $me FLOODCHECK
No message will appear, no TEXT events are fired. This only happens when sent to yourself, but appears normally when sent to/from other people.

If I might make a suggestion to Mr Khaled: Instead of sending this throttle detection packet via PRIVMSG, simply send a /raw FLOODCHECK and watch for the 421:Unknown Command response. This is universally compatible on all IRCDs, will not mess up one's idle time, and cannot be blocked by server-side ignore features (eg: +g).

- Raccoon

True! That's when I caught this message.. when I had the flood protection enabled. Indeed it's a mIRC feature.