Thanks for looking into it.
I have another request that is more of a new feature: the ability to locally enable/disable the functionality of the plugin, without actually disabling the plugin.
We have some team members that prefer not using Blueprint Assist (clearly they are crazy but I’ll try not to judge them…), but the only way (that I know of anyway) to disable its functionality is to disable the plugin in the .uproject. On a source-controlled project, that isn’t a realistic solution because it forces you to keep the uproject file checked out, and at some point it will need to be reconciled and less-technical people might run into problems.
I had implemented this myself a few years ago on an older version of the plugin by modifying the source directly, but I feel like it would be useful as a built-in feature (and in a probably less hacky way than I had done it). I basically added a user-level (and not project-level) bool to the BPA settings that would early-return in the initialization of the plugin, effectively disabling without needing to actually disable it.
Nothing urgent, just something that would be nice if you get around to it.