Need some IRC help!

[Marv]

Hello all!

I am new to an alliance and I need to be on the netgamers server and the alliance server..

this causes some problems for when my perform list runs when I join each one, naturally I have 2 separate list of perform functions.

So...Can anyone offer any simple suggestions on how to put in a simple script for me to have the servers run independant.

Thanks for any help anyone can offer!

Marv

[furball]

Lo marv

I always use two separate mIRC programmes myself...one for private servers, one for netgamers.


furball

[Phil^]

the $network and $server identifiers , along with the if statement in mirc script are your friends here

for example

on *:connect:{
if ( $network = Netgamers ) {
do netgamers stuff
}
if ( $server = irc.myalliance.whatever ) {
do alliance stuff
}
}


add if statements for as many servers/networks as you want

if you want mirc to autoconnect to the servers when you start it then :

on *:start:{
server irc.netgamers.org
server -m irc.allianceserver.whatever
}

[Marv]

were do i put this script? in the aliases bit or what??

[Phil^]

remotes, alt-r

[A2]

If you've got a new(ish) copy of mIRC then you'll find that it's possible to specify a separate perform list for each one. Just change the dropdown box on the perform screen to each network name, as opposed to "all networks"
You may have to use the "add networks" button in order to get the ones you want to show up there.

[Marv]

ok so i did it...but nothing happens...i set it to auto connect on irc start up...

im such a noob at this...

[Phil^]

the on start script triggers when mirc is started. the on connect script triggers when mirc connects to a server

it wont do anything unless these events happen

also, check status screen for any error messages, incase any additions youve done to the script have broken it


where it says " do netgamers stuff" and " do alliance stuff" you obviously replace this with "join #channel" and so on

[mist]

i was under the impression that $network and $server are set server side, meaning that there's a danger with this kind of script that should you join another network they'll be able to milk your details from you.

for example, were your alliance to set their server to say it were on netgamers, they could get your P user/pass. while this isn't particularly a problem, were someone to 'persuade' you to join a different network they could easilly harvest your login/pass for both netgamers and your alliance network

i believe there were a few incidences of this problem a while back, involving P nicks stolen in this way

-mist

[Phil^]

$network is defined by the server you`re connecting to yes, but $server always returns the server you are connected to
$network is just handy when connecting to netgamers unless you want to specify one server only to connect to and do things for that server only.
ofc if/when it dies you`re in trouble

you COULD do it ( if you`re paranoid ) so that it goes like :

if (( $network = Netgamers ) && ( *.netgamers.org iswm $server )) {

that`d be pretty ok to ensure you were on ng only with it

[mist]

* Dns resolved london.uk.eu.netgamers.org to 195.149.21.43
* Dns resolved 195.149.21.43 to administrator.jolt.co.uk

if $server isn't also set by the server, what's it set by?

-mist

[Jonas]

just /server -m irc.theserverinquestion.com ? works for me