ouchsss, ok thanks for you time :).
The enum isn’t for setting those values, it’s for the player knowing which type of pickup they’ve touched and modifying the player’s settings appropriately.
Then again, I’m not sure if it’s best to do this in the Player’s BP or the Pickup BP.
Or maybe the level-blueprint…
I have an custon event in player, the pickup call this event to send the amount of ammunition or healt.
@ Wilson, sorry I didn’t know this thread had been getting replies…
What you are saying is pretty much what I was asking for, but I DO want that simplified editor. Also, having a way to easily save a blueprint used in the world as a data-only blueprint would be great! I didn’t actually know that blueprints without code were considered data-only, so that is news to me; maybe this should be made more obvious (again, having a simplified editor like there was before could solve this). Anyways, my main reasons were for simplicity and faster execution, and the latter is already solved without me realizing it. Hope that helps.
PS: The comparison made earlier to Materials/Mat Instances is very apt, and more or less exactly how I would want it to work.