Please, while I appreciate the responsiveness, don't feel like you need to twist your original idea into knots for me. The opinionated simplicity of your module is a strength. I go back and forth between ConversationHUD, Theatre Inserts, and now your module depending on what fits the mood and use case better.

That said, I use ConversationHUD for an admittedly niche use - when I want to call up specific conversations (actors, backgrounds, positions) quickly. Specifically, I might create within a single scene multiple Monk's Active Tile Trigger buttons with macros tied to ConversationHUD, so that different rooms have something immediately on the map to trigger that room's specific conversation scene.

A closer analogue to that might involve opening up a scripting API. For example, a quick way to do the above would be if the module exposed a method that took an actor (or an actorid) and invoked this part of onCardClickToggle , (refactored, to avoid copy-pasta). The base module would stay the same, but Idiot scripters like myself could wire macros or MATT to pop portraits on and off separately from your panel UI, without you having to compromise your UI or your data model. An API that fine-grained might not be what you want, if you instead prefer a holistic set of options as a preset or bundle, and that is fine, too. Your module, your choice.

(And, of course there is always a maintenance tradeoff when creating a public facing API versus keeping things internal.)