Manually set blueprint interface to be function without making a return value?

Development Programming & Scripting Blueprint
, , , ,
1

When making events in a blueprint interface, so long as an output is not created, the event will be displayed as an event when implemented in the graph.
If you set an output, it becomes a function.

Just for organizational purposes, I prefer to use functions rather than events unless I need latency action (delay, timer, etc).

What I do is add a boolean output:

image
image1314Ă—547 65.9 KB

just so that it is forced to be displayed as a function.

Does anybody know if it is possible to set the event to display as a function without having to add an output?

Is there any fundamental knowledge I’m missing to suggest this might be a bad practice at all?

It is just personal preference, but I don’t like tons of stuff in the event graph. I like to use functions over events when possible so that I can open one at a time and not have any other nodes to get distracted by.

1 Like
2

Inside your InterfaceBlueprint you can tick Const and compile. If you double click the Interface “Event” inside the blueprint where you implemented it it will be a function. You can also deselect Const again inside your InterfaceBlueprint, compile and it will stay a function. Depends on what you want.

4 Likes
3

Thanks @L1z4rD89

The Const flag indicates the the function is promising not to change the value of any variables. Is that right?

I did a some c++ courses in the past, but not sure I fully understand the implication of what const means.

4

Yes, const = not allowed to change any variable.

5

is that inherent to an interface function though? Does it also mean that the class which implements the function must not change any variable?

6

Everything inside this function is read only. So it is more like a Get function. Inside this function you can not e.g. use a SetVariable. What you do outside of this function works as always.

2 Likes