This is one I asked about a while back. To my knowledge, this currently has the status "Suggestion for Future Enhancement"
In theory, all that would be needed would be a simple scripting directive which told MUSHclient (in effect) "Before you do anything else, load the contents of file X and put it right here". MUSHclient, while loading the main script file, would assemble all the library files (In ASP, they're "Include files, so that's how I refer to them) in memory and pretend they're a single script file, to be parsed normally.
This would require additional passes over each of the script files by MUSHclient, *recursively* looking for INCLUDE directives. Once MUSHclient has found and (in memory) replaced the INCLUDE directives with the contents of all the script files, it would then pass it to the script engine.
Then you could take all the MUSHclient constant definitions, stuff them into an include file and put that in a central location to be referenced by your individual world script files, allowing you the ability to edit single files and update the scripts for all your worlds at once.
|