thank you for the reply.
that’s an interesting take on the problem you got there.
i didn’t think of that.
what i ended up doing is creating a class with geometry collection component in it.
then create a bunch of child blueprints of that class each one to hold the different geometry collections i have, then i choose the correct class to spawn using a data table.
actually the way you’re doing it might be better than mine since you don’t have to create a bunch of different classes that only hold GC, only down side is that enum can get a bit heavy and confusing depending on how many GC you have.