just imagine seeing all the get/setter variables from the project in one place and u will get the answer to u r Q.
As shown in the images below, setting the variable to “Private” has no effect once its Getter method is in another BP’s event graph.
I guess Private variables are accessible through the correct ref ( variable anotherBP ).
Then what is the point of having access specifier? I mean, if that is the case, I don’t see why the Editor goes to an extent to hide variables from accessing via Event graph. It is almost a broken OOP design, don’t you think?
If you set a variable to private, it is private and you can’t see “Get”/ “Set” from event graph of other Blueprint, that’s is how it is supposed to work. The only other way to access private variables is from within a public member function of the respective class that returns the said private variable.
I am sure you can do that by pointer. But don’t really think it was intended in this case. Oh well, needs someone to clarify.
This issue seems to related to LINK