@splatwes Sorry just one question on the way you were thinking of implementing this, were you thinking of allowing at the moment up to 3 different viewer html pages? so I would have viewer-panel.html, viewer-overlay.html and viewer-component,html (if that’s the use case for components). Or were you thinking one viewer.html and the developer has to distinguish between the two?
To answer your question however I think for example I am building an extension for my Twitch Chat bot, this extension is going to have things like a “casino” and other features. I would like a “click map” section to the overlay extension but I only want the “broadcaster schedule” part of the bot to be on the panel. So although they are the same extension, integrated into the same EBS and are part of the same twitch bot. I would have to have a specific Panel and Overlay Extension as the “single” extension with multiple anchors wouldn’t be a viable option as I would like both.