mIRC Home    About    Download    Register    News    Help

Print Thread
#85888 08/06/04 02:43 AM
N
Norbertka
Norbertka
N
HY!

MiRC 6.15 is crashed to join the special room.
(Color Code, on the room name, and Crashed the MiRC )

#85889 08/06/04 05:05 AM
Z
zaz
zaz
Z
What network allows the use of color codes in the channel name? It should be an illegal character.

#85890 08/06/04 09:10 AM
Joined: Jun 2003
Posts: 4,670
M
Hoopy frood
Offline
Hoopy frood
M
Joined: Jun 2003
Posts: 4,670
Indeed, colour codes in a channel should not work if the network follows protocol (afaik). If I try and join a channel with a colour code in, I simply get the server returning the error "test Channel name contains illegal characters"

Therefore, cannot confirm, 6.15/XP Pro.

Regards,

#85891 08/06/04 09:58 AM
Joined: Dec 2002
Posts: 2,958
W
Hoopy frood
Offline
Hoopy frood
W
Joined: Dec 2002
Posts: 2,958
There seems to be quite a few different ways that servers handle it. Some block the characters completely, some accept the first part of the channel name (ie the letters before the codes) and some allow the full name including the codes.

#85892 08/06/04 10:06 AM
L
LifeIsPain
LifeIsPain
L
Nope, per the updated RFC (2812 for client, as this is what I look at the most), you have the following lines:

chanstring = %x01-07 / %x08-09 / %x0B-0C / %x0E-1F / %x21-2B
chanstring =/ %x2D-39 / %x3B-FF
; any octet except NUL, BELL, CR, LF, " ", "," and ":"

As long as the channel starts with "#", "+", or "&", and doesn't contain those characters mentioned, you shouldn't have a problem (with most networks only likeing the "#")

Anyway, just did /join #06all_your_base and was fine, so I for me, the bug didn't happen.

But not all networks may like it, but they are valid codes.

#85893 08/06/04 03:04 PM
Joined: Apr 2003
Posts: 701
K
Hoopy frood
Offline
Hoopy frood
K
Joined: Apr 2003
Posts: 701
//join #a $+ $chr(3) $+ 4red $+ $chr(2) $+ bold $+ $chr(15) $+ normal $+ $chr(35) $+ $chr(22) $+ reverse $+ $chr(9) $+ tab $+ $chr(1)

Works perfectly here (mIRC 6.15, WinXP). The last $chr(1) gives an extra line saying log file cannot be opened, I call that a feature for testing channel stuff that I don't want logged grin
Iirc earlier mIRC versions also couldn't open log files for channels containing a tab ($chr(9) or ctrl-i).

Maybe you have a script loaded that parses this incorrectly. Do you have the same problem with a copletely clean mIRC?

#85894 08/06/04 03:10 PM
Joined: Jul 2003
Posts: 733
M
Hoopy frood
Offline
Hoopy frood
M
Joined: Jul 2003
Posts: 733
lifeispain: my network (UNREALIRCD 3.2 Win32) just joined '#'

kelder: my network joined '#a'

i guess its just the IRCD that lets/doesnt let stuff hapen


Link Copied to Clipboard