Hmmmm, another thought. This really shouldn’t happen on a Saturday morning. When using a .mf file as a web plugin it will need to have its file writing capability limited obviously, otherwise it could go and replace shared libraries etc, which would be bad. You might want to pre-empt that by defining some function that returns a directory that its allowed to write to, for storing local data - saved games etc. Would have to be keyed off the path of the .mf file, be it local path or url. Also include a function that returns how much space its got - will probably want to cap that for web apps, otherwise you could get 100meg files from a browser game, which I would personally frown on. Its a simple little task, but if web games are your ultimate goal then standardising this stuff early will help.