As a side-effect of these changes, it is also possible to force a specific resource to be loaded by the client. This might be useful if you do not have client.preload_rsc turned on but you need to make sure certain resources are pre-loaded in a given situation. Currently, this involves sending a query to the client each time it is called (no batching or server-side memory), so just keep that in mind. Example:
mob/verb/test()
usr.client.Export("##action=load_rsc",'whaap.wav')
usr << "Whhhhaaaap!"
usr << 'whaap.wav'
If this turns out to be a common need, we'll probably add a convenience function for the purpose, (and it would take multiple files rather than just one). Many other client.Export() actions are handled through convenience functions (such as browse(), browse_rsc(), ftp(), and so on). Hopefully this won't be the case, though, because that would circumvent the ease of use that the automatic system provides.
I believe doth time has come to turn this into a proper function, and such create a reference entry.
if such a function were to be implemented into proper function form - it'd be coo if it could accept a list of resources or something (a list of objects whose icons need to be transmitted?).
Definitely needs to be a function