None of the access specifies work in blueprints, nor do they at least generate warnings.
Hello ,
I was able to reproduce the part of your issue about showing no warning for access specifiers and logged it for you to view here:
You can track the report’s status as the issue is reviewed by our development staff. Please be aware that this issue may not be prioritized or fixed soon.
I have tested and found that other parts of the Access Specifies are working in a new project. I have a couple questions that will help me narrow down your issue:
- How are you using the access notifiers and how are they conflicting with your expectations?
- Could you provide screenshots of your issue?
Thanks!
Hi ,
Before I begin, can you tell me which parts were working for you? On my end, functions were not working, but I did not test variables nor the specifier of protected.
Cheers
no problem, I created an Actor BP with a custom function that outputs an INT value of 5 and set the Specifier to Private (This means the function can only be successfully used inside of the blueprint it was created in) then created a second actor and in its event graph I cast to the first actor and got the function and had the INT output go into a print string. When the string is printed, it prints out a value of 0, not 5, this is because the function isn’t actually being called despite the editor not giving a warning about it!
It is still not working. You can access any blueprint function even if it marked as private or protected from another blueprint class. Access specifiers just do not prevent from adding it.
Counterwise private flag on variables is working. You cant even see private variables in right-click search menu from another blueprint.
4.20, still happening, can you please fix basic programming thing? That would be great!
Thanks epics, much love. :3