Connection IDs aren't simply a matter of no two connections having the same ID at the same time, if this is all you need then you can use $scon(n) as previously suggested. No, the point of a connection ID is that for as long as mIRC is open each connection's ID always remains the same. Connection IDs are used in multi-server-spanning scripts to uniquely identify what parameters/options/variables/whatever are attached to which connection. If the connection IDs are then all reset/reordered then those stored parameters/options/variables/whatever are all referring to the wrong connections. Seeing as this is the point of having connection IDs I simply can't understand why people are suggesting this 'feature', and from the looks of it, neither can you.


Spelling mistakes, grammatical errors, and stupid comments are intentional.