You have mismatched brackets.
The second closing bracket before on 8:JOIN should be moved to the very end of the on JOIN section.
Also, you do realize that you've only scripted for users level 8 and above, with and without the [LC] in their nick?
This responds to everyone who joins #lc who has a User Level of 8 or higherThis section deals with those who also have [LC] in their nick if ( [LC] isin $nick) {
inc %clanjoins 1
describe $chan Welcome back to the clan room $nick you are member %clanjoins to return
mode $chan +h $nick
}
This section reacts to those who don't have [LC] in their nick, but only if they are still level 8 or higher else {
inc %joins 1
describe $chan Welcome to $chan $nick hope you enjoy you're stay here btw your number %joins to happen in here.
mode $chan +v $nick
}
}
To respond to ppl who join who have a level lower than 8, or who are not in your User List at all, you need a separate on JOIN event:
on *:JOIN:#whatever: {
do stuff
}
You switched from #mol to #lc, so YOU figure it out You can have as many on Join events as you have levels, plus one (to catch all the non-listed users). The trick is to keep track of which level gets what,
and what level do you want to assign to whom. For example, for reasons I can no longer remember, I assigned users to one of eight levels.
So far I have only coded events for 4 of those levels, and for the * level (everyone else).
Having just re-read for the umpteenth time the paragraph 'Order of Definitions' in the help file, at the bottom of the 'Access Levels' page,
I finally get what he is saying. The suggested order is for the scripter to keep track.
I thought he was referring to the order that the events should appear in a script, and personally found it more logical to place them higher to lower.
It seems that the order of on JOIN events in a script does not matter to mIRC, whereas the order of on TEXT events in a script is crucial.
If anyone knows different, please disabuse me of this notion ASAP.