What doesn't work: event handlers that are bound. Everything else works for me (including Geyser stuff so you can share your tabbed overlays easily, and have their load method bound to the resizewindow to keep them in the right proportions!)
A centralized script system
A centralized script system
I'm unsure whether a similar incarnation of this script exists, but if not, here is a way to share scripts easily across sessions. To use it, make a script with the following code in it, and make sure it has a sysLoadEvent handler. Then, instead of importing scripts across profiles and having to do it over and over again with updates, write your code in .lua files, and store them in a common repository. My respository is my mudlet home dir+shared/. To load a script saved in here, do: loadShared('package name'). For larger packages with many subfiles, you can create a directory and load all the files within that directory with: loadSharedFolder('3k Mapper') (3K mapper being my shared directory).
What doesn't work: event handlers that are bound. Everything else works for me (including Geyser stuff so you can share your tabbed overlays easily, and have their load method bound to the resizewindow to keep them in the right proportions!)
What doesn't work: event handlers that are bound. Everything else works for me (including Geyser stuff so you can share your tabbed overlays easily, and have their load method bound to the resizewindow to keep them in the right proportions!)
Re: A centralized script system
Also, the directory listing is very specific to linux. Windows users will need to see how to get lua to list directories, and if you do please post it and i'll update it to address windows/linux specifics.
Re: A centralized script system
can use the registerAnonymousEventHandler() function for event handlers.
Re: A centralized script system
Hey, I just started trying out Mudlet and I've been looking for something like this to keep scripts in sync between multiple profiles. Is this still the best way or have you found a better solution since then?
Re: A centralized script system
Modules have replaced this system.
Re: A centralized script system
Got some pointers about modules? There doesn't seem to be much on the wiki.
Re: A centralized script system
Sure, install by Toolbox -> Module Manager
If you choose to Save & Sync them, any changes you make while in the mudlet-editor will propagate to other modules. Priority is the load order, in case you have modules that depend on each other.
If you choose to Save & Sync them, any changes you make while in the mudlet-editor will propagate to other modules. Priority is the load order, in case you have modules that depend on each other.