if you join one of these channels it closes all the channels and does god only knows what

<Patient> Doc .. it hurts when I do this ..
* Patient moves his arm
<Doctor> Then don't do that .. $50 please

Please see here

if it's not a bug, then why is it that it does that on everyone network i join, including dal.net, efnet, quake, and my network. all with different IRCD's.

Many moons ago, when IRC was still a hairy, smelly scruff of a chat medium (unlike it's relativly clean-cut, fresh smelling decendent), joining channel #0 was the way to exit all channels you were in. It is the intentional behaviour of mIRC to do this also

Someone once told me that this is a bug that sends all your serial keys to Khaled or some elite hacking group lol, of course i know that's probably bs, but still i'd like to know why it does this?

Actually .. it's the server that parts you from all
channels when you join that .. not mIRC itself.

Yes, that is 'BS'. All it does is make mIRC (and any other standards-complient IRC client) exit all channels.

Even so, the end result is the same :P

Ok I am a network owner, how can i prevent this from happening to my users? could i forbid the channels? also when i installed my server it had the nick Status forbidden, it says Bug in mIRC? any light on that subject?

Sorry, I can't help you with that. I've never set-up/configured an IRCD before. Someone else may be able to help you tho

make a channel lock in the config.. "you lock all channels beggin with 0 unvalid ones".. that means that people cant join them, its like som network have lock on abusive channels.. rasistic ones, and also som porno channels..

if you do /join 0 you will part all channels...

So it has nothing to do with channel locks either seeing how "0" is not a valid channel name. Also, seeing how comma's cant be used in a channel name either doesnt help. the only reason you part all channels on /join #100,000 is because to the server you are joining channel #100 and then after the comma it sees 000 which is 0, so it thinks it wants you to part all channels, so that is what it does.

And with what naki said in mind, it is conceivable that you can find the "partall" code in your IRCd of choice. This is, however, standard behavior and should be left alone. It is conceivable that some clients expect this behavior and use and rely upon it to function correctly.

- Raccoon

I'm actually wondering why Khaled has it join the listed channels, not not seperate it. I mean as Raccoon said, a comma is only a delimiter, and not a valid character and realistically should not be included in mirc's join (just as a period, parentesis, etc isn't). That's just my $0.02.

Because it is on the IRC protocol level, to join a list of comma delimited channels instead of several separated JOIN commands. mIRC is doing what it should.

I wish mIRC further honored this by consolidating re-connect re-joins into a single JOIN command.

I'm not questioning mIRC's method of joining several channels, just its method of a join per double-click. When you click on a channel in a sentance, you join one at a time. I am saying that channels listed in delimited form should also take on this property of joining the one you click, instead of those prefixing and herafter.

It does to an extent. If you click on "#somechan,0" or "#somechan,#another" you will only join #somechan.

Well if it doesn't work all the time, couldn't this be classified a bug?

About the Status stuff, it's probably due to the fact that many scripts halt the ON INPUT event and/or customize the /say command, forgetting to check if $active is "Status Window" - so, using "/say blah" when status is the active window would make it call "/msg Status Window blah", sending "Window blah" to anyone with the nick "status".
In this case, it isn't a mIRC bug.. it's the scripter's fault instead.

When doesn't it work? I've never found myself in such situation..

It works that way all the time here.

According to RFC 2812, IRC servers are supposed to interpret joining 0 (not #0) as parting all channels. This is not a client feature, which can be seen by looking at mIRC's debug output; mIRC doesn't send a part message, it sends "JOIN 0". Commas separate channel names in a join message, so the second channel name in JOIN #1,000 is 000.

so why not fix it then?

There.. Is.. Nothing.. To.. Fix...

The... observed... behavior... is... intended...

People..... need..... to..... read..... harder.....

I was actually basis that post off what Iori said. The fact that clicking on the #1,0 will join 0 also, just $comechan,0 will join #somechan. I was testing it out, and the only reason it works is because most users tend to click a link in the cente. Being there is a 0 in the center of the link, it joins the 000 side fo the comma. (#1,000)

Well it doesn't join 0 also.. actually here it doesn't join any other channel than the first one specified.

It doesn't.
It ALWAYS joins the first channel listed (based on the comma as delimiter) just as I said, and as you quoted,
If you click on #1,0 you will join #1, if you click on #1,000 you will join #1 - no matter where on the string you click.

NEVER will mIRC join "000" from a double click, unless you have scripted #channel hotlinks, in which case it is not mIRCs fault.