Where does this custom inventory data "live" at runtime?

[anonymous_user_a1d09d07]

@IanBreeg;337133

Sure, items you spawn in the world are ‘pickups’. And for that you’d definetely want to use an Actor class. But I was referring to items you ‘store’ on the character, like after you’ve interacted with some pickup. You don’t want this whole pickup anymore, you only want its class and runtime properties, like quantity and etc. So for that you’re better off having a struct with several fields to hold just the information you might need in the future (when you decide to drop it or save to some persistent storage in a database).

But again, if you use structs to define an “item” then how does a level designer, in the editor, make different types of items and define their properties? That is the part I don’t understand. With Actors – or in my case i’m trying it with ActorComponents – the designers in the editor can make a BP from it and set its properties. If I instead made my items simple structs, how would the designers then work with them?