This will mean that on load it will load my values then overwrite them with your values. Two things you need to know for this is that firstly, use the same variable name to assign to so it replaces the value(rather simple, eh?) and secondly, Mudlet loads the script settings from top to bottom, so put any overwriting 'personal' scripts into a script setting BELOW any packages you are trying to customise. There are a couple different ways of customising various parts of the packages.įirstly and the most common: overwriting variables with your own values. This is my most common type of question, and requires you not just pick out the bits you think useful but actually listen a fair bit. How should I customise the ShakPack packages? by the way, please tell me if I have left something personal in a package by mistake! I know it's a bit ugly to have a useless folder wrapping up the setting(created by the package exporter), but if you do change the location of the settings, you will need to make sure to manually remove them when updating to a new package! It is strongly advised to leave the folder structure of the package as is. NB: I suggest restarting Mudlet after installing or uninstalling packages. All done, it should now appear in your settings.
#Mudlet 2.1 zip file#
The backbone and facilitator for many other packages, but also includes many toolbox type functions to make scripting easier. Mudlet/Lua Tutorials Setting Up Mudlet Beginner Tutorials Intermediate Tutorials Advanced Tutorials Tips and Tricks ShakPack Packages ShakPack.System ShakPack is an all encompassing collection of packages to aide various part of Avalon life, created by Shakralay. Welcome to the ShakPack wiki! What is ShakPack? 8 Actually its the package, and I have an idea!.5 How should I customise the ShakPack packages?.The stylesheet to apply to the back portion of the gauge. The stylesheet to apply to the front portion of the gauge.Ĭssback: Optional argument. This provides a way to give a caption to the timer, so that you can label it with something other than the timeĬss: Optional argument. TimerCaption: Optional argument, except if you want to pass further arguments. This determines whether or not the time remaining is shown on the timer. ShowTime: Optional argument, except if you want to pass further arguments. If you don't wish to bind to a container, but do wish to set up a stylesheet or turn off the display of the timeleft, then pass the empty string for this argument. Give the timer a Geyser container to bind to. Accepts decimal valuesĬontainer: Optional argument. Time: How long in seconds you want the cooldown to run. This is where you specify your coordinates, height, width, etc. Name: any name you wish to give the timer in string formatĬonstructor: The same constructor you would pass to Geyser.Gauge:new(). I just gussied it up a bit.ĭemonnic.anitimer:new(name, constructor, time, container, showTime, timerCaption, css, cssback) It also means if you give it different arguments (such as a new position or size) then it will use these when it resets.īig thanks to Lin of Aetolia, most of the core logic to the algorithm really didn't get changed. This means if you recall the same timer with the same arguments, it will essentially reset even if it's not finished running from the first time. If you reuse a name, it will reuse the gauge associated with it, giving it the new constructor information, adding it to the proper container (or removing it from all containers, if no container is passed), time, etc.
So I spent a bit of time rewriting it to use Geyser. After a bit of browsing/searching around I didn't find anything that did everything I needed, but I did find the following POST. So I was working on a project and had a need for a basic cooldown timer. The constructor below will only work up to 2.2, the readme at the repo has the new constructor for 3.0+ Everything below here is out of date You should look at for up to date information.