.mrc... - mIRC Discussion Forums

Not really a MAJOR feature, but I'd like to see the default created script files (Aliases/Remotes) be defaulted with the extension .mrc instead of .ini, seeing as how .mrc has inevitably become the standard of mIRC script files. Anyhow, more like a personal preference, really; anyone else?

i agree, .ini files are annoying to edit in notepad -_-

yeah .. it should have been changed
when .mrc was introduced really.

Edit: .. although I still would like the choice to use .ini

Is there any difference besides .mrc and .ini besides the way it shows up in a text editor?

file size

.mrc is simply a flat file, an unformatted text file.
as a matter of fact, you may use -any- extension, except .ini, to acheive this effect. But I agree, the default filetype should be non-ini.

And in the load dialog (Alt+R -> File -> Load), it would be nice to have this selection as default: *.txt;*.ini;*.mrc
(right now it's *.txt;*.doc and I often find myself playing with this option before I can select the desired script file).

agreed

For me, *.ini;*.mrc is the default.

You probably opened the load dialog from the Aliases/Popups tabs

Nope, from any tab, and in a clean copy too.

You probably loaded a .txt or .doc file last time to get that

Yes, you're right. I usually load .txt's to my remote, hence the pre-selected file type.

I agree. The .mrc file should be the default file type, but .ini should also be offered. The only benefit the .ini file has over mrc is its unique ability to store other information as well as just the script. i.e.

----- Script.ini -----

Code:

[Network]
KingTomato=MyPassword
[Remote]
n0=on *:CONNECT: {
n1=  if ($readini($script, $network, $me)) /nickserv identify $ifmatch
n2=}

----- /Script.ini -----

Where you can have settings stored in the same file. Otherwise, ini's are just larger in size, and harder to edit externallty.

It's not an unique ability, you can achieve the same results with any other file type...

Code:

#ini off
[Network]
KingTomato=MyPassword
#ini end

on *:CONNECT: {
  if ($readini($script, $network, $me)) /nickserv identify $ifmatch
}

...Provided that you'll always put the INI group before everything in the file, so $readini wouldn't completely mess up your script where it finds chars like '[', ']' and '=', searching for sections and items.
(Group usage is just a precaution, hopefully you wouldn't really need one)

But it's not a great idea to use a loaded script file as an INI file too. You will have write conflicts when INI cache is flushed to file, especially if you edit your script or toggle (.enable/.disable) any other #groups in the script.

- Raccoon

Hrm, what kind of problems? I know I've been using them like that for a long time and no problems have ever happened.

Same here .. with no problems.