I see it this way. The big picture is we have MQ2 with a couple dozen plugins all working in the background, and one macro with 1 or many includes, and all work together. It is an accomplishment that a group of programmers work remotely together ad lib and designed all this software that integrates smoothly with EQ. All of it is "bloat" from an EQ developer perspective. Why not just play EQ? KA is a combat assist macro which provides numerous player services while keeping it simple. isn't that what it's for? Why not have a minimal bit of code that collects quest items with barely any configuration and frustrating guesswork with plugins and disparate macros? It's completely integrated with helpful messages. Documentation on plugins is not there, or doesn't perform the services that I perceive as necessary. If I'm taking KA in a different direction, then let's do this. Strip KA down to it's utter bare essentials, and then provide the means to add-on with more than just binds. I'm already working on that.