Corrupted set variable nodes

There can be still multiple variables with the same name!

It shows only one variable of that name in the variables list but I have 2 different set variable nodes with the same variable name. When I set something in one of them it isn’t there when I get it out of the output of the other node. It works fine when I use the input and output of only of the nodes. My guess is there is still something wrong with renaming variables which can cause existing nodes to get corrupted. Very annoying bug since you can easily spend hours wondering what is going wrong in a complex blueprint.


I was unable to reproduce your issue on our end. I have a couple of questions to help narrow down the issue you are experiencing:

  1. Can you reproduce this issue in a new project?
  2. If so could you provide a detailed list of steps so I can reproduce this issue on our end?
  3. Could you provide screenshots related to your issue?


Turns out this is very easy to recreate:

Just do it the same in a actor. So it has nothing to do with multiple variables with the same name. Probably with something how blueprints are now compiled.

We have logged a report for this issue 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 recommend for this set-up to use a get node instead of a set node to return the values.