Sign up to Hawkee
commented on mIRC Script:
Dec 23, 2006
As update wont be approved as soon as i xpected i will put a little comment on current version released here.
First of all, thanks for nice review RoninWarrior. As instructed in readme file all credits (plus website & contact/support) can be found in JediControls/JediHelp/Help. There are 2 parts in fact, credits for partial code solutions (coders/scripters) and for ppl who helped me out in person with tips / testing /suggestions. Snake is there also, i do consider him to be one of the best scripters ever. ;) Besides Credits section in Help file, u can find 'em all in code comments also.
Thx for comment Lindrian, now about themes u mentioned, i dont use some theme system like MTS but u can do few tweaks with ctrl+F10 or JediControls/Configure/vStylez then hit 'Default' button to get the visuals i prefer or simply play around with options, not sure if they work on 6.2 tho (still oldskuling on 6.16 lol). As u have noticed there are CPS (Amit) and KBD (CyberLoner) both used with Author's permisions, tested thru years on various servers and in my opinion improved both in efficiency and compatibility. :)
I hope update will be published soon cause it brings bugfixes, few important changes/features and enhanced overal stability. Thats it for now, have some great time ircing & happy holidays everyone..seeya around guys.. :)
commented on mIRC Snippet:
Oct 09, 2006
Sry, i ran out for a bit..
Now, you prolly ment %locked On, %win.ini <1st encryption>, %mirc.ini <2nd encryption> but.. have u actually tried it? :)
As for direct answer, this method is more secure (& better) because:
1) when u lock ur mirc with built-in locker, u can open it on any system without reg changes (ex. ur friends comp or 2nd sys on ur machine);
2) for the same reason, if u lock one instance of mirc, all other will be locked too which is pretty unpleasent if u script or something;
3) due to its nature, build-in locker might have problems under wine. (not tested);
4) u cant remove protection by simply deleting/changing variables from remote.ini (in case u find em 1st), in fact u will make things worse as u wont be able to open it at all until u copy vars back;
Anyway, u gave a good point, if this was separate .mrc file u could simply delete it to break script based protection. Thats why I added detailed instructions of passlock implementation for scripters in 'Author's Notes'.
Thx for input Yoinx. :)