Blueprint Return Node behaviour

I’ve just discovered the hard way that if:

  1. You call a blueprint function that returns a value.
  2. You call the same function but the logic results in it not returning a value.

It will return the value it returned the first time. It will continue to return that value every time you call the function until the logic explicitly hits the ReturnNode and returns a new value.

It’s not entirely unreasonable behaviour it’s just not what I’d expected it to do (I thought it would return None).

The moral of the story is:

Always connect all of your logic paths to the ReturnNode.


Leave a Reply

Your email address will not be published. Required fields are marked *