Yes, a /filewatch would be required. mIRC only parses events when something triggers them, it does not create triggers out of events.
Thanks for clearing it up.
As far as the suggestion itsself goes - yes I personally can see quite a many use cases for it. Script settings file being one of many as Raccoon already points out in the title of this topic. Getting ability to have constant monitoring of specific files in realtime would make some things easier.
The use of a CRC check has been discussed before but it would not be practical. If someone has a large number of scripts loaded, this would result in a freeze every time mIRC had to scan all loaded scripts, eg. at startup, whenever you edited a script, or during file change notifications, since a CRC check would take time to perform. A file time check, on the other hand, is instant and, although there may be some outliers, is generally satisfactory.
I don't mean to hijack this thread for another suggestion but wouldn't it be viable to add at least DST to the existing routine to supress the pointless warnings twice a year when DST changes?
Seeing as mIRC already can tell if DST is in effect or not ($daylight) it seems like something doable if you store the seconds offset along with the timestamp and suppress the warning if the timestamp changes together with the DST offset (Or check specifically if the amount of change is the same as changed seconds offset.)
