UnityEvent can't select from TWO of the same component

If I've got a normal UnityEvent
eg
public UnityEvent OnFinished = new UnityEvent();

and I want to run a function in the inspector, it works fine..
eg I've got this Zoomer animator that fires an event when it finishes.


BUT, if I want to run a function in ANOTHER Zoomer, eg to chain effects together, it doesn't let me select it.


The only way to do this setup is to use separate GameObjects, which is cumbersome. Is this missing? Is there a reason not to show both in the pulldown?

 

I'm uncertain of how UnityEvent works internally through the inspector- it may AddListener on all possible listeners matching the function signature (using GetComponents). My gut says it probably just references the first script it finds, through a single GetComponent, to add the most likely listener to the list.

That said, you can add the necessary pieces to your own script and add the listeners manually in Start, or you can just put in a middle-man function in the Zoomer script- say named "Trigger". When Trigger() gets called on one Zoomer script, it can then use GetComponents to reference all Zoomer scripts on the same GameObject, and call Activate() on all of them.

There may be additional benefits to having children objects that each have their own Zoomer script though- almost nothing in Unity is really set up to accommodate multiple copies of the same components on a single GameObject, and this may not be the last time you run into problems trying to do this even if you manage a workaround here.

 

Yep, I'm guessing it just looks for the first one. But this would be trivial for Unity to fix. It seems arbitrary that Unity don't 'like' multiple copies of components. If they ever get round to drag-rearranging and renaming of components it would be much more consistent and usable.
I usually have middle men connection scripts using C# events, but for quick effects chains the inspector and UnityEvent would be more convenient, which I believe is the point of UnityEvent over C# events.

 

Try drag-and-dropping the zoomer script into the object slot on the UnityEvent. I believe it will select the correct one, though I'm not completely sure.

 

Sorry to bump this, but I'm still curious about this (guessing it's just how it works)
I'm using Playmaker and it's not uncommon that you several FSM's on the same object (like you would with scripts). Problem is that each FSM is the same component type.

 

Any news?

 

That is not working!

 

I have the same problem. Two conversation components for my dialogue system in the same Game object and the events couldn't distinguish them. Seems like it is not a reliable idea to have multiple same components and Unity Events.
In my case I can create an empty GameObject as a children of my NPC for example for each conversation, unfortunately this is the way for my problem.

 

This is resolved by the following steps:

1. Drag&Drop right component (not whole gameObject) to unityEvent.Target.


2. Do not select Function in inspector! It will reset your selected component to first avaliable component in gameObject by this type.


3. Switch inspector to Debug mode and write `Method name` field


4. If your method has argument change field `Mode`.
5. Switch inspector back to normal mode and fill arguments if your changed `Mode` in step 4.

This works but has drawbacks. When you come back to this after a while, you will have no idea who is invoke whom...

 

I have a rather easy way to fix this, you just create a class like "Zoomer1" that just inherits from the Zoomer and do nothing else. There could be 2,3,4,5 as you wish

 

Interesting!

I ran into this myself and came to the conclusion that Unity was doing a GetComponent<...> and just storing the type of the target component. If this works then that can't be the case, and that would surely mean that changing the target when setting the function name is a bug.

Did you report it, by any chance?

Also, from memory, Timeline has exactly this issue as well (possibly because it uses UnityEvents, but I can't remember).