What the Well-Dressed Man Is Wearing
What ho, script-users all! The devs have very understandably decided not to implement a CLI command for the portable pantogram, however I found the daily trousers ritual had become rather cumbersome, like that cheery aunt who's come round for tea a few too many times in recent history for my liking, if you ask me. One's patience only goes so far, does one's. So I wrote this little blighter that almost fools me into thinking there is a CLI command that works pretty much just like I'd want it to. Topping, eh, what?
How to Use It
Simply typein the CLI. The keywords are items or modifiers or nicknames, and specify what you want in each slot. They can be in any order. You may omit specifying up to all slots -- for any omitted slots, default choices will be used (the obvious free choices based on your primestat, plus stench resistance and -combat). You can type "pantogram help" to see a list of all available keywords, keeping in mind that in addition to the provided list, the item name will also work. The default/current choice for each slot will also be bolded so you can see what you need to select if you want to override those values.Code:pantogram <pipe-delimited item names/keywords>
Since summoning pants is something you can't retry if you mistype, the script will tell you what it's about to summon and sacrifice, and ask for confirmation before actually summoning your pants.
But now things get more powerful, with a few features for people who wish to automate or just generally be 'power users'. There are a handful of keywords which you can also include to alter the script's default behavior:
- silent -- Suppresses the confirmation message, so you'll simply get whatever you typed. "pantogram silent" would simply summon pants with all the default choices.
- default -- Useless. Does nothing. It exists so that you (or cli_execute()) can "pantogram default" to summon default pants without triggering the popup asking for params. Including this keyword will not overwrite any other selections.
- force -- This keyword lets you make prioritized lists. Normally, if you specify multiple selections for the same slot, the script would abort with a warning. Likewise, if you specified a keyword but don't have the requisite item, the script would abort with a warning. However, using the force keyword, you can specify as many options for a slot as you'd like, and the most recent (last-mentioned) possible option will be selected for that slot.
For example, "pantogram low meat|low items|high items" would cause an error because they are all options for the same slot, but "pantogram low meat|low items|high items|force" would first check "low meat" (let's suppose you have a taco shell), choose that, then check "low items" (you lack a fairy gravy boat so it will stick with the taco shell), then move along to "high items" (you have a tiny dancer), choosing high items for the slot in the end. If you lacked the required sacrifice items for all three, it would fall back to the default.
- help -- as already mentioned, prints a list of keywords for each slot (with current selections highlighted). Current selections, meaning whatever is currently chosen at that point in your keywords list. "pantogram mus|help|mox" would show a list with Muscle highlighted as your current choice, then pop up the confirmation message, in which Moxie was your selected bonus. Silly, but possibly useful in debugging.
Download the two attached files. Put the text file in your data directory and the ASH file in your scripts directory. You're done!
Spiffing! I find that being conveniently betrouser'd has put a veritable spring in my step! I wish the same for you lot. Toodle-oo!