This is possible through scripting... take the challenge!
For example a script which updates servers.ini from
mirc.co.uk/servers.ini- Info:
There is a comment in the servers.ini giving the update-date which could be used as a "version" for checking if an update is neccesary. - Implementation:
Every 1st of the month/on START or whenever... connect to mirc.co.uk to retrieve the servers.ini (eg. using a socket connection; write output to a file and read the "version". Or just read the "version" from the output).
Anyway if you had this "version"...
If the new-version is actually newer than the current-version...
Then you could do something like:
- Simple method:
Do something like replace old-ini with new-ini
- More advanced method:
Replace all [servers] items with all items from the new servers.ini keeping the [custom servers] items.
- "Something completely different"
The first option has drawbacks relating to the user being able to edit the servers.ini through mirc (editing/adding/deleting servers in the Options->Connect dialog).
The second option's servers.ini is NOT standard (It has have two blocks). Unfortunately the second block [custom servers] will not be listed in the mirc-server-management-dialog so a custom-management-dialog would be needed. 
- Conclusion:
- You could always google it.
- A similar method could be used for updating mIRC itself.
--Jah
