Thanks. Simply put, because my experiences with the marketplace do not make me eager to submit another free plugin there. Also I can’t commit to support - I intend to keep it updated, but it’s on Github and people can use it as they like. I don’t have the time to clean up the code, provide proper documentation, etc.
Yeah, and from what I understand, those modifications complicate the license situation, meaning they can’t release that code with the engine source. Anyway, the nice thing about doing it this way is that by piggy-backing on the reflection system, the plugin can document both (reflected) C++ and Blueprint functions by exactly the same process. Hopefully, Epic will add the option to enter function parameter descriptions in Blueprint - if they do, the plugin will include those without needing any modifications to its code.