Forums Feature Suggestions Auto connect

I want an easy auto connect feature.
So I can add some servers.

That's what scripts are for.



Then, you can always add in channels to join and such on those /server lines. For information on how to do that, use /help /server .

I disagree. Wanting to have mIRC start with multiple status windows (and possibly auto-connecting to them and auto-joining network-specific channels) seems like a really basic feature now that mIRC has multi-server support.

Scripting is of course capable of doing it, but it seems like such a fundamental feature for a multi-server IRC client that IMO you shouldn't need to resort to scripting for this.

I'm not saying it's a bad thing. Just that scripting it is easy. Also, if it were added to mIRC, how complex are we going to make the options dialog? I mean, if you just add enough to join the networks and nothing else, people will be complaining that they don't have options to change nicks, idents, etc in there. If you start adding everything, it's just going to get too complex. I'd rather keep the options dialog simple and let scripts handle something like this instead. That's just my opinion on it, of course.

Why are you putting what was already given?

lol

there is a way in the options menu...
you goto the preform on start place and type it in

Heh... that won't work well when pinging out.

lol :P

I suggested that before too.

A "Connect on Startup" box in the edit window for each server. The same as there's already a "join on connect" for channels.

It's a multi server client now, but it still only has the abiltity to automatically join a single server.

(yes, you can do that with scripts, but scripting is hardly something novice users should need to learn.)

Actually...

What would probably work better and be much more user friendly would be multiple connect dialogs.

Go to options and connect and find a list of connections with, add, edit and delete boxes.

When you add or edit a connection, you get something similar to to the connect dial with full name, email address, nickname, alternative, invisable.

What would also make things simpler would be to have all the server settings on that same page: Server description, address, ports, network name, password and a button to let you browse the server list to choose one instead of just typing the info.

And *then* a check box for connect on startup.

And then also a button to open the perform box for that connection.

You might use a different nick and password on different servers, and you might need to perform different commands when you connect to different servers.

I use mIRC a lot to help people get people connect to my IRC channel and it would be a lot easier for me if I could guide them to one dialog box to enter all the connection settings rather than going to the connect dialog for user info, the server browser to add and select a network and server and the channels folder to add the channel, select the network it's on and make it join on[/b] connect.

As per letting you still use "irc:" urls correcty, you could have a default first connection where you take the user info from for those links.

Seems like a big project to impliment, but after adding multiple server capability, it's probably not a bad idea to go over the interface with multiple servers in mind from the beginning rather than adding the functionality on top of a single server interface.