mIRC Home    About    Download    Register    News    Help

Print Thread
#76889 27/03/04 05:55 PM
Joined: Nov 2003
Posts: 2,327
T
Hoopy frood
OP Offline
Hoopy frood
T
Joined: Nov 2003
Posts: 2,327
considering these no longer work (good!), why not add a message (error message) when they are typed.
so typing: //$time, will echo: //$time so such command or w/e


New username: hixxy
#76890 27/03/04 05:58 PM
Joined: Jun 2003
Posts: 5,024
M
Hoopy frood
Offline
Hoopy frood
M
Joined: Jun 2003
Posts: 5,024
Yeah I don't think it would take too long to add that, so might aswell. Can't hurt!

That said, not many people will try to use that in the first place surely?

Regards,


Mentality/Chris
#76891 27/03/04 06:05 PM
Joined: Nov 2003
Posts: 2,327
T
Hoopy frood
OP Offline
Hoopy frood
T
Joined: Nov 2003
Posts: 2,327
maybe not, but it just makes it work like the rest of the language smile


New username: hixxy
#76892 27/03/04 08:57 PM
Joined: Dec 2002
Posts: 1,321
H
Hoopy frood
Offline
Hoopy frood
H
Joined: Dec 2002
Posts: 1,321
I just found out it doesn't work anymore. I used to use that sort of thing regularly, since I do a lot of editbox coding.

//$iif(condition, echo, msg $active) something


DALnet: #HelpDesk and #m[color:#FF0000]IR[color:#EEEE00]C
#76893 27/03/04 11:27 PM
Joined: Dec 2002
Posts: 2,962
S
Hoopy frood
Offline
Hoopy frood
S
Joined: Dec 2002
Posts: 2,962
Yeah it is a shame that some people's persistent ignorance has resulted in a genuinely useful feature being removed, especially since the restriction can easily be side-stepped with pipes and evaluation brackets and is just as likely to be copy/pasted as the common //$ exploits.


Spelling mistakes, grammatical errors, and stupid comments are intentional.

Link Copied to Clipboard