# Array input broken in ActorComponent delegate

**URL:** <https://forums.unrealengine.com/t/array-input-broken-in-actorcomponent-delegate/384864>\
**Category:** Blueprint\
**Tags:** unreal-engine, bug-report, CPP, question, Blueprint\
**Created:** [February 14, 2017, 3:49am UTC](https://forums.unrealengine.com/t/array-input-broken-in-actorcomponent-delegate/384864 "2017-02-14T03:49:34Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![anonymous\_user\_87b7f658](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@anonymous\_user\_87b7f658](https://forums.unrealengine.com/u/anonymous_user_87b7f658)\
**Post date:** [February 14, 2017, 3:49am UTC](https://forums.unrealengine.com/t/array-input-broken-in-actorcomponent-delegate/384864/1 "2017-02-14T03:49:34Z")

</div>

It’s similar to UE-20613,  
I did this:  
DECLARE\_DYNAMIC\_MULTICAST\_DELEGATE\_OneParam (FSomething, TArray, InArray);

and then:  
UPROPERTY (BlueprintAssignable, Category = “BumpCar UDP Messaging”)  
FSomething SomethingHappened;

finally go to an actor blueprint and add this actor component, then add this event, the result looks quite similar to what happens in UE-20613.

---

<div class="post-metadata">

**Author:** ![anonymous\_user\_2b03d27c](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@anonymous\_user\_2b03d27c](https://forums.unrealengine.com/u/anonymous_user_2b03d27c)\
**Post date:** [February 16, 2017, 9:18pm UTC](https://forums.unrealengine.com/t/array-input-broken-in-actorcomponent-delegate/384864/2 "2017-02-16T21:18:08Z")

</div>

Hey vito\_BumpingWorkshop-

Thank you for submitting a bug report. I have reproduced this issue and logged a report for it here [Unreal Engine Issues and Bug Tracker (UE-42065)](https://issues.unrealengine.com/issue/UE-42065) . 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.

Cheers
