Well there are many ways for script kiddies to modify the registry. Simply supply the registry.dll with the provided script, and viola.

However, I think built-in mIRCscript, if it ever had native registry support, should be ONLY limited to a specific key in the registry.

Something like, HKCU\Software\mIRC\

You can modify, delete, read, and change values in ONLY that location. Maybe having the key in HKLM would be better for some people, though.

This would prevent users from seriously damaging their registry.

I also think it would make mIRC a 'true' windows 32 native, as opposed to its continuing usage of ini files.

But hey there are strengths and weaknesses to both methods, and quite frankly mIRC itself works fine using ini files so one might as well not complain.