Find discussions and posts across the Forum sections you are allowed to read.
Filter by Forum, author, date, content scope and sort order without exposing restricted discussions.
here molson
try hop $chan also, the built-in deowner protection works and it's a lot faster than that would be.
that alias is intended strictly for internal use. i have tinkered with it in the upcoming version 6.0.2 tho, and you might have better luck with that file.
maybe safer, but not as sexy. lol
uh oh, err0r. he's got you there. i'm not sure i know what he's talking about but he used lots of CAPS and exclamation points. so he must be right.
by the way.. the reason the signal feature is in there is so you can write your own separate addons without editing the connection file itself. you can write a signal event in a separate remote script file. also, use the signal event...
thats why its better to put it in the connection itself.. you dont have to flood the server with unnecesary ping replies because it tells you if somebody's a nonsubscriber when they join...
on *:text:*:#:{ tokenize 32 $strip($1-) if ((http isin $1-) || (*www.*.???* iswm $1-)) && ($nick !isop $chan) { access $chan add deny $address 0 :dont post that crap :) | kick $chan $nick no links d00d } } maybe
gatekeeper's code will work, but you have to do /who $chan when you first go into the room, or any time before actually using the command.
thats why they have links to pages 2,3,4.. etc
when you send a /raw command you're sending it the same way you would send a sockwrite command. a sockwrite kick command looks like KICK <channel> <nick> :reason here note the : right before the reason. without that : it will only accept...
you can use $msn.roompass($chan) or $msn.chan($chan).key //pass $msn.roompass($chan) //mode $me +h $msn.roompass($chan)
right click on the window's switchbar button and choose 'nicklist' and then "off" in the dropdown box .. and "set as default for all channels" if you dont want a nicklist in any room.
no it isn't as of yet. but im working on a minor update that will allow you to use gatekeeper in it. the currently available version doesn't do it.
using my new connection (nüclearmsn) you can chat on msn in linux, as long as you're running mIRC with WINE. no need for the ocx or to even have IE installed at all. only bug reported with it on linux is a minor glitch in the room lister.
ozzy i think i will remove clone, and since the updaters work well, i think i will force users to use the msnregcookies in chats, that way they can only use the nickname they're registered with. as for adding it in from previous versions...
on ^*:PART:#:{ echo 14 $chan $replace($msn.decode($nick),>,Guest_) (*! $+ $address $+ ) has left the conversation. if ($window($nick)) echo 14 $ifmatch $replace($msn.decode($nick),>,Guest_) (*! $+ $address $+ ) has left the conversation. }
what jesse suggested will work but he forgot something important... $1 in the sockread is not just the nickname, but the : in front of the nickname and the gatekeeper address too. change the first part of the code to if ($len($1) > 8...
ya, you basically have to write an msn connection in order to do it. so its best to go with a connection that can already do it.
i thought he was changing it in the join/part sockreads. i guess hes changing in the theme.
msn doesn't really care. it isn't technically against the TOS, the TOS only says msn will not provide support for 3rd party clients. it isn't against the rules to use them, you just cant bug msn staff with questions about them. but msn w...
hey cleric, release it before i get done with NuClear so i can accidentally rip it. .. okay here's another ss - passport manager and access dialog passports are easier to deal with now, and since the updaters work without any problem...
where did you get dcx.dll?
you can also stick with the code you were using in vincula, and in the ClearMSN control panel, go to the Font tab and un-check the box at the top so ClearMSN won't format your messages with its font controls. your other code will do the...
