Blueprint function returning wrong value
I have a pure blueprint function that returns a value based on a simple condition.
Now when the condition is not met anymore and the function has no return node, the last valid path is returned. In the case of this example, when the condition is false, the node still returns a value of 150.
I wonder if this is expected behavior or a bug ? Either returning zeroes or a log warning would make more sense and be less prone to errors.
This can easily be reproduced and i have included a test project in the post that shows the issue.
Have a great day!
asked Nov 15 '18 at 12:39 PM in Bug Reports
Follow this question
Once you sign in you will be able to subscribe for any updates here