This is what I was thinking. Essentially I want to keep all the functionality that the in-built classes provide, but I’d like to add a <User Widget> class variable to use for a contextual menu system. Then I can derive my own blueprints that maintain the parent’s in-built functionality, but also contain the contextual menu class reference as a base property of Actor.