It's one of those cases of 'implementation and maintenance time cost' vs 'total benefit gained' situations, but...
I'm so tempted to just get drawn back into writing extensive AutoHotKey scripts - AHK programs, effectively - to the extent of making a whole, custom macro tool. Logitech's software is... Getting less and less tolerable, and I'm pretty certain I could just make a script straight on top of a stable config for it that won't interact with its macro tools, and just like, usurp the handling of macros.
I did this way back in the day when I first played Sunless Sea - like, early patches. It was a set of dynamic automation scripts to help automate the Salt Lions trade run regardless of its location (before they capped it), and to automate the Mirror-Catchbox fill-trade run (also before they capped it). I called it The Shaggy Quartermaster, and IIRC it even had settings for loops. It worked by a very early/rough implementation of image-search, allowing it to work pretty much regardless of the resolution, position of game windows, etc. There's way faster ways to do just that now, like, suuuper powerful, just in basic-ass AHK scripts, buuuut...
It's a loooong-ass project. The bare minimum is many features - record/save/replay macros with a lot of configuration, like being able to record a macro that can then be played back in multiple changeable ways such as playing back a just-recorded macro but now with uniform timings between each action of a given value, or the original values reduced by a given percentage, while sitll retaining the ability to play the original macro if desired. Being able to (as a benefit of using AHK) reclaim buttons on my keyboard that can't be rebound via Logitech's software - being able to bind the scroll wheel as something outside of volume! Or even configurably outside of volume, such as with a modifier! The ability to chain together saved macros, have them only fire when a desired window is in focus, the ability to easily access and change these things!
I even got as far as building UI for The Shaggy Quartermaster. In AHK. Just straight up juryrigging a whole-ass program out of a script manager. Probably not the most efficient way of writing that kind of thing, I guess, but AHK was weirdly easy for me to learn, which is always a plus for me; didn't have to wrap my head around object/class situations, or, y'know, even more advanced shit than that.
It begs the question, I suppose, of whether there's a better method out there or not? Is there something more suitable for this task than AHK, that doesn't require picking up a whole new programming language? There might also be unsuitable limits to extensive AHK scripts. Not sure. Just pings around my head a lot.
