Right now, you can expose variables in blueprints to the level designer by making them “editable”.
It’d be nice if you could do the same with functions. Right now I’m using bools as a work-around.
Cool.
'Cause a variable for something that should be just a click just seems weird (And difficult to determine if is in fact a variable or a function).
What I had in mind was, instead of this:
You’d get something like this:
Hi MulleDK19,
How do you imagine level designers using exposed functions? Would you want them them to have a checkbox like you show in the video, and that enables/disables functions? Is the idea that they can disable functionality, and any calls to that function will just pass through without executing it?
I am trying to envision a specific scenario, so I can maybe help suggest an alternative.
If we were to implement something like I’ve explained, then we’d just do it in that same manner that you have, with a bool variable.
This is a feature we’ve discussed before internally, and have some use cases where it would be much nicer than a toggling bool. I’ve thrown in a TTP to discuss potentially implementing it in a future release.
Cheers,
Noland
Ya, the video was still processing. It provides 1080p now.
Great. cheers!
Awesome, yeah I could barely make out what the checkbox said in the video, so seeing it here is much clearer. Like Noland said, we’ve created a task to track and discuss this feature. Thanks for bringing it up!
Look like cool idea for object testing for designers 
+1