it would be a huge help if we could set custom event nodes to private so they could not be called from outside. Often I use events only to decouple different parts of a complicated event graph.
All these events in list for a blueprint which should NOT BE CALLED from outside can get really confusing.
Thanks again for this suggestion. As mentioned in other post we were discussing this on, we have an existing feature request for this (UE-19803). I’ll go ahead and switch focus for that to this AnswerHub post, so if I see any movement on it I’ll update here. Thanks again!
Since posting of link, we’ve moved away from hosting feature requests on public tracker to ensure that it remains an easy place for users to search for existing bugs.
I can, however, check on status of it internally. This feature has not been implemented at this time, as developers are currently focusing on high priority crashes and blocking issues. It is still active in our database, however.
I really wished Epic would wait a bit with all big features for once - after Niagara , and do thousands of little things in editor that make whole experience better.
This particular one would also be usefull to hide events that are just used to fire timers.
This is something I have been looking for throughout years, I would love if Epic could get around to it. Or someone else that could implement it for us
Yes please. This is something that would help me right now as I’m developing an asset with blueprint logic to sell on marketplace. Those who buy it would have an easier time working with it if they can only call events that makes sense to call directly (and, I wish events would be able to be categorized like functions so that they don’t just appear under “call function” category when searching for them under right click menu). I can’t convert events to private categorized functions either, because it makes heavy use of Delay node.
I’d love to find out status of this issue. I think it’s important to be able to clearly show that certain events aren’t intended to be called from outside blueprint.
If you do not require it in an Event Graph use “Create Event” node instead of “Add Custom Event” node. “Create Event” node allows you to create a separate function or event or select an existing function or event (that matches parameters). If you use a function that function can be made private and therefore does not become visible from outside of class. Unfortunately this doesn’t always work in case you need event to interact with other parts of same Event Graph. “Create Event” node also shows you function signature as well as allowing you to bind an event or function from another object instead of self.
, and do thousands of little things in editor that make whole experience better.