When my ISP switched servers it upgraded the php version and changed some defaults. The text encoding output changed and it broke the macro. Shaky, thanks for letting me know. It is now fixed (2 lines of code & an hour later). Giggles also requested a feature allowing you to set the use amount per pulse “/use X\r” where X is now a pull down with options between 1 & 10 for people with crazy fast Regia. Doh! I meant Respia. (Thanks Leinis) hehe.

While I have not extensively checked it, it seems to work fine now.

I had problem using my Fkeys (F3,F4, etc), but some worked. I realized I had other macros binding to my F3 F4, etc. So, I moved those macro files to load on the character they belong to, so now the Fkeys work. Shaky if you can’t use all the keys, you can look/search your macros for other macros bound to whatever you set.

I really wish CL had a command that would read your macro fie and show all the f-key and other trigger (optionally the text triggers and expansions) so we could avoid overwriting a macro trigger with an other macro.

Shakyamuni wrote:Oh something I noticed.. Shaky doesn't carry a weapon.. So is it possible to make it so you don't "require" one?

The word you fill in for weapon can be “moonstone” since the script only checks to make sure [:alpha:] (“A to Z”) characters are present. You could also type in “bacon” but you’re likely to get an error message like “you have no ‘bacon’ to equip.” For your use case (which may be not just your use case), I rewrote the macro to check each swap and if your right hand item is the moonstone. If it is it starts the infinite healing loop. This means it will still try to swap, but if you defined your weapon as a “moonstone,” it should start the self-healing loop but also give you the message “your moonstone is already equipped”.

I realize it’s not a clean fix since it will generate a message, but it does refine the moonstone_functions’ utility. So, thanks for the suggestion. If anyone wants to rewrite “itemswap” to get rid of the message in the case that the person’s weapon is a “moonstone” & submit it to me. Feel free to do so, and I’ll credit you in the macro.

FYI: There was a recent bug induced into the text encoding thanks to a recent server move (mentioned in Coffee & Donuts section) that is now fixed. But if you get any errors while using the macro, please report the error message to me, verbatim. Thanks.

Shaky,
per your request I updated the QuikNDirty cad builder ( http://noivad.net/moonstone_functions-template.php ). choosing "none" for the restart moonstone modifier will now use the cad-lock modifier to do the swap while the trigger labeled swap will use the unmodified selection — esc in shaky’s use case.

I could refactor to make it more flexible, but without feedback, I don’t know what additional feature are desired. Currently, my Thoom flies around the field with my setup plus Gorvin’s Right-Clicker 2 macro & a gaming mouse (Logitech MX Master) with F-triggers mapped to all the extra buttons.

FYI: Shares.txt (v2.1.7) )on the CLUMP had a minor bug skipping exiles that are not clanning/non-exsitant. I messed it up when I added new functionality. It’s not fully debugged yet though So, regressions/errors? please let me know.

In plain language: I’m messing up cuz I is rusty af, & forgot how these worked, and a cursory glance to get my bearings is not enough without notes.

Devs:
I’m out of practice with the CL language and how basic it is, so bugs will be a bit more common. These updates might be wonky on edge cases that aren't caught properly. Refactoring the scripts is more difficult because the barebones-ness of the macro language means we have to either document more than we think we need to becaus =e what was obvious 2 years ago is forgotten. Also the barebones part, makes for a lot more mental juggling. So, I’m starting to comment sections and globals more explicitly to prevent these regressions. When I was being paid for development I was logging everything, and it ran much smoother. If I could find a way to make money on CL scripts (jk) my work would be more organized .

If you get an error or things aren't working "/set debug 1" (if you have that macro in my defaults) will give more feedback, assuming I included the block. and you can send me part of your text log so I can see what parts are erroring out.