I did consider how a mud might go about handling versions - perhaps maintaining a series of "patch from version X to version X+1" files as well as the full package, and if you're more than one version out of date the mud could either send you several patch files or just resend the full package (whichever is smaller). But I'm not sure it's really necessary...even if you have to get all the scripts again each time you update, it's still going to be a pretty tiny download.Oneymus wrote:Theoretically, with downloadFile( path, URL ), it's possible to do the same in Mudlet. It's not something I've played with, but it is an interesting concept. Barring a fully-formed Mudlet package repository (with proper package support, of course), this is the next best thing. It would require that as much of the scripting as possible be moved to separate .lua files in order to ease replacement, which introduces other problems (no scriptable Events, can permanent items be deleted via script? to name a couple).
It's only really when it comes to graphics and sound files that size starts becoming a concern. In theory it should be possible for the latest script to check for those, ideally using the datestamp as well, and download any missing or outdated files individually.
On a slightly related note, I finally managed to get my protocol snippet working, and I plan to release it soon. It only takes a few minutes to add it to a mud, so I'm hoping we might see a few more mud owners taking an interest in GUIs in the near future. It uses MSDP, but I'll add my ATCP hack before I release it, so that Mudlet can use it as well.