Making a custom data asset
12 Replies
It's abstract
Does it need to be abstract?
oh i see
i didnt want the class to have any logic handling, just structure and specifications
i thought abstract was the way to specify that?
where it has to be implemented and cant be used directly
Instances of a data asset are... instances of that data asset class
As opposed to blueprints, which create a new class, such that you can have instances of that child class
yeah i see what i did i was trying to make it as a blueprint, but use it as a data asset
if it's a data asset then it should not be blueprintable or abstract
Yeah, you also want NotBlueprintable so that you can't do that (unless you actually want derived data asset classes in blueprints for whatever reason)
i would still want
BlueprintType, right?BlueprintType means that this type can be used in blueprint code
So being used as a variable in BP, and access to its properties
you have BPRW properties so yeah you want it as BlueprintType
although those properties will only be set once by the data asset so probably remove that from them?
I would worry about that later