Forums Feature Suggestions on *:SERVOUT:*:

I think it would be a nice idea to handle what mIRC sends to the server. For the moment, if I want to halt some default automatic actions done by mIRC (such as /mode #channel on every joined channel), there's no option for me. Something like on *:SERVOUT:<matchtext>: would be great, allowing us to /halt or to modify (/raw bleh) what is sent.

i personally cant think of one place this would be usefull, since most ircds commands are pretty much set in stone as to how they need to recieve messages. the limited things u may have to change can be done thru /quote and the like. give an example as to where ud need to change the commands being sent to the server if you dont mind.

Ditto d3mon. Not only that, even more reason for people to "hide" commands.. You think you said one thing, and another was sent. You wanted to op yourself, but it ops someone u were unaware of.

No thanks, if you want to enterpret your own command--/sockopen is available.

There is one place it would be useful... making mIRC work on MSN. I don't know if that's the reason the poster wanted it for, but that's the only one that comes to my mind. Unless someone can provide legitimate reasons for it to be added, I don't think it should.

nobody start saying "you use msn etc etc" because i dont.
there is no need for on *:servout for that because the msnchatx.ocx already does it.

/mode #channel isn't a default mirc action when someone joins. All the happens is the joining is displayed, which can be turned off or responded to via the on join event. All other mode changes, like +o/v/l/i/m/M/R/ etc are triggered by scripts and not mirc

Not to get off topic, but it doesnt? Have u actually even tested that before hypothesising

mirc Debug:

-> irc.dynamix.com JOIN #BAR
<- :KT|Lazy!KingTomato@mask-20252708.lndnnh.adelphia.net JOIN :#BAR
-> irc.dynamix.com MODE #BAR
-> irc.dynamix.com WHO #BAR this is my own scripting
<- :irc.dynamix.com 353 KT|Lazy = #BAR :@KT|Lazy
<- :irc.dynamix.com 366 KT|Lazy #BAR :End of /NAMES list.
<- :ChanServ!services@dynamix.com TOPIC #BAR :Teemu drank the bar dry! What are we to do? -:|:- Save the channel! =( || Save The Channel Fund! Donate to help save the channel (Note you get absolutly nothing for your contribution .... (KingTomato)
<- :ChanServ!services@dynamix.com NOTICE KT|Lazy :This channel has been registered with ChanServ.
<- :ChanServ!services@dynamix.com MODE #BAR +ntr-o KT|Lazy
<- :irc.dynamix.com 324 KT|Lazy #BAR +ntr
<- :irc.dynamix.com 329 KT|Lazy #BAR 1064205037
<- :irc.dynamix.com 352 KT|Lazy #BAR KingTomato mask-20252708.lndnnh.adelphia.net irc.dynamix.com KT|Lazy H :0 KT|Scriptin
<- :irc.dynamix.com 315 KT|Lazy #BAR :End of /WHO list.

My IRC program in C#

:KingTomato|CSharp!CSharpBot@(Addy) JOIN :#bar
:irc.dynamix.com 332 KingTomato|CSharp #bar :15,1Teemu drank the bar dry! What are we to do? -:|:- Save the channel! =( || Save The Channel Fund! Donate to help save the channel (Note you get absolutly nothing for your contribution ....
:irc.dynamix.com 333 KingTomato|CSharp #bar KingTomato 1061225345
:irc.dynamix.com 353 KingTomato|CSharp = #bar :KingTomato|CSharp KT|Lazy
:irc.dynamix.com 366 KingTomato|CSharp #bar :End of /NAMES list

That's a good suggestion. I'd like to intercept some commands that mIRC sends through its automation; well, through a command too (better than having to use aliases, events like ON INPUT and such).

Why exactly would you want to block that? So that mIRC has incorrect information about what modes are set on the channel?

Anything you need to want to be edited is already allowed via the "halting default text" option in mirc . The other alternative if to redefine an alias to do what you want to do. ersonally, there is no need for a function to intervene with the text being sent to the socket on the grounds of a "legitimate" reason.

You're right, I agree. But I misunderstood the suggestion.
I'm currently writing a new post explaining what I really want, then I'll post in a new thread here for discussion.

Edit:
LOL, nevermind! Writing the post, I realized that many issues I thought of already have applicable solutions, then I concluded that what I really want ends up being completely satisfied if a built-in theme system is added, which was suggested thousands of times already.

Sorry for replying to this 2 days later.. i'm quite busy these times :tongue:

There's two reasons why I posted that. First, I connect to IRC through a psyBNC and the program itself returns the channel modes (raws 324 and 329) when I join a channel. mIRC sending a /mode #channel at the same time, I send 10 /mode #channel everytime I connect to my psyBNC... making me lagging. The second reason is that I would want to $strip() text that is sent to a specific channel, both in what I type in editboxes and what I send via a script (mp3 player, away, etc.). I know I could make a on *:input:#: and modify each script to use a *putmsg* alias instead of the initial /msg command, but I think it would be much more easier to have an event triggered before something is sent to the server.

Also, I read in that post (I don't remember who said that) this could lead to 'hiding commands'.. I agree with this since one is a bad programmer. This is not my case and I hope this is not the case of everyone here. Every command could make mIRC become a backdoor and I don't think we should think about that when suggesting new functions... Well, I think it could also help to protect against irc worms, halting every spam text and advising the user he got a bad script in his remote.

By thinking a little bit, I'm sure everyone could find a way where that suggestion would be useful..

(Sorry for my english, my first language is french ... )

I suppose that's true.

As easily as this command could make backdoors easier to write, it would make protection scripts even easier to write.

It would also be a great way to unify a command queue instead of having to alias over all of mIRC's commands. By this I mean a queue that gives certain commands precidence over other commands, mode stacking, and other fun botstuff to prevent getting flooded off the server.

Yes, every mIRC event and command can be used for bad, but mostly for good.

- Raccoon

Even though I probably won't upgrade past 6.03, here's one thing I'd hypothetically use it for.

ON *:SERVOUT:$(* $+ $pass $+ *):if ($istok(ChanServ NickServ Identify NS CS,$2,32)) { return } | else { halt }

And I $1- would return $me IDENTIFY passwordSENT

Where $me is $1, the person who sent it.
And $2- is the stuff I actually sent.

on 1:INPUT:*: {
if (($pass isin $1-) and $wildtok($1-, *serv, 32, 0) > 0)) { return }
}

Pass is the password, on input is the event, and this is where we say script it

Sorry for the remarks, but seriously.. On input is there.. its not any easer tot ype on SERVER_WHATEVER: then it is to do on INPUT.. or just this..

alias msg {
...
... do ur crap here
...
}

done, and done.

Smart spam/trojan/whatever-kind-of-bad scripts (they must exist anywhere..) would use !.msg, neither ON INPUT nor an alias would override that.

I didnt mention prevention I mentioned creation... There is a difference

Well, I didn't specifically mean prevention nor creation, I rather meant use. I didn't say you mentioned anything either, so..

(sorry for the duplicate email notification (if you received))

But there's a difference. ON SERVOUT could prevent a lot more than what ON INPUT would do.

A side note. I wish the whois for notifies would do "whois nick nick" instead of the regular whois.