My Connection

First and foremost I would like to credit Chuck for his time and patience in helping answer my questions about the Buzzen server.

PLEASE USE THE MOST CURRENT VERSION OF MIRC WHEN RUNNING MY CONNECTION!

I cannot stress this enough. I have had several people complain to me that they could not get the connection to work.

Only to realize later that they were using mIRC 6.2x and there were some issues with sockets.

The current version is 6.31 as of today. It is fully Vista compatible and a sharp new look!

------------------------------------------------------------------------------------------------------------------------------

I had mentioned in a previous post that I would post this so here is my connection to buzzen as of right now.

This connection uses the ChatDrive protocol not the standard IRCx

New Thread

good work tewl thanks for posting it.

* Update - bug

I noticed a problem earlier where admin acounts were not sending the profile string so incorrect data format was being sent to the localhost which caused users not to appear in the channel. I changed the JOIN clause to fix this issue. With that in mind this connection can work using either IRCx and ChatDrive protocol. the ChatDriveProtocol is still set on connect "CLIENTMODE cd1" if you wish to change to IRCx just type "CLIENTMODE cd2" or remove the "CLIENTMODE cd1" from the buzzen socket open event before connecting.

About ircop account flag, it has not been implemented yet, but soon in an upcoming update server will switch to that instead of ^. What I've done to keep it compatible with the updates in my client is to check the length of the flags string, if it is 4 then it ignores the account flag, if it is 5 then last char is used for the account type. I'm tokenizing the irc messages by space, so this method works best for me.

btw, good work

uhm thats usless

i sniffed there server and this is what i got

ISFLASHSOCKET

.AUTHTYPE ircwx1

.NICK >Guest

.USER anon "anon.com" "0.0.0.0" :anon

.

:FlashIrcServer.1 NOTICE AUTH :*** IRCwx 1.x auth type set..

:FlashIrcServer.1 433 * >Guest :Nickname is already in use.

NICK >Guest7236

.

:FlashIrcServer.1 AUTHUSER.

CREATE %#!!!!!!!!!!!!!!test

.

:FlashIrcServer.1 451 :You have not registered.

UTICKET <removed by X-Fusion; advice from Chuck>

.CLIENTMODE cd1

so all u have to do is

/server irc.buzzen.ne

it will connect u as a guest

then

/UTICKET then ur ticket

so baiscly u dont need to write a conn ... just get the ticket

"so baiscly u dont need to write a conn ... just get the ticket"

That depends what you are doing. Standard mirc connection won't parse listview correctly under CLIENTMODE cd1. But you don't need to write a connection if you are not using cd1 mode.

btw, don't post uticket info. If above is the correct one then change your password now.

Removed.

You can connect to BuzzenV2 through mIRC with two lines.

server -m irc.buzzen.net 6667

raw loginh <email> $md5(Password)

then join a room.

You can do this, but a true connection is a whole lot more than simply connecting you to a server.

Stripping fonts and formatting your text.

Allowing you to add/remove accounts and change to them with a click.

Changing your font color and style with a few clicks.

Room List

etc.

You can connect to BuzzenV2 through mIRC with two lines.

 

server -m irc.buzzen.net 667

raw loginh <email> $md5(Password)

then join a room.

You can do this, but a true connection is a whole lot more than simply connecting you to a server.

 

Stripping fonts and formatting your text.

Allowing you to add/remove accounts and change to them with a click.

Changing your font color and style with a few clicks.

Room List

etc.

you can also do it this way

/server irc.buzzen.net 6667 then /login [email protected] passhere

btw nice work Tewl

Thanks for replying everyone

Made a couple changes for error handling. Also changed the regex again, this one seems to work very well. I have been considering posting the entire script for download but I do not have the "features" most users desire. No dialogs or eyecandy addons and limited menu support, BUT my theme is hawt, lol. Ya it's the same theme I used on my last msn script (since it basically just is my msn script altered for buzzen).

http://www.tewlzbox.com/script.png

cool

* Update

Fixed issue where channel would not open if not using chatdrive or when logging in using an admin account.

Added alias login to make it easier for users to connect using a different account. If you use this command it will disconnect you. I may later add switch support if users wish to run different accounts in the same clients (ie multiserver).

I do occassionally notice errors with the style parser not removing tags when you first joining a room. Generally this is when people send messages as soon as you join which include a lot of style tags such as fadders.

I am giving my script out to a few people to use and maybe notice some bugs. When I am certain it is stable enough that I wont embarrass myself releasing it I will post it onmy website for download. When I do post it please do not post it or submit it to any website for download without my consent.

For someone who doesn't script anymore I seem to be doing a lot of it lately -.-;

On a side note...

I have also been working on an IRC client in C# and have been considering creating some type of client (not a mIRC script) for buzzen as well. I do not have a great deal of time to work on these things though, so if anyone would be interested in working together on something like this I would be more than welcome work something out. I do ask however that only serious programmers contact me about this not users just starting out learning. Oh... this doesn't have to be in C#, I can write applications in VB 6 and .Net (2005) as well.

*Update

Added support to handle multiple room joining. /join %#room1,%#room2,%#room3 ect...

This also fixes issue where rooms would not be rejoined after reconnect.

I noticed a problem today that some of you might remember from msn where nicknames in mIRC would be truncated(shortened) because they were too long. This is very annoying to say the least so I have posted on the mIRC forums hoping for a better solution than the one I have. If no can be found the only way to have a properly working connection will be to handle ALL events through the socket instead of the mIRC ON events.

You can view the thread here.

I think the only solution I could see would be to do it through a socket event. Now that mIRC supports unicode characters and UTF-8, it would be very difficult to do it otherwise, especially a long nickname that's unicode. I think monitoring it through ON events may be suseptible to mIRC getting confused. Not only that, if someone comes in with a host of long names, they could easily flood your stuff out using ON events.

I think in the end I will have to come up with a hash table system for both channels and nicknames in the socket connection.

yep, that was how connections like NuClear and DogCollar got around that issue. Even though mIRC now supports UTF-8, it still is restricted to the 50 character condition (unicode). Hash table is the best as it would allow for quick access to the information. You would just need to record the details when they join the room, and for every event, just retreive the correct details when an action is performed, just prior to the sockwrite.

I'm sure you know how to do it tewl, but if you need a hand, i would be happy to help as i do remember some of the things i did when i made DogCollar for GuarDDog, so i should be able to assist with any of the information handling and socket handling/writing. The offers there, but like i said, i think you are more than capable .

I know how to do it, I just don't want to do it for many reasons. For one, the displayed name will not be accurate mainly. I could use the hash table to display the proper unicode of a nickname but that would take away from the functionality of clicking nicknames in the channel or figuring out which nick in the nicklist belongs to the displayed name. Secondly, no matter how fast hash tables are they are still add lag to the processing speed. True in rooms that have 10 or so people you may not notice this but when its 20, 30, or even 40 it gets nasty processing the 353. You can still run into nickname collisions if 2 people with very similair names join a room and are both cut off, this would also apply to channel names. The only true and stable solution will be to increase the length for channels and nicknames in the client itself

* Update

Added ability to turn on or off the sockread (debug) window. Simply type "/sread on" to turn it on or "/sread off" to turn it off.

Altered NOTICE data. Buzzen sends notices like this: "NOTICE <channel> <nickname> :message" the proper way to send a notice would be "NOTICE <channel or nickname> :message" due to the improper format mIRC was not displaying entire NOTICES so I removed the nickname from the incoming data as well as altered outgoing messages that they are in the proper format for buzzen. If Buzzen decides to change it to follow the standard I will remove these changes but for now they are for your benefit.

Additional: I have still not got a reply from Khaled about increasing the length for channels and nicknames. If it turns out he has no intention of doing so I will most likely discontinue working on the script. Even when using hash tables to back reference there are still way too many possible errors that could happen to invest in making this a stable project.