Forums Bug Reports $scon or $cid bug?

Using mIRC 6.14 on XP Pro
Not sure if this is a mIRC bug or lack of understanding on my part.

I am on 2 irc servers, and when i set away i get " * No such connection id: 2"

The aim is to cycle through the current connections and set away on each, but



the first connection is rightly mumbered 1


Now if i switch to the only other connection, it says 3?


Since i have not been on a 3rd connection since starting mIRC i'd expect the 2nd connection to be 2 not 3?

Anyone know of a way to handle this? I cant loop for 1 to $scon(0) as that tries to switch to connection 2 which doesnt exist, instead of connection 3

Maybe try looping and on each loop check if $scid(loop #) is $null?

I realize that, in theory that shouldn't be possible, but then again, in theory, if you only have two sessions going, then they should be numbered 1 & 2, not 1 & 3.

You should always try things on the latest version of mIRC before reporting a bug since the bug you're reporting may of already been fixed.
$cid rightly returns 2 on my second connection in 6.16.

mIRC has the functionality you're looking for built-in:

/loopservers
Number of servers 2
Server number 1's cid is 1
Server number 2's cid is 4


Were u using /SCID to change servers?
Using /SCID N to change to a specific server should only really be used when you already know the $cid of that server since $cid is the N value.

If your wanting to loop through each server use /SCON N it uses 1 to N for the server numbers, the $cid's well be set according to each connection, in my case the cids were 1 then 4.
Note. I had just started mirc, so i assume the $cid value is not always dependent on server connection order etc, but rather is a unique Conection IDentification number.

CIDs are just numbers that uniquely identify a session. They were never designed to be sequential, with no gaps among them. The only rule they must follow is that each session must have its own, unique CID. In reality, when you start up mirc, the Status window is assigned the CID 1. If you open a second Status, it gets the CID 2. If you then close that Status and open another one (so that the new one will be the second in list), it gets the CID 3 (as if mirc remembers how many Status windows have ever been opened). So in the above example, you end up with two Status windows, the one having CID 1 and the other CID 3.

It's now obvious that you can't loop through CIDs by incrementing a variable %i and using it for the CID. This is why $scon() and /scon were introduced. $scon(N) returns the CID for the Nth connection (that CID may very well be a number other than N). /scon N command performs the command on the Nth session, while /scid N command performs the command on the session with CID N.

So there are 2 ways to loop through all connections and do something on them. Either by incrementing a variable and passing it to /scon:

or by incrementing a variable, passing it to $scon(), then passing $scon() to /scid: