Changing a function to pure does not update the function to pure in child blueprints
In my parent blueprint, I have implemented a function. In a child blueprint, that function is overriden and used in the event graph. Now I set the function to pure in the parent BP. However, in the child blueprint where the overriden function is used in the event graph, the function node still has an execution input. The workaround to get rid of the execution input was to delete the function in the child blueprint and to create the override function again. Then, the execution input was gone.
asked Jun 13 '15 at 11:35 AM in Bug Reports
Ah, I see what you're saying. In overridden functions, you don't have the ability to toggle between pure/not pure. That seems like an oversight to me, so I've entered a bug report for the issue (UE-17804). I'll let you know when I see any change in its status.
Inheritance of functions should be simple: the child receives all the changes to the function from the parent. If you override the function in the child at any point, it no longer inherits changes to the function from the parent. So a pure function will remain pure in the overridden function, even if you make the function not pure in the parent. If you delete that override, then override the function in the child again, the new overridden child will inherit the current state of the parent. That's all pretty consistent, but without being able to make any changes to the details of the overridden function, I can see how that might be confusing. Hopefully we'll get that fixed. Thanks for the report!
answered Jun 27 '15 at 06:17 PM
Follow this question
Once you sign in you will be able to subscribe for any updates here