mIRC plugin

Started by Ralesk,

Ralesk

Newest, 1.7Pro, version of the mIRC plugin wants to /say or /me into the server window... I can't seem to use it (and I don't want to change my lines into /describe # blabla... that'd be nasty.)

I hope the author sees this!

JimVonMoon

#1
QuoteNewest, 1.7Pro, version of the mIRC plugin wants to /say or /me into the server window... I can't seem to use it (and I don't want to change my lines into /describe # blabla... that'd be nasty.)
Actually the newest version is 1.8 but I don't think that it solves the problem.

As you can see since v1.7 my script supports all mIRC identifiers in NP line format fields (now you can use $ip, $ansi2mirc and many other identifiers that are completely unnecessary in NP lines :P).
It works only because my script sends NP line via DDE to mIRC (yeah, I now it's stupid but I haven't got any better ideas how to do it). And, of course, all DDE commands recieved by mIRC go to status window.
 
My first peace of advice: download v1.8.
This version gives you 4 possibilities to fix that problem:
1. You can turn mIRC's DDE server off (most people don't need it anyway ;D).
2. Use /xmplay command with a parameter (eg /xmplay #xmplay - btw such channel would be a nice thing ;D).
3. Use this damned /describe (or /msg) command. ;) Line:
/describe $active blah blah blah
is exactly the same as:
/me blah blah blah
(you can use %target parameter if you don't like $active)
I don't understand why you don't want to use this leet command. :-/
4. You can change the script by yourself. ;)
QuoteI hope the author sees this!
The author sees all! :evil:

Ralesk

#2
Why did you change?  This is a lot more complicated than it used to be and I also think there is absolutely no need for all the needless variables.

It's not that I dont want to use it, but I think a /me foo bar or a /say foo bar (or even the alias /ame which would send to all channels...) is a LOT easier than to fiddle with stuff like $active...  are these mentioned in the help file?  No.  Any normal user would just persay or perme it and then wonder what the fsck is going on...

And I'm lame to mirc scripting...  I looked into it and after like ten minutes I have found which line sends actually something.  But how to "cure" it...  naw.  If I or an average user knew how to script, we would have written a script ourselves, not?

PS: please look into the tab order of the options window... after the MOD textfield comes the OK button, quite illogically.

And, I'm really thankful for this script and I like(d) it a lot, but the changes are undocumented and thus it is quite a bother for the most of us to use it...  I guess you can understand my frustration.

JimVonMoon

QuoteIt's not that I dont want to use it, but I think a /me foo bar or a /say foo bar (or even the alias /ame which would send to all channels...) is a LOT easier than to fiddle with stuff like $active...  are these mentioned in the help file?  No.  Any normal user would just persay or perme it and then wonder what the fsck is going on...
It seems to be OK now. Please check v1.9Pro. I gave it about 5 second testing (got no time, all exams failed, they are going to kick me out of this damned university - I am sure you understand :P) so please tell me if I'm wrong.
QuotePS: please look into the tab order of the options window... after the MOD textfield comes the OK button, quite illogically.
Fixed.

Ralesk

Sorry I was so harsh last time... and yes, I can definitely understand the problems with your exams... :-/