I first noticed it when I created a realy big script (over 500k) and never thought of spliting it to multiple files. Few days later I noticed that the file got corupted and I thought that it might have to do with a HD problem I had (A software called deep freeze doesn't work with Nforce chipsets and it crashed the HD literaly!!!).
After I fixed the corrupted file, I noticed that I can not add new text in the script to the file using the script editor (When I press a key it jues nothing, just like you have a form which is limitted to lets say 20 letters and you are trying to add the 21th letter).
This is not the only problem..... if it was then I wouldn't bother to nag you, but the problem with the script editor is that is corrupts files!!!
For this matter I have created an example:
We will create a "script" (well actualy a text file) which is bigger than 500KB and we will load it into mIRC..... Then I will show you that it gets corrupted.
Lets start with our text builder script:
alias crpt {
var %a = 1
while (%a <= 2000) {
write crpt.txt $str(%a,100)
inc %a
}
}
Now lets load the file into mIRC:
/load -rs crpt.txt
Now we will look how the text file look like in notepad:

Looks fine....
Now lets look how it looks lke in mIRC script editor:

You can see that "2000" that should be at the end is now somewhere in the middle!!! NOT VERY GOOD

Lets look at the end of the script in the script editor:

You can see that line 1553 is shorter.... The reason for that is that line 1553 was Cutted in the middle!!! The first half is still where it is supposed to be and the next half is near the end.
The line that contains the 1553 was splited exactly at the 500KB !!!
Now lets overwrite one of the numbers in the script editor and then press OK (if we change nothing then presing OK will not save anything into the crpt.txt)
Now lets open the crpt.txt with notepad:

Now the original text file got compeltle corrupted... the order of the lines is messed, the line with 1553 got splited etc.
IMO the file size limit shoule be higher..... yes, I know.... scripts are usualy not that big, but still.
Thanks, and I hope that this problem will be fixed someday (Problem was tested on mIRC 6.16 and 6.17)