2 onjoins in same remote file

hi guys again

if I have two onjoins in same remote file such as:

on *:join:*:{ blah blah }

on *:join:*:{ blah2 blah2 }

sure both do not work without using on ^*:join:*:{ .......

but my question is: should I use ^ for the two of them or only one or what?

You dont need those

on *:JOIN: will work fine.

er why not just put both commands in one onjoin.. just use some if's and then's and throw a var or 2 in just in case.

Gotta luv vars

Down with hash tables VARS VARS VARS

ozzy quit looking at me like that and LEAVE MY DAM VARS ALONE YOU GIT.

but i don't want to mix both err0r for some reasons lol and fussy both did not work but when I move one of them to another remote so both work well.

this means both in same remote never work

That doesnt mean its the onjoin command. Its probably what you have after the onjoin.

putting two seperate on joins in one remote file is a bad idea.

Either combine the two in one onjoin or put them in seperate files.

You could always do it this way too. I have a remote file with several onjoins in it. I just didnt close the {} till very end of file. All of them work just fine. I'll post an example.

on ^1:join:#:{ 
 if (slut isin $nick) { /access # add deny # $nick | /kick $chan $nick You Are Not Needed Here thanks. Try elsewhere :)  | /auser autok $nick 
 }

 on ^1:join:#:{ 
   if (cd isin $nick) { /access # add deny # $nick | /kick $chan $nick You Are Not Needed Here thanks. Try a GAY room :)  | /auser autok $nick 
   }

   on ^1:join:#:{ 
     if (pimp isin $nick) { /access # add deny # $nick | /kick $chan $nick You Are Not Needed Here thanks. Try elsewhere :)  | /auser autok $nick 
     }
  }
}

No sooner than i posted this someone came in with pimp in his name lol. Seeing how pimp is the third onjoin event i'll post an example of the kick.

Host ¿ΜЯ»«ΆÅ Å ЊÃ˜Â£Ξ¿1 kicked pimpininkc out of the chat room: You Are Not Needed Here thanks. Try elsewhere

what does 1 mean in this onjoin command? I really want to know what is the difference between:

on ^*:join:

on @:join:

on 1:join:

what does 1 mean in this onjoin command? I really want to know what is the difference between:

 

on ^*:join:

on @:join:

on 1:join:

if i remember corectly

^ acts like a switch if used ignores normal mirc functions

@ will triger only if you are an op

* means everyone

+ is for that level and that level alone

and the numbers are representitive of userlevels, mirc is set up with userlevels on a numerical order to make the code flow ezier as well as asign multiple levels to a single code, 1 is the default level, but if you had like on 5:join: it would worl for levels 1,2,3,4, AND 5.

lmao err0r, you still havent changed.

I'm agreeing with err0r here though on the if-then-else choices.

Set it like

on *:JOIN:#:{

if ($level($nick) == Admin) { msg $chan Welcome Admin $nick }

elseif ($level($nick) == Remote) { msg $chan Welcome $nick $+ , you have Remote Access. }

elseif ($level($nick) == Kicklist) { access $chan add deny $nick 60 :Kicklist | kick $chan $nick Kicklisted }

}

Its also a little quicker at times using just a single on join statement for multiple things that are mostly the same.

Ignore err0r on the variables though

Edit: Its been awhile since I've used /access, so I might have it backwords between the mask and time

Also edit: Mail, wouldn't that cause a 'ON is not a valid command' styled error? ;\ It always did when I screwed up brackets..

on *:join:

Can allow any user to trigger an event regardless of their access level

on @:join:

Can limit events to being executed only when you have Ops on a channel

on 1:join:

The default access level is 1 for users that are not listed in the Users list.

All users can access level 1 events.

on ^*:join:

Triggers before mIRC sends the standard messages etc

eg b4 an

on *:join: event

No antics not really. There are 6 on join events in that remote and i never have a problem with it. If you click the bracket checker then it says its wrong. I just dont click it and close the file. Seems like it would cause an error but it doesnt for me. For some reason it checks the whole remote file and kicks appropriately.

Hmm.

I guess my mirc just hates me then huh?