I appreciate the suggestion Chrustec, but that is not what I am talking about and is actually a worse solution than just making another blueprint; that solution would end up wasting lots of processing time. What Farshad said makes a lot of sense: you have to use Archetypes to understand why they were so great. You can do essentially the same thing as an archetype by just creating another blueprint, but it would be cluttered by the event graph and components section, which it just simply doesn’t need.
What I would REALLY appreciate is for an Epic developer to give me some feedback on why they didn’t choose to implement something like archetypes or if there is a way to do something similar.
PS: hit it right on the head with that image and short description: that is what archetypes should be.