No value will be returned by reference?

[IslandQuest]

Did you try this? Declare your array as const TArray<type> &

No value will be returned by reference?

I’m not sure if the OP was doing this in Blueprints or C++, but I ran in to this issue creating a custom event in C++, so I thought I’d post the solution here in case it helps. I was trying to create a custom event that would pass an array of the currently selected actors whenever the selection changes. This was the signature in my original attempt: DECLARE_DYNAMIC_MULTICAST_DELEGATE_OneParam(FOnSelectionChanged, TArray<AActor*> , SelectedObjects); This caused the “NOTE” message which said “N…

[Gono]

Just stumbled on this (UE 5.3), and like ro0nik, I see the blue Note but the data is being passed to the event correctly.

[UnrealMKJ]

Count me as another person having this issue in 5.3. I am passing an array. The array is not being recognized by the event and I am getting the dreaded No value will be returned blue bar.

[Unsttopabel]

Hey guys can anyone solve my issue with DMX materials ??

[Lupoluke]

The issue is still there in 4.27.

But you can easly solve it by flagging “pass by reference”

[IbeJudgment]

I had this issue in 5.2 with an interface. I had to disconnect any interfaces connections on the sending side, then delete the variables and connect the ‘send out connections’ before connecting the ‘send input connections.’ This fixed it for me, but is certainly annoying to have such a random UI bug!

[Maciek_Leto]

Issue persists in UE5.32.
My workaround was to refactor logic to avoid passing the array via the custom event.

Steps to repeat this problem:

1. On blueprint event graph, add a “Get All Actors of Class” (e.g., Pawn)
2. Drag “Out Actors” to a “For Each Loop”.
3. Add a “Custom Event”
4. Drag “Array” from the “For Each Loop” onto the new “Custom Event” (this will add a new Input, which is an Array with greyed-out Pass-by-Reference)
5. Click “Compile” and see the “NOTE” appear.

[Pretty_Boy_Acid]

Even though when you set the array it auto sets pass-by-reference, set it back to a single, manually turn on pass-by-reference and it went away for me when I changed it back to Array.

[LittleToastier]

Yep still a thing. Setting it back to to single then to array again does work though.

[Keda_L]

Here in 5.0.3, it happens again when I want to added an array in custom event

[User-400315961]

It just happened to me too (5.3). Is there any workaround?

[pelorustech]

The message “No Value will be returned by reference” indicates the array parameter is not marked as “pass by reference.” This means changes to the array in the event won’t reflect back to the caller. To fix this, ensure the array is passed by reference in the function signature. Alternatively, process and return the modified array explicitly from the event node.

[BlackYesus]

5.4 here, still persists.

For those trying to replicate, here is my case with event dispatcher:

I have a struct and an array of enums in that struct (type actually doesn’t matter) and I’m calling the OnDamageResponse.

Event setup, basicly just an input with an array of enums.
Keep in mind that You cannot tick the ‘pass by reference’ here, so I can’t even try.

If I pass a single enum (not an array) there is no error, but trying anyhow with the array keeps producing the Note with ‘No value will be returned’:

Additionaliy, everything that listens for that particular event gets notes too, when binding.

All above work flawlessly though, exactly how I thought they would, so seems to be a matter of UI still.

[pelorustech]

The issue occurs because Blueprint events don’t support passing arrays by reference, leading to the “No value will be returned” note. Instead, return the modified array explicitly or use a setter function to update it. This ensures safe handling without triggering warnings.