VStar's code base is fairly large (in the order of 100,000 lines of code) and has been around for awhile.
Cliff Klotnik commented briefly on this here:
https://www.aavso.org/comment/65373#comment-65373
While the plugin architecture is intended to isolate a plugin developer from some of the internals, there's only so much that can be hidden and plugins have their own semantics that must be understood.
I'd like to seek your input on which aspects of VStar are most in need of explanation.
I also have a long-standing ticket to create some design documentation.
Thanks.
David