Hi!
Currently experimenting with Smart Objects and State trees. It’s a bit confusing on how things work in the background, if you are just using Blueprints, and don’t have access or can’t read code that runs in behind the nodes.
After inspecting the code behind it all, I don’t understand why actions like “Occupy” and “Free” are done in the background of “UseSmartObjectwithGameplayBehavior”, and are not given to the programmer/ user to define the time to call both functions.
I might want to call “use” to run a behavior but not call “free” when the behavior ends, and I might want to “occupy” the slot, before “use” or running the behavior defined in it.
Yet if you do any of this you get bombarded with log messages.
I don’t want to have to create my own “use” task just to avoid this. I really think Epic should consider how to handle this better. This should be done by the user not in the background otherwise why expose all of these functions?
Would love to hear the opinion both from people at Epic and people in the community that are also experimenting with this.
Kind Regards,
Deeroy08
